Closed realdegrees closed 3 years ago
What happens when you exec into the container and try something like curl localhost:9001
?
The result should look like this:
root@8e9cc86c773f:/# curl localhost:9001
<head>
<title>Error response</title>
</head>
<body>
<h1>Error response</h1>
<p>Error code 401.
<p>Message: Unauthorized.
</body>
This should quickly tell us if the supervisor web UI is active or not.
Also check the container logs. One of the first lines should say something like
INFO - Supervisor http server activated
...
...
2021-07-22 10:04:26,397 INFO Included extra file "/usr/local/etc/supervisor/conf.d/http_server.conf" during parsing
which also indicates that the supervisor web server is being loaded.
Closing for inactivity. Reopen if still an issue.
I am using docker-compose to run this image. The server runs fine and we've played on it for a few days. Now I wanted to enable to supervisor web UI for easier restarting. All supervisord functions work fine inside the container. The web UI always gives me a gateway error. Ports are open in UFW and everything works fine in other game containers which also provide web UIs.
This is my docker-compose
Traefik has nothing to do with this error, my minecraft server running the exact same traefik config has no problem exposing its' web services. Here's that docker-compose for reference.
It seems to me that the supervisord web UI just isn't running. I have already tried changing the port via the environment variable but that didn'T make a difference. However I think that the environment variable might not get passed to the container properly since the "LOG_FILTER" environment variables didn't change anything in the logs either, maybe there is a problem with that?