Omada API error in v0.9.1

[rookie50]

Description

In the new version I got an API error:
{"error":"Unmapped proxy request."}

homepage version

v0.9.1

Installation method

Docker

Configuration

- Network:
    - Omada:
        icon: omada.svg
        href: "https://oc01.domain.me:8043"
        description: omada
        widget:
            type: omada
            url: "https://oc01.domain.me:8043"
            username:  "idiot"
            password:  "xtremeSavePWD"
            site: "Asylum"
            fields: ["connectedAp",  "activeUser", "alerts"]

Container Logs

no log output

Browser Logs

Network Answer

{"error":"Unmapped proxy request."}

Troubleshooting

v0.8.13 works with same settings.

[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 and the context from the sources, it seems that the issue might be related to the use of HTTPS in the Omada widget configuration. The Omada widget documentation specifies the use of HTTP in the URL field, and there is a reported issue (issue #2545) where a user encountered problems when attempting to use HTTPS with the Omada controller.

To troubleshoot this issue, you could try the following steps:

1. Ensure that the Omada controller is accessible via HTTPS from the machine where Homepage is running. You can do this by accessing the controller's URL directly in a web browser or using a tool like curl.

2. If the controller is accessible and you still receive the API error, consider switching the URL in the widget configuration to use HTTP instead of HTTPS, as the widget might not support HTTPS or there might be an issue with the SSL certificate that is causing the widget to fail.

3. Check the Homepage version compatibility. Since you mentioned that version v0.8.13 works with the same settings, there might be a regression or change in behavior in version v0.9.1 that is causing the issue. Review the release notes or changelog for v0.9.1 to see if there are any breaking changes or updates related to the Omada widget or proxy requests.

4. If the issue persists, you may want to report it to the Homepage development team by creating a new issue on the GitHub repository, providing all the relevant details and the steps you have taken to troubleshoot.

Remember to replace any sensitive information like usernames and passwords before sharing your configuration publicly.

If you need further assistance, please provide additional details or clarify any specific steps you have already taken.

This comment was generated by Glime.

[shamoon]

Thanks for reporting, some widgets git broken by a security fix we added.

Since I cant test this without Omada hardware, can you try out the main docker tag and let me know if its solved for you?

Closed by #3587

[abolians]

I had the same issue with 0.9.1 and can confirm the widget works fine with the ":main" tag.

[rookie50]

I can confirm as well: in the main release it is working.

[ToqQrrl]

Same thing here ... the :main release works

[github-actions[bot]]

This discussion has been automatically closed because it was marked as answered. See our contributing guidelines for more details.