Carlo 4330 Posted July 10, 2021 Share Posted July 10, 2021 These ports need to be changed. The Internal ports need to be 443 and 80 since that is what NGINX is listening to. BTW, did you say you were using Cloudflare? 1 Link to comment Share on other sites More sharing options...
Carlo 4330 Posted July 10, 2021 Share Posted July 10, 2021 Show us your new port forwarding after making these changes. Link to comment Share on other sites More sharing options...
crusher11 851 Posted July 10, 2021 Author Share Posted July 10, 2021 4 minutes ago, cayars said: These ports need to be changed. The Internal ports need to be 443 and 80 since that is what NGINX is listening to. BTW, did you say you were using Cloudflare? Yes, I'm using CloudFlare. Changing the ports did not help, but it did change things. I used to get a CloudFlare 524 error, now I get a browser "this site can't be reached, [domain] is taking too long to respond" error. It's also appended port 5001 to the domain. No idea why. Link to comment Share on other sites More sharing options...
rodainas 188 Posted July 10, 2021 Share Posted July 10, 2021 Use your browser in private incognite mode to avoid cookies giving outdated urls. Link to comment Share on other sites More sharing options...
Carlo 4330 Posted July 10, 2021 Share Posted July 10, 2021 2 minutes ago, crusher11 said: It's also appended port 5001 to the domain. No idea why. Do you by chance have Proxy Server installed? Link to comment Share on other sites More sharing options...
rodainas 188 Posted July 10, 2021 Share Posted July 10, 2021 2 minutes ago, crusher11 said: Yes, I'm using CloudFlare. Changing the ports did not help, but it did change things. I used to get a CloudFlare 524 error, now I get a browser "this site can't be reached, [domain] is taking too long to respond" error. It's also appended port 5001 to the domain. No idea why. Is Your cloudfare dns A Record? Pointing to your public ip address ? Link to comment Share on other sites More sharing options...
crusher11 851 Posted July 10, 2021 Author Share Posted July 10, 2021 2 minutes ago, rodainas said: Use your browser in private incognite mode to avoid cookies giving outdated urls. Same result. Link to comment Share on other sites More sharing options...
crusher11 851 Posted July 10, 2021 Author Share Posted July 10, 2021 1 minute ago, cayars said: Do you by chance have Proxy Server installed? What? 1 minute ago, rodainas said: Is Your cloudfare dns A Record? Pointing to your public ip address ? Yes. Link to comment Share on other sites More sharing options...
Carlo 4330 Posted July 10, 2021 Share Posted July 10, 2021 3 minutes ago, crusher11 said: Yes, I'm using CloudFlare. Changing the ports did not help, but it did change things. I used to get a CloudFlare 524 error, now I get a browser "this site can't be reached, [domain] is taking too long to respond" error. It's also appended port 5001 to the domain. No idea why. You have a lot of things going on and issues could be anywhere. You would be best removing Cloudflare until you have NGINX working correctly. The easiest way to do this is modify the Cloudflare DNS to point to your WAN-IP. 1 Link to comment Share on other sites More sharing options...
rodainas 188 Posted July 10, 2021 Share Posted July 10, 2021 Use it in dns mode, not proxied to make it easier to pinpoint where the problem is. 1 Link to comment Share on other sites More sharing options...
crusher11 851 Posted July 10, 2021 Author Share Posted July 10, 2021 2 minutes ago, cayars said: You have a lot of things going on and issues could be anywhere. You would be best removing Cloudflare until you have NGINX working correctly. The easiest way to do this is modify the Cloudflare DNS to point to your WAN-IP. Isn't that where it's already pointing? Link to comment Share on other sites More sharing options...
rodainas 188 Posted July 10, 2021 Share Posted July 10, 2021 Question what happens when you enter public ip:80 on browser now? Link to comment Share on other sites More sharing options...
Carlo 4330 Posted July 10, 2021 Share Posted July 10, 2021 1 minute ago, crusher11 said: Isn't that where it's already pointing? Only you would know unless you take a screen shot of your Cloudflare DNS setup. You can blank out part of any IPs showing. Take a picture and show us what Installed packages are shown in Synology Package Manager. Link to comment Share on other sites More sharing options...
crusher11 851 Posted July 10, 2021 Author Share Posted July 10, 2021 2 minutes ago, rodainas said: Question what happens when you enter public ip:80 on browser now? It redirects to port 5000 and refuses to connect. Link to comment Share on other sites More sharing options...
crusher11 851 Posted July 10, 2021 Author Share Posted July 10, 2021 1 minute ago, cayars said: Only you would know unless you take a screen shot of your Cloudflare DNS setup. You can blank out part of any IPs showing. Take a picture and show us what Installed packages are shown in Synology Package Manager. It's currently pointing to my external IP. That's what a WAN IP is, right? Where else would it be pointing? I have Emby, Docker, OAuth Service, Universal Search, File Station, Log Center, inotify-tools, and exFAT Access installed. Link to comment Share on other sites More sharing options...
vdatanet 1549 Posted July 10, 2021 Share Posted July 10, 2021 1 minute ago, crusher11 said: It redirects to port 5000 and refuses to connect. Change DSM or Nginx ports. They cannot be the same. 1 Link to comment Share on other sites More sharing options...
vdatanet 1549 Posted July 10, 2021 Share Posted July 10, 2021 Link to comment Share on other sites More sharing options...
crusher11 851 Posted July 10, 2021 Author Share Posted July 10, 2021 But...they aren't. DSM is 5000, NGINX is 80 and 443. Right? Link to comment Share on other sites More sharing options...
crusher11 851 Posted July 10, 2021 Author Share Posted July 10, 2021 DSM is 5000 and 5001, according to that. FWIW I have no external access set up for DSM itself. Link to comment Share on other sites More sharing options...
vdatanet 1549 Posted July 10, 2021 Share Posted July 10, 2021 No, they DSM default ports are 80 and 443, 5000 is redirected to and 5001 is redirected to 443 Link to comment Share on other sites More sharing options...
crusher11 851 Posted July 10, 2021 Author Share Posted July 10, 2021 Just now, vdatanet said: No, they DSM default ports are 80 and 443, 5000 is redirected to and 5001 is redirected to 443 I don't follow. As above I have no external access configured in DSM. Link to comment Share on other sites More sharing options...
vdatanet 1549 Posted July 10, 2021 Share Posted July 10, 2021 What is showing this picture for you: Link to comment Share on other sites More sharing options...
crusher11 851 Posted July 10, 2021 Author Share Posted July 10, 2021 It's showing HTTP port 5000, and HTTPS port 5001. As I said previously. Link to comment Share on other sites More sharing options...
Carlo 4330 Posted July 10, 2021 Share Posted July 10, 2021 Can I ask a simple question? If using Cloudflare why do you need NGINX? Is there some reason you NEED two proxy servers inline? Right now this is just making your life super complicated, likely for no benefit at all. 1 1 Link to comment Share on other sites More sharing options...
vdatanet 1549 Posted July 10, 2021 Share Posted July 10, 2021 5 minutes ago, cayars said: Can I ask a simple question? If using Cloudflare why do you need NGINX? Is there some reason you NEED two proxy servers inline? Right now this is just making your life super complicated, likely for no benefit at all. Yes, @crusher11 why do you need two proxy servers? Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now