intermitent API Error, 502, 500

[ankycooper]

Description

Intermittent API and 502 errs, auto-fixes on self-refresh at times.

homepage version

v0.8.11 (4239e8f, Apr 9, 2024)

Installation method

Docker

Configuration

version: "3.9"
services:
  homepage:
    image: ghcr.io/gethomepage/homepage:latest
    container_name: homepage
    ports:
      - 3000:3000
    volumes:
      - /mnt/flash/hosted/docker/homepage/config:/app/config
      - /mnt/flash/hosted/docker/homepage/images:/app/images
      - /mnt/flash/hosted/docker/homepage/icons:/app/icons
    env_file:
      - stack.env
    restart: always

Container Logs

[2024-04-09T01:57:03.935Z] error: HTTP Error 502 calling https://port.mydomain.com/api/endpoints/3/docker/containers/json?all=1
[2024-04-09T01:57:04.794Z] error: Error calling https://auth.mydomain.com/api/v3/events/events/per_month/...
[2024-04-09T01:57:04.808Z] error: [
500,
Error: getaddrinfo EAI_AGAIN auth.mydomain.com
at GetAddrInfoReqWrap.onlookupall [as oncomplete] (node:dns:118:26) {
errno: -3001,
code: 'EAI_AGAIN',
syscall: 'getaddrinfo',
hostname: 'auth.mydomain.com'
}
]
[2024-04-09T01:57:04.812Z] error: HTTP Error 500 calling https://auth.mydomain.com/api/v3/events/events/per_month/?action=login
[2024-04-09T01:57:10.115Z] error: Error calling https://adg.mydomain.com/...
[2024-04-09T01:57:10.119Z] error: [
500,
Error: getaddrinfo EAI_AGAIN adg.mydomain.com
at GetAddrInfoReqWrap.onlookupall [as oncomplete] (node:dns:118:26) {
errno: -3001,
code: 'EAI_AGAIN',
syscall: 'getaddrinfo',
hostname: 'adg.mydomain.com'
}
]
[2024-04-09T01:57:22.560Z] error: HTTP Error 502 calling https://port.mydomain.com/api/endpoints/3/docker/containers/json?all=1
[2024-04-09T01:57:23.528Z] error: Error calling https://adg.mydomain.com/...
[2024-04-09T01:57:23.531Z] error: [
500,
Error: getaddrinfo EAI_AGAIN adg.mydomain.com
at GetAddrInfoReqWrap.onlookupall [as oncomplete] (node:dns:118:26) {
errno: -3001,
code: 'EAI_AGAIN',
syscall: 'getaddrinfo',
hostname: 'adg.mydomain.com'
}
]
[2024-04-09T01:57:55.897Z] error: HTTP Error 502 calling https://port.mydomain.com/api/endpoints/3/docker/containers/json?all=1
[2024-04-09T01:57:57.145Z] error: Error calling https://adg.mydomain.com/...
[2024-04-09T01:57:57.149Z] error: [
500,
Error: getaddrinfo EAI_AGAIN adg.mydomain.com
at GetAddrInfoReqWrap.onlookupall [as oncomplete] (node:dns:118:26) {
errno: -3001,
code: 'EAI_AGAIN',
syscall: 'getaddrinfo',
hostname: 'adg.mydomain.com'
}
]
[2024-04-09T01:58:21.959Z] error: HTTP Error 502 calling https://port.mydomain.com/api/endpoints/3/docker/containers/json?all=1
[2024-04-09T01:58:22.961Z] error: Error calling https://adg.mydomain.com/...
[2024-04-09T01:58:22.966Z] error: [
500,
Error: getaddrinfo EAI_AGAIN adg.mydomain.com
at GetAddrInfoReqWrap.onlookupall [as oncomplete] (node:dns:118:26) {
errno: -3001,
code: 'EAI_AGAIN',
syscall: 'getaddrinfo',
hostname: 'adg.mydomain.com'
}
]

Browser Logs

No response

Troubleshooting

Uptime kuma container on the same host is monitoring the services without any issue
DNS resolution works
can access the services from my laptop

[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 your Homepage instance is experiencing intermittent network-related errors, specifically HTTP Error 502 and Error: getaddrinfo EAI_AGAIN. These errors suggest that there are issues with DNS resolution or network connectivity from the Homepage container to the services it's trying to reach.

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

1. DNS Resolution: The EAI_AGAIN error is a DNS lookup timed out error, which means it could not resolve the hostname. Ensure that the DNS settings are correctly configured inside the Docker container. You can try to exec into the container and manually check if DNS resolution works by using commands like nslookup or ping.

2. Network Connectivity: Verify that the Homepage container can reach the external services. You can do this by using curl from within the container to the services' URLs to see if they are accessible.

3. Service URLs: Double-check the service URLs configured in your Homepage setup. Ensure there are no trailing slashes or typos in the URLs as per the documentation.

4. Logs and Debugging: Since the logs are showing errors, you might want to increase the log verbosity to get more detailed information. You can set the LOG_LEVEL environment variable to debug for more verbose logging. Make sure to restart the container after making this change.

5. Proxy Configuration: If you are using a proxy, make sure that it is configured correctly and that it is not the source of the 502 errors.

6. Homepage Version: Ensure that you are running the latest version of Homepage, as the issue might have been addressed in a newer release.

7. Ask AI Support: Utilize the Homepage AI Bot for more specific troubleshooting related to Homepage by hitting the 'Ask AI' button on any page in the docs, opening a GitHub discussion, or checking out the #ai-support channel on Discord.

8. Check GitHub Issues: Look for similar issues on the Homepage GitHub repository to see if others have encountered the same problem and if there are any suggested solutions.

If these steps do not resolve the issue, consider opening a GitHub issue with detailed information about your setup, configuration, and the steps you've taken to troubleshoot, so that the maintainers or community can assist you further.

This comment was generated by Glime.

[ankycooper]

There was a DNS rate-limit on my DNS server, disabled so far looking good.
I'll post if I see any more errors.

[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.