[Solved] All of a sudden every widget displays red API error message

[canoben]

Description

I'm not sure when it started (used Homepage for the last time a few days ago and it worked fine) but when invoking Homepage now all the widgets "pulsate" for several minutes and then display the red API error message (router, Home Assistant, NextCloud, Synology NAS, Jellyfin and others, even the weather). This exact configuration had been working fine now for several weeks at least.
I notice an ETIMEDOUT error for all the widgets now (see log below). What could have caused this?

homepage version

latest (6/6/2024)

Installation method

Docker

Configuration

Homepage latest running in Container Manager 20.10.23-1437 on Synology RS818xs.

Container Logs

2024/07/05 21:29:24 stdout port: 9000
2024/07/05 21:29:24 stdout address: '192.168.1.75',
2024/07/05 21:29:24 stdout syscall: 'connect',
2024/07/05 21:29:24 stdout code: 'ETIMEDOUT',
2024/07/05 21:29:24 stdout errno: -110,
2024/07/05 21:29:24 stdout at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1555:16) {
2024/07/05 21:29:24 stdout Error: connect ETIMEDOUT 192.168.1.75:9000
2024/07/05 21:29:24 stdout 500,
2024/07/05 21:29:24 stdout [2024-07-05T19:29:24.656Z] �[31merror�[39m: [
2024/07/05 21:29:24 stdout [2024-07-05T19:29:24.655Z] �[31merror�[39m: Error calling http://192.168.1.75:9000/...

Browser Logs

No response

Troubleshooting

Homepage can connect to the devices and services because when I click on a widget the corresponding page loads.

[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 seems like the issue might be related to a network timeout when Homepage is trying to connect to the widgets' services. The ETIMEDOUT error indicates that the connection attempt timed out, which means Homepage was not able to establish a connection within the expected timeframe.

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

1. Check Network Connectivity: Ensure that the network is stable and that the Homepage container can reach the services on the specified ports. Since you mentioned that clicking on a widget successfully loads the corresponding page, this might not be the issue, but it's still worth double-checking.

2. Verify Service URLs: Make sure that the URLs configured for the widgets in your services.yaml file are correct and do not end with a trailing slash, as mentioned in the documentation. Incorrect URLs can cause connection issues.

3. Ping Services: Try pinging the services from within the Homepage container to ensure that they are reachable. You can do this by executing the following command:

   docker exec homepage ping SERVICEIP
   

4. Check Firewall Settings: If there is a firewall in place, ensure that it is not blocking the connections from the Homepage container to the services.

5. Review Docker Network Configuration: If you are using Docker, make sure that the Homepage container is on the same network as the services it is trying to reach. If they are on different networks, you may need to adjust your Docker network settings.

6. Check for Updates: Since you are using the latest version of Homepage, ensure that there are no updates or bug fixes that address this issue. Check the Homepage GitHub repository for any recent updates or issues reported by other users.

7. Review Homepage Logs: Look into the homepage.log file for any additional error messages that might give you more insight into the problem.

8. Restart Homepage: Sometimes, simply restarting the Homepage container can resolve transient issues. You can restart the container using the following command:

   docker restart homepage
   

If after following these steps the issue persists, you may want to reach out to the Homepage community for further assistance. You can use the 'Ask AI' feature in the documentation, open a GitHub discussion, or join the Discord channel for support.

This comment was generated by Glime.

[canoben]

Damn, the AI bot is good and I'm stupid. I messed around with the Synology firewall a few days ago and only allowed my normal network, plus another VLAN I'm using. The bot suggested checking the firewall and voilà.
I suppose I'll have to add the internal Docker network, too. That would be the 172.something network, right?

[github-actions[bot]]

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

[github-actions[bot]]

This discussion has been automatically locked since there has not been any recent activity after it was closed. Please open a new discussion for related concerns. See our contributing guidelines for more details.