You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was trying to use the watchtower widget for my Homepage dashboard, but I keep getting the same problem.
When homepage trying to do his thing to fulfill the widgets' information, it returns "connection refused".
The watchtower and homepage containers are on the same docker-compose file (so, in the same network) :
This error only appears when I'm using the hostname "watchtower" to retrieve the metrics.
From the host, I can curl using curl -H "Authorization: Bearer mytoken" http://localhost:8080/v1/metrics so the API config and metric enabling is OK.
From the homepage container, I can ping the watchtower container with docker exec -it homepage ping watchtower so the hostname is OK.
But if in the homepage container, I wget --header="Authorization: Bearer mytoken" --output-document - http://localhost:8080/v1/metrics I get wget: can't connect to remote host: Connection refused
Finally, using Traefik to expose watchtower to watchtower.mydomain.com, I can curl curl -H "Authorization: Bearer mytoken" https://watchtower.mydomain.com
Steps to reproduce
copy the docker-compose.yaml I dropped above.
docker compose up -d
Uncomment ./homepage/config/docker.yaml lines 9 and 10 (to set the docker sock)
Go to localhost:3000 to see the error in the dashboard
docker exec -it homepage wget --header="Authorization: Bearer mytoken" --output-document - http://localhost:8080/v1/metrics to get the connection refused
docker exec -it homepage ping watchtower to see homepage pinging watchtower
Expected behavior
I'm expecting the same behavior using ip or hostname
Screenshots
When using the host name as is the docker-compose file
When exposing watchtower through Traefik
The only change between the picture is going https://watchtower.mydomain.com instead of http://watchtower:8080
Environment
OS : Ubuntu 22.04.3 LTS
Docker Version: 24.0.7
Your logs
Nothing appears on the log, even with the debug
Additional context
No response
The text was updated successfully, but these errors were encountered:
Hi there! 👋🏼 As you're new to this repo, we'd like to suggest that you read our code of conduct as well as our contribution guidelines. Thanks a bunch for opening your first issue! 🙏
Describe the bug
I was trying to use the watchtower widget for my Homepage dashboard, but I keep getting the same problem.
When homepage trying to do his thing to fulfill the widgets' information, it returns "connection refused".
The watchtower and homepage containers are on the same docker-compose file (so, in the same network) :
This error only appears when I'm using the hostname "watchtower" to retrieve the metrics.
From the host, I can curl using
curl -H "Authorization: Bearer mytoken" http://localhost:8080/v1/metrics
so the API config and metric enabling is OK.From the homepage container, I can ping the watchtower container with
docker exec -it homepage ping watchtower
so the hostname is OK.But if in the homepage container, I
wget --header="Authorization: Bearer mytoken" --output-document - http://localhost:8080/v1/metrics
I getwget: can't connect to remote host: Connection refused
Finally, using Traefik to expose watchtower to watchtower.mydomain.com, I can curl
curl -H "Authorization: Bearer mytoken" https://watchtower.mydomain.com
Steps to reproduce
docker compose up -d
docker exec -it homepage wget --header="Authorization: Bearer mytoken" --output-document - http://localhost:8080/v1/metrics
to get the connection refuseddocker exec -it homepage ping watchtower
to see homepage pinging watchtowerExpected behavior
I'm expecting the same behavior using ip or hostname
Screenshots
When using the host name as is the docker-compose file
When exposing watchtower through Traefik
The only change between the picture is going
https://watchtower.mydomain.com
instead ofhttp://watchtower:8080
Environment
Your logs
Additional context
No response
The text was updated successfully, but these errors were encountered: