添加链接
link管理
链接快照平台
  • 输入网页链接,自动生成快照
  • 标签化管理网页链接
For several days, I have been trying to set up NextCloud on testing rig first to make sure it works then I would set it up on my main server. I have been following a series of tutorials from Spaceinvader One (See Below) and I have been following word for word except for the parameters that correspond to me. When I tried to make sure the Reverse Proxy is working after doing the port forwarding in my router, I should see the Swag Instance screen, but instead I'm getting Cloudflare error 522. I followed the tips on Cloudflare's community page so far with no luck. Then I saw a similar post from a few years ago with a different reverse proxy and someone suggested going under the management access and changing the HTTP & HTTPS ports and adding them into the router settings to if that helped. I tried that and all I could bring up was Unraid login screen. I switched them back and now I'm back to Error 522. I am using an AT&T Fiber router and originally thought that was the issue due to the restrictions they place on it. So I did a IP pass through and switched to pfsense with no luck. I removed all restrictions I can think of to see if I can get it to respond with no traction. I went back to the AT&T router because pfsense was causing way too much lag and connectivity issues. (other problems i need to solve down the road). I went through every config file... Every setting in Unraid.. Followed all the guides and forum posts i could find on the issue with no luck. I just updated to 6.11.0 (thinking maybe this will fix some underlying issue i cant find) and nope, same problem..  To offer some more info to maybe be help speed the process along, just like rlentz2022, I am trying to get NextCloud to run off of a reverse proxy so i can access it from anywhere. I am using nginx to ease of use but am willing to switch back to swag if that will help fix the issue. I have a cloudflare domain directing back to a duckdns.org url to my home IP which should then be port forwarded to nginx and that will tell which docker to connect to. I get back error 522. If there is anything i am missing in this process, please correct me. I truly don't know how to fix this issue.  I am using an AT&T Fiber router and originally thought that was the issue due to the restrictions they place on it. So I did a IP pass through and switched to pfsense with no luck. I removed all restrictions I can think of to see if I can get it to respond with no traction. I went back to the AT&T router because pfsense was causing way too much lag and connectivity issues. (other problems i need to solve down the road). I went through every config file... Every setting in Unraid.. Followed all the guides and forum posts i could find on the issue with no luck. I just updated to 6.11.0 (thinking maybe this will fix some underlying issue i cant find) and nope, same problem..  To offer some more info to maybe be help speed the process along, just like rlentz2022, I am trying to get NextCloud to run off of a reverse proxy so i can access it from anywhere. I am using nginx to ease of use but am willing to switch back to swag if that will help fix the issue. I have a cloudflare domain directing back to a duckdns.org url to my home IP which should then be port forwarded to nginx and that will tell which docker to connect to. I get back error 522. If there is anything i am missing in this process, please correct me. I truly don't know how to fix this issue.  Thanks for this! This was bugging me for months. Weirdly my iPhone was unable to connect to aything from a remote location, yet a Roku stick offsite had no issue connecting to Emby.
At the time of writing, the SSL/TLS Encryption Mode setting in Cloudflare is under the SSL/TLS -> Overview menu.  You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.