Error 502 Bad Gateway with NPM (nginx proxy manager) #2029
-
Shlink versionlatest docker PHP versionlatest on docker How do you serve ShlinkDocker image Database engineMariaDB Database versionmariadb:latest Current behaviorI get error when trying to access a shortened URL (that I made accessing the As well as when trying to access the url. Docker compose file: On nginx proxy manager (docker:latest): Router and firewall port open. I used a subdomain because the Logs don't seem to indicate anything relevant to this?: Expected behaviorBeing able to access it from the https URL How to reproduceUsing docker shlink and docker NPM with shown configs. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 12 replies
-
|
Please, try not to report bugs for things that are clearly configuration issues. Opening a discussion is preferred in that case. |
Beta Was this translation helpful? Give feedback.
-
|
Sorry, I didn't know about github discussions 🙇. I was only trying to separate one thing from the other, in case someone looks for something similar in the future and I thought it made more sense to treat them separated. That was why I closed the other "issue". 👍️ |
Beta Was this translation helpful? Give feedback.
-
|
Separation and trying to keep one topic per issue is perfectly fine. What I mean is trying not to report something as a bug, when it's not a bug. When trying to create a new issue, you see this dialog first:
You should select "Bug report" only if you know for sure something is not working. In most of the cases what you want is the last option "Question - Support". I guess I should put that first 😅 |
Beta Was this translation helpful? Give feedback.
-
|
Is that a common thing in github? Honestly I didn't see it 😅😅. Maybe it was because of the "greysh" button that doesn't pop up that much (as in "decline/configure cookies" vs ACCEPT cookies 🤣), more likely because I wasn't paying attention, but in my mind the options are just bug report/feature request. I'll be more cautious on any other project as well from now on. Thank you for pointing it out to me! |
Beta Was this translation helpful? Give feedback.
-
|
I would check the reverse proxy logs, as that will probably have more information about what is causing those 502 errors. Most probably, the reverse proxy is not configured to forward traffic to the right place, specially taking into consideration that shlink-web-client is working when bypassing the reverse proxy via |
Beta Was this translation helpful? Give feedback.
-
|
If the reverse proxy is also running in a docker container, then the backend is definitely not localhost 😅 That would reference the container itself, and Shlink is running somewhere else, so that would never work. You need to figure out the right docker network config. Perhaps one option would be defining all the containers involved in the same docker-compose file. There are discussions from other people using similar setups. Perhaps you can find something there. |
Beta Was this translation helpful? Give feedback.
-
|
That makes sense about Anyway, wouldn't not using special docker networks and just pointing to physical addresses work? I'll try to look into other discussions regarding docker. Thanks! |
Beta Was this translation helpful? Give feedback.
-
|
#!@*&%!!!! C'MON ME 😭😭😭😭 IT WAS THE FIREWALL. I was so sure I opened the ports both on the router and on the firewall that I didn't check anymore... But did now and while the router was indeed open, 8081 was only open for the local network 192.168.1.0/24. on the firewall 😢. Now I am ever more ashamed of opening the issue instead of the discussion and making you waste your time! I'm so sorry. Just went straight to https://slnk.to/donate and compensate for this! Thanks man! |
Beta Was this translation helpful? Give feedback.
-
|
Now, once solved the issue of me being dumb, both using docker internal networks and referring the container name or not using docker networks and pointing to regular local IP address. Here are my working compose files and NPM config, in case it helps someone in the future (or if you consider useful to add as compose file examples for the documentation): shlink compose:Note: Nginx Proxy ManagerNPM docker composeAgain, NPM settingsOn the NPM web interface:
Firewall and routerOpen... 🤣 |
Beta Was this translation helpful? Give feedback.
Now, once solved the issue of me being dumb, both using docker internal networks and referring the container name or not using docker networks and pointing to regular local IP address.
Here are my working compose files and NPM config, in case it helps someone in the future (or if you consider useful to add as compose file examples for the documentation):
shlink compose: