crusher11 851 Posted April 30, 2020 Share Posted April 30, 2020 Tried setting this up but I'm getting a 522 error. Installed the docker NGINX, mapped the previous conf file and my cert files, adjusted everything I thought I needed to in the conf file. Turned off NGINX on my PC - a PC based version of my server is still running and was working prior to me killing that NGINX - and now my domain just gives me a 522. I can't connect via IP:Port either, to either my PC or NAS server. They use different ports. Link to comment Share on other sites More sharing options...
Luke 37067 Posted April 30, 2020 Share Posted April 30, 2020 I would suggest comparing your nginx configuration to that of @@pir8radio. Link to comment Share on other sites More sharing options...
crusher11 851 Posted April 30, 2020 Author Share Posted April 30, 2020 It's literally his exact config, which I've used successfully for some time on my PC server. I copied, pasted, and changed a couple of paths and ports to suit. Link to comment Share on other sites More sharing options...
mastrmind11 717 Posted April 30, 2020 Share Posted April 30, 2020 (edited) I can't connect via IP:Port either, to either my PC or NAS server. They use different ports. as in you can't hit either of your machines even when bypassing the proxy? Edited April 30, 2020 by mastrmind11 Link to comment Share on other sites More sharing options...
crusher11 851 Posted April 30, 2020 Author Share Posted April 30, 2020 It would seem that way. Link to comment Share on other sites More sharing options...
crusher11 851 Posted April 30, 2020 Author Share Posted April 30, 2020 If I fire up NGINX on my PC I can hit that server via the domain, though. Link to comment Share on other sites More sharing options...
crusher11 851 Posted April 30, 2020 Author Share Posted April 30, 2020 The NGINX docker container also keeps stopping unexpectedly. Three times within the first five seconds of starting it just now. Up to ten within less than a minute. Link to comment Share on other sites More sharing options...
crusher11 851 Posted May 1, 2020 Author Share Posted May 1, 2020 Changed the location of the error log and the crashes have stopped, fixed my Docker port settings and I can now hit my NAS-based server via IP:PORT. My domain is still getting a 522 error from CloudFlare though. Link to comment Share on other sites More sharing options...
crusher11 851 Posted May 2, 2020 Author Share Posted May 2, 2020 Well I fixed it, although I don't actually know how. Link to comment Share on other sites More sharing options...
pir8radio 1292 Posted May 2, 2020 Share Posted May 2, 2020 (edited) Well I fixed it, although I don't actually know how. lol, i was just going to ask how? good work! I know nothing about the NAS/docker installs. Edited May 2, 2020 by pir8radio 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