-
Notifications
You must be signed in to change notification settings - Fork 134
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
Login to dashboard does not work #258
Comments
This is an occasional reported issue, it seems to be something to do with the way people manage their networking/proxy for the containers... |
Then let me ask, why the example shows bridge configuration, which at least I prefer not to use. Is there any technical reason behind this? |
The documentation is inherited and its not all perfect... If you know a better way then feel free to suggest edits :-) |
If I would understand the need for bridge, I could make or suggest edits. But I am lacking the knowledge here on the technical need. Nobody around that understands the networking needs? |
I dont use bridge networking, I proxy it using traefik and a different instance via apache. |
I installed and configured statping-ng with docker compose. My setup differs from https://github.com/statping-ng/statping-ng/wiki/Docker as I have nginx outside of docker compose serving multiple scenarios, and I didn´t use a bridge network. The relevant section looks as follows:
statup:
container_name: statup
image: adamboutcher/statping-ng:latest
restart: always
depends_on:
- postgres
volumes:
- ./statup/app:/app
ports:
- 8081:8080
environment:
VIRTUAL_PORT: 8080
...
I am getting to the overview page via https://mysubdomain correctly. However trying to login via /https://mysubdomain/login doesn´t work. I don´t even see a network request being issued. I also tried http://hostip:8081, same results. I also tried using a different VIRTUAL_PORT and target port in docker-compose.yaml, but that didn´t work. Actually I am wondering what VIRTUAL_PORT is supposed to do.
Any thoughts?
The text was updated successfully, but these errors were encountered: