Caddy metrics issue on 0.9.1

[lnlyssg]

Description

The Caddy widget does not work under 0.9.1 but does work OK under 0.8.13. This is what the widget now shows:

I can't see any errors in the logs

homepage version

v0.9.1 (19c3ac0, Jun 3, 2024)

Installation method

Docker

Configuration

- Caddy:
        icon: caddy
        widget:
          type: caddy
          url: http://192.168.6.198:2019/

Container Logs

No response

Browser Logs

"Failed to load resource: the server responded with a status of 403 (Forbidden)" against api/services/proxy?group=Home&service=Caddy&endpoint=result

Troubleshooting

curl within container works fine
ping works fine
Widget works fine after downgrading to 0.8.13:

[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 that the Caddy widget is not functioning correctly after an update to version 0.9.1 of Homepage, but it works fine when downgraded to version 0.8.13. Since you've mentioned that there are no errors in the container logs and that both curl and ping commands work fine within the container, this suggests that the issue is not with the network connectivity or the Caddy service itself.

The browser logs indicate a "403 (Forbidden)" error when trying to load a resource from the api/services/proxy endpoint. This could imply a permissions issue or a change in the way the proxy endpoint handles requests in the new version of Homepage.

Here are a few steps you can take to troubleshoot the issue further:

1. Review the release notes or changelog for Homepage version 0.9.1 to see if there were any changes made to the proxy service or widget configurations that could affect the Caddy widget. Look for any migration steps or breaking changes that need to be addressed.

2. Double-check the widget configuration in your yaml file to ensure that it adheres to the new version's requirements. Make sure that the URL does not end with a slash, as per the troubleshooting documentation, which states that URLs should not end with a / or other API path unless otherwise noted.

3. Since the error is a 403 Forbidden, verify if there were any changes in the authentication or authorization mechanisms in the new version that might be blocking the widget from accessing the Caddy service.

4. If possible, enable debug logging for Homepage by setting the LOG_LEVEL environment variable to debug and check the logs again for more detailed error messages.

5. If the issue persists, consider opening a GitHub issue or discussion on the Homepage repository to seek assistance from the developers or community. Provide all the relevant details, including the steps you've taken to troubleshoot and any findings from the logs.

If you need further assistance or have additional information, please let me know.

This comment was generated by Glime.

[fate8383]

I have exact the same problem.

[shamoon]

#3578

[lnlyssg]

Thanks. I did search but only on Open discussions - the other discussion should probably be left open until the fix is out.