Disable Internal nginx Proxy #367
-
|
Is there a way to disable the internal nginx proxy? I've been using caddy to serve the media files (never used the external nginx), and with the update adding the internal nginx I'm getting an error on start saying "Starting nginx: nginx failed!". I redid my compose to be almost exactly the same as what is in the repo (not serving files via caddy, update envs, remove custom user id), but am still having issues. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 5 replies
-
|
While right now I don't have an exact way to disable it because its the standard feature... that does not mean you have to use it. The main reason why this error is popping up and preventing container start is the nginx conf used by default assumed that there is docker service called "server". If you want to call it "adventurelog-server" or something else, you would have to get a copy of the nginx conf used, found here: https://github.com/seanmorley15/AdventureLog/blob/main/backend/nginx.conf. Then mount it into the container at /etc/ngninx/nginx.conf, changing any reference to "server" with your desired service name. I know you are not exactly using it but this should at least prevent it from preventing startup. If this is still causing issues feel free to send your compose so I can take a look and help ! Sorry this is happening |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the steps on how to fix it, that is indeed what is probably causing my issue (using a different container name). |
Beta Was this translation helpful? Give feedback.
-
|
Sounds good! Let me know if you have any other questions! |
Beta Was this translation helpful? Give feedback.
-
|
Been doing some work on this and still can't get it to work. Is it every reference to server, or just the second server on line 14 and the one on line 22? |
Beta Was this translation helpful? Give feedback.
-
|
These are the references to change in the nginx file. |
Beta Was this translation helpful? Give feedback.
-
|
Hm I was struggling with this, so I just ended up removing the http block entirely. Now nginx starts and I can go back to serving my mediafiles via caddy 😄 |
Beta Was this translation helpful? Give feedback.
While right now I don't have an exact way to disable it because its the standard feature... that does not mean you have to use it. The main reason why this error is popping up and preventing container start is the nginx conf used by default assumed that there is docker service called "server". If you want to call it "adventurelog-server" or something else, you would have to get a copy of the nginx conf used, found here: https://github.com/seanmorley15/AdventureLog/blob/main/backend/nginx.conf. Then mount it into the container at /etc/ngninx/nginx.conf, changing any reference to "server" with your desired service name. I know you are not exactly using it but this should at least prevent it…