-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Running behind proxy #1
Comments
Hi @Jogai , Thanks! Could you provide the command you use to run it? From the log it seems your are requesting http://nimletter:5555, try with http://127.0.0.1 instead 👍 |
Then I see the issue. The 'nimletter' address is of course internal to the proxy (it resolves correctly to 172.16.2.18) but nimletter is just listening to localhost. Can you change this to listening to its own ip or any ip (often 0.0.0.0). |
To be complete, here is my docker compose file where the external docknet network is for the traefik proxy. This way the database is not exposed publicly, and has an extra authentication layer trough authelia.
|
Thanks for PR#2. Regarding the above then it might be because, that I used an older version of podman go generate it - it's still a bit flaky. I would be glad to accept a ready-to-run docker compose file 👍 |
Every environment is different, so I'd imagine with the above most users will be able to run nimletter. If you dont use traefik you can just omit the labels, although they wont hinder running in a different setup. The network part is dependent on the proxy, if any, and which. |
This seems like a nice tool. however, I cant get it to run. The log says its running on port 5555, and the database tables are filled with data, so it seems to start fine. Is there anything in the software itself that would refuse traffic?
The text was updated successfully, but these errors were encountered: