All of my services are no longer working.

[Manny8787]

Description

I had all my services and widgets running correctly. I hadn't changed, updated or done anything and now all of a sudden nothing is working.
I installed hompage with container station on QNAP.

homepage version

v0.8.8

Installation method

Other (please describe above)

Configuration

version: "3.3"
services:

  dockerproxy:
    image: ghcr.io/tecnativa/docker-socket-proxy:latest
    container_name: dockerproxy
    environment:
    - CONTAINERS=1 # Allow access to viewing containers
    - SERVICES=1 # Allow access to viewing services (necessary when using Docker Swarm)
    - TASKS=1 # Allow access to viewing tasks (necessary when using Docker Swarm)
    - POST=0 # Disallow any POST operations (effectively read-only)
    ports:
    - 127.0.0.1:2375:2375
    volumes:
    - /var/run/docker.sock:/var/run/docker.sock:ro # Mounted as read-only
    restart: unless-stopped
  
  homepage:
    image: ghcr.io/gethomepage/homepage:latest
    container_name: homepage
    ports:
      - 3010:3000
    volumes:
      - /share/CACHEDEV1_DATA/appdata/homepage/config:/config # Make sure your local config directory exists
      - /var/run/docker.sock:/var/run/docker.sock # (optional) For docker integrations

Container Logs

]
[2024-02-20T17:31:10.135Z] error: Error calling http://192.168.1.50:8787/api/v1/book...
[2024-02-20T17:31:10.135Z] error: [
500,
Error: connect ETIMEDOUT 192.168.1.50:8787
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1555:16) {
errno: -110,
code: 'ETIMEDOUT',
syscall: 'connect',
address: '192.168.1.50',
port: 8787
}
]
[2024-02-20T17:31:10.136Z] error: Error calling http://192.168.1.50:8686/api/v1/queue/status...
[2024-02-20T17:31:10.137Z] error: [
500,
Error: connect ETIMEDOUT 192.168.1.50:8686
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1555:16) {
errno: -110,
code: 'ETIMEDOUT',
syscall: 'connect',
address: '192.168.1.50',
port: 8686
}
]

Browser Logs

[2024-02-20T17:14:14.311Z] error: HTTP 500 getting data from qBittorrent. Data: { error: [Object] }
[2024-02-20T17:14:14.312Z] error: Error calling http://192.168.1.50:8085/api/v2/torrents/info...
[2024-02-20T17:14:14.312Z] error: [
500,
Error: connect ETIMEDOUT 192.168.1.50:8085
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1555:16) {
errno: -110,
code: 'ETIMEDOUT',
syscall: 'connect',
address: '192.168.1.50',
port: 8085
}
]
[2024-02-20T17:14:14.312Z] error: HTTP 500 getting data from qBittorrent. Data: { error: [Object] }
[2024-02-20T17:15:23.936Z] error: Error calling http://192.168.1.50:7331/api/libraries...
[2024-02-20T17:15:23.936Z] error: [
500,
Error: connect ETIMEDOUT 192.168.1.50:7331
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1555:16) {
errno: -110,
code: 'ETIMEDOUT',
syscall: 'connect',
address: '192.168.1.50',
port: 7331
}
]
[2024-02-20T17:15:23.937Z] error: Error getting data from Audiobookshelf: 500. Data: [object Object]
[2024-02-20T17:15:23.937Z] error: Error calling http://192.168.1.50:9696/api/v1/indexerstats...
[2024-02-20T17:15:23.937Z] error: [
500,
Error: connect ETIMEDOUT 192.168.1.50:9696
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1555:16) {
errno: -110,
code: 'ETIMEDOUT',
syscall: 'connect',
address: '192.168.1.50',
port: 9696
}
]
[2024-02-20T17:15:23.938Z] error: Error calling http://192.168.1.50:5055/api/v1/request/count...
[2024-02-20T17:15:23.938Z] error: [
500,
Error: connect ETIMEDOUT 192.168.1.50:5055
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1555:16) {
errno: -110,
code: 'ETIMEDOUT',
syscall: 'connect',
address: '192.168.1.50',
port: 5055
}
]
[2024-02-20T17:15:23.939Z] error: HTTP Error 500 calling http://192.168.1.50:5055/api/v1/request/count
[2024-02-20T17:15:23.939Z] error: Error calling http://192.168.1.50:8085/api/v2/torrents/info...
[2024-02-20T17:15:23.939Z] error: [
500,
Error: connect ETIMEDOUT 192.168.1.50:8085
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1555:16) {
errno: -110,
code: 'ETIMEDOUT',
syscall: 'connect',
address: '192.168.1.50',
port: 8085
}
]
[2024-02-20T17:15:23.940Z] error: HTTP 500 getting data from qBittorrent. Data: { error: [Object] }
[2024-02-20T17:15:23.940Z] error: Error calling http://192.168.1.50:6767/api/episodes/wanted...
[2024-02-20T17:15:23.941Z] error: [
500,
Error: connect ETIMEDOUT 192.168.1.50:6767
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1555:16) {
errno: -110,
code: 'ETIMEDOUT',
syscall: 'connect',
address: '192.168.1.50',
port: 6767
}
]
[2024-02-20T17:15:23.941Z] error: Error calling http://192.168.1.50:9696/api/v1/indexerstats...
[2024-02-20T17:15:23.942Z] error: [
500,
Error: connect ETIMEDOUT 192.168.1.50:9696
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1555:16) {
errno: -110,
code: 'ETIMEDOUT',
syscall: 'connect',
address: '192.168.1.50',
port: 9696
}
]
[2024-02-20T17:15:23.944Z] error: Error calling http://192.168.1.50:8086/api/v2/torrents/info...
[2024-02-20T17:15:23.944Z] error: [
500,
Error: connect ETIMEDOUT 192.168.1.50:8086
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1555:16) {
errno: -110,
code: 'ETIMEDOUT',
syscall: 'connect',
address: '192.168.1.50',
port: 8086
}
]
[2024-02-20T17:15:23.944Z] error: HTTP 500 getting data from qBittorrent. Data: { error: [Object] }
[2024-02-20T17:15:36.225Z] error: Error calling http://192.168.1.50:8085/api/v2/torrents/info...
[2024-02-20T17:15:36.225Z] error: [
500,
Error: connect ETIMEDOUT 192.168.1.50:8085
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1555:16) {
errno: -110,
code: 'ETIMEDOUT',
syscall: 'connect',
address: '192.168.1.50',
port: 8085
}
]
[2024-02-20T17:15:36.226Z] error: HTTP 500 getting data from qBittorrent. Data: { error: [Object] }
[2024-02-20T17:15:36.226Z] error: Error calling http://192.168.1.50:7331/api/libraries...
[2024-02-20T17:15:36.227Z] error: [
500,
Error: connect ETIMEDOUT 192.168.1.50:7331
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1555:16) {
errno: -110,
code: 'ETIMEDOUT',
syscall: 'connect',
address: '192.168.1.50',
port: 7331
}
]
[2024-02-20T17:15:36.227Z] error: Error getting data from Audiobookshelf: 500. Data: [object Object]
[2024-02-20T17:15:36.227Z] error: Error calling http://192.168.1.50:5055/api/v1/request/count...
[2024-02-20T17:15:36.228Z] error: [
500,
Error: connect ETIMEDOUT 192.168.1.50:5055
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1555:16) {
errno: -110,
code: 'ETIMEDOUT',
syscall: 'connect',
address: '192.168.1.50',
port: 5055
}
]
[2024-02-20T17:15:36.228Z] error: HTTP Error 500 calling http://192.168.1.50:5055/api/v1/request/count
[2024-02-20T17:15:36.229Z] error: Error calling http://192.168.1.50:6767/api/episodes/wanted...
[2024-02-20T17:15:36.229Z] error: [
500,
Error: connect ETIMEDOUT 192.168.1.50:6767
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1555:16) {
errno: -110,
code: 'ETIMEDOUT',
syscall: 'connect',
address: '192.168.1.50',
port: 6767
}
]
[2024-02-20T17:15:36.230Z] error: Error calling http://192.168.1.50:9696/api/v1/indexerstats...
[2024-02-20T17:15:36.230Z] error: [
500,
Error: connect ETIMEDOUT 192.168.1.50:9696
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1555:16) {
errno: -110,
code: 'ETIMEDOUT',
syscall: 'connect',
address: '192.168.1.50',
port: 9696
}
]
[2024-02-20T17:15:36.231Z] error: Error calling http://192.168.1.50:8086/api/v2/torrents/info...
[2024-02-20T17:15:36.231Z] error: [
500,
Error: connect ETIMEDOUT 192.168.1.50:8086
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1555:16) {
errno: -110,
code: 'ETIMEDOUT',
syscall: 'connect',
address: '192.168.1.50',
port: 8086
}
]
[2024-02-20T17:15:36.231Z] error: HTTP 500 getting data from qBittorrent. Data: { error: [Object] }
[2024-02-20T17:15:40.320Z] error: Error calling http://192.168.1.50:5055/api/v1/request/count...
[2024-02-20T17:15:40.321Z] error: [
500,
Error: connect ETIMEDOUT 192.168.1.50:5055
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1555:16) {
errno: -110,
code: 'ETIMEDOUT',
syscall: 'connect',
address: '192.168.1.50',
port: 5055
}
]
[2024-02-20T17:15:40.321Z] error: HTTP Error 500 calling http://192.168.1.50:5055/api/v1/request/count
[2024-02-20T17:15:40.322Z] error: Error calling http://192.168.1.50:6767/api/episodes/wanted...
[2024-02-20T17:15:40.323Z] error: [
500,
Error: connect ETIMEDOUT 192.168.1.50:6767
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1555:16) {
errno: -110,
code: 'ETIMEDOUT',
syscall: 'connect',
address: '192.168.1.50',
port: 6767
}
]
[2024-02-20T17:15:40.324Z] error: Error calling http://192.168.1.50:9696/api/v1/indexerstats...
[2024-02-20T17:15:40.324Z] error: [
500,
Error: connect ETIMEDOUT 192.168.1.50:9696
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1555:16) {
errno: -110,
code: 'ETIMEDOUT',
syscall: 'connect',
address: '192.168.1.50',
port: 9696
}
]
[2024-02-20T17:15:40.325Z] error: Error calling http://192.168.1.50:8086/api/v2/torrents/info...
[2024-02-20T17:15:40.325Z] error: [
500,
Error: connect ETIMEDOUT 192.168.1.50:8086
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1555:16) {
errno: -110,
code: 'ETIMEDOUT',
syscall: 'connect',
address: '192.168.1.50',
port: 8086
}
]
[2024-02-20T17:15:40.325Z] error: HTTP 500 getting data from qBittorrent. Data: { error: [Object] }
[2024-02-20T17:15:40.326Z] error: Error calling http://192.168.1.50:8085/api/v2/torrents/info...
[2024-02-20T17:15:40.326Z] error: [
500,
Error: connect ETIMEDOUT 192.168.1.50:8085
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1555:16) {
errno: -110,
code: 'ETIMEDOUT',
syscall: 'connect',
address: '192.168.1.50',
port: 8085
}
]
[2024-02-20T17:15:40.327Z] error: HTTP 500 getting data from qBittorrent. Data: { error: [Object] }
[2024-02-20T17:15:40.328Z] error: Error calling http://192.168.1.50:7331/api/libraries...
[2024-02-20T17:15:40.328Z] error: [
500,
Error: connect ETIMEDOUT 192.168.1.50:7331
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1555:16) {
errno: -110,
code: 'ETIMEDOUT',
syscall: 'connect',
address: '192.168.1.50',
port: 7331
}
]
[2024-02-20T17:15:40.328Z] error: Error getting data from Audiobookshelf: 500. Data: [object Object]

Troubleshooting

Nothing has worked

[glime-ai[bot]]

Thanks for posting a discussion about homepage here on GitHub. Homepage now uses a fancy new AI tool thanks to our friends at Glime, so the answer below is the AI bot's attempt to answer your question. If you feel it's sufficient you can mark the answer and close this post, otherwise feel free to leave it open of course!

Thanks for using Homepage! ❤️

---

Based on the information provided, it appears that your Homepage instance is unable to connect to the services it's trying to proxy. The ETIMEDOUT errors indicate that connection attempts to the various service IPs and ports are timing out, which suggests a network connectivity issue.

Here are some steps you can take to troubleshoot the issue:

1. Check Network Connectivity: Ensure that the Homepage container can communicate with the service hosts. You can do this by logging into the container and using ping or curl commands to reach the service IPs.

2. Verify Service Status: Make sure that the services you're trying to reach are up and running. You can check this by accessing them directly or by checking their status in their respective management interfaces.

3. Firewall/Network Configuration: If there have been any changes to your network configuration or firewall rules, they could be blocking the connections. Verify that the necessary ports are open and that there are no new rules that could be causing the timeouts.

4. Container Network: Ensure that the Homepage container is on the correct Docker network and that it has the necessary permissions to communicate with other containers or hosts on your network.

5. Service URLs: Double-check the service URLs configured in Homepage to ensure they are correct and do not have any trailing slashes or incorrect paths as per the documentation.

6. Logs: Review the logs of both the Homepage container and the service containers for any additional error messages that could provide clues.

7. Restart Services: Sometimes, simply restarting the services and the Homepage container can resolve transient network issues.

8. Documentation and Support: Utilize the Homepage documentation and support channels such as the AI bot, GitHub discussions, or Discord for additional help.

If you need further assistance, please provide more details about any changes made to your network or service configurations, or any additional error messages you might be seeing.

This comment was generated by Glime.

[Manny8787]

All the services say they are running. As i mentioned. I hadn't changed anything in the containers or in any or the yml files. I can reach all the services through homepage. The API key is correct.

[shamoon]

It’s presumably a network thing. Try deleting and re-creating the homepage container and or docker proxy. If that doesn’t do it, you may need to take everything down and then back up (literally compose down then up)

also there’s no point in using the docker proxy if you also give homepage access to the docker socket, it’s an either or kinda thing

[Manny8787]

Ok, I have removed both containers, and all all folders and recreated them. Still no luck. I have tried disabling the firewall, with and without docker proxy and still no luck.
When i'm onn homepage, it says all the services are running, but it wont show any inforamtion about them, when I click on the service it takes me to the correct web page. I have tried restarting all of the services and even my qnap.
I am not sure what else I can try at this point.

[shamoon]

Try running a curl to the service(s) from inside the homepage container, see the troubleshooting guide. My assumption is that will fail

Also deleting the docker network(s) if applicable

[Manny8787]

Yes it has come back with this error: curl: (28) Failed to connect to 192.168.1.50 port 5055 after 132151 ms: Couldn't connect to server
As I mentioned, I haven't changed anything in regards to the networking so I am not sure how to even fix this.

[shamoon]

Oh, are you using IP addresses to connect to other containers? If so, don’t.

take a look at eg https://www.tutorialworks.com/container-networking/
And https://docs.docker.com/network/

[alaya233]

I also have the same problem and it's not resolved. Is there any solution?

[alaya233]

It may be a problem with QNAP docker permissions. The same configuration works fine on Synology.

[alaya233]

If you use docker compose,added
network_mode: bridge
to the dockerproxy ymal and homepage ymal.
it worked fine

[github-actions[bot]]

This discussion has been automatically closed due to inactivity. See our contributing guidelines for more details.