Omada Issue

[ryaneford]

Description

Hi there, I added my omada controller info but it's giving the following error.

API Error: JSON.parse: unexpected character at line 1 column 1 of the JSON data

homepage version

v0.8.13 (986a181, May 6, 2024)

Installation method

Docker

Configuration

- Omada:
        icon: omada.png
        href: http://192.168.0.11
        description: Omada Controller
        widget:
            type: omada
            url: http://192.168.0.11
            username: REDACTED
            password: REDACTED
            site: Turntable
            fields: ["connectedSwitches", "connectedAp",  "activeUser", "alerts"]

Container Logs

[2024-05-07T22:57:54.052Z] error: Error calling http://192.168.0.11/fb6be238b74fc2aa4c40a7b44f7d5ea2/api/v2/login...
[2024-05-07T22:57:54.054Z] error: undefined
[2024-05-07T22:57:54.053Z] error: [
500,
Error [ERR_FR_REDIRECTION_FAILURE]: Redirected request failed: Protocol "https:" not supported. Expected "http:"
at RedirectableRequest._onNativeResponse (/app/node_modules/.pnpm/follow-redirects@1.15.6/node_modules/follow-redirects/index.js:95:17)
at Object.onceWrapper (node:events:632:26)
... 2 lines matching cause stack trace ...
at HTTPParser.parserOnHeadersComplete (node:_http_common:119:17)
at Socket.socketOnData (node:_http_client:541:22)
at Socket.emit (node:events:517:28)
at addChunk (node:internal/streams/readable:368:12)
at readableAddChunk (node:internal/streams/readable:341:9)
at Readable.push (node:internal/streams/readable:278:10) {
cause: TypeError [ERR_INVALID_PROTOCOL]: Protocol "https:" not supported. Expected "http:"
at new NodeError (node:internal/errors:405:5)
at new ClientRequest (node:_http_client:188:11)
at Object.request (node:https:366:10)
at RedirectableRequest._performRequest (/app/node_modules/.pnpm/follow-redirects@1.15.6/node_modules/follow-redirects/index.js:326:24)
at RedirectableRequest._processResponse (/app/node_modules/.pnpm/follow-redirects@1.15.6/node_modules/follow-redirects/index.js:483:8)
at RedirectableRequest._onNativeResponse (/app/node_modules/.pnpm/follow-redirects@1.15.6/node_modules/follow-redirects/index.js:91:12)
at Object.onceWrapper (node:events:632:26)
at ClientRequest.emit (node:events:517:28)
at HTTPParser.parserOnIncomingClient (node:_http_client:700:27)
at HTTPParser.parserOnHeadersComplete (node:_http_common:119:17) {
code: 'ERR_INVALID_PROTOCOL'
},
code: 'ERR_FR_REDIRECTION_FAILURE'
}
]

Browser Logs

No response

Troubleshooting

tried adding http/https

[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 error message you're receiving and the container logs, it seems that there is an issue with the protocol being used to connect to your Omada controller. The error Redirected request failed: Protocol "https:" not supported. Expected "http:" indicates that the widget is trying to redirect from an HTTP to an HTTPS protocol, but this is not supported in the current context.

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

1. Check the Omada Controller Configuration: Ensure that your Omada controller is configured to accept connections via the protocol you are using in your widget configuration. If your Omada controller is set up to only accept HTTPS connections, you will need to use https:// in your widget URL.

2. Verify URL in the Widget Configuration: According to the documentation, the URL should not end with a slash or other API path unless otherwise noted. Make sure that the URL in your widget configuration follows this rule.

3. Use HTTPS if Required: If your Omada controller requires HTTPS and you have a valid SSL certificate installed, change the protocol in the widget URL to https://.

4. Check for Redirection Rules: If there are any redirection rules on your network or within the Omada controller that automatically redirect HTTP to HTTPS, this could be causing the issue. You may need to adjust these rules or update your widget configuration to use the correct protocol from the start.

5. Review the Homepage Documentation: Make sure that you have followed all the steps in the documentation for setting up the Omada widget correctly.

6. Check for Updates: Ensure that you are using the latest version of Homepage, as updates may contain fixes for issues like this.

7. Seek Support: If you continue to experience issues, consider reaching out for support on the Homepage GitHub issues page or the Discord channel mentioned in the troubleshooting documentation.

Remember to replace any sensitive information such as usernames and passwords with placeholders when sharing your configuration for troubleshooting.

If you need further assistance, please provide additional details about your setup, including whether your Omada controller is configured to use HTTPS and if you have a valid SSL certificate installed.

This comment was generated by Glime.

[ryaneford]

HTTP appears to resove to HTTPS automatically and there doesn't appear to be a setting that allows me to not resolve to https

[swooshant]

You need to adjust your widget url to this url: https://192.168.0.11:8043

[swooshant]

Widget url needs to have url: https:<ip-address>:8043 since you are getting redirected to https.

[ryaneford]

There is http port 8088 which seems to resolve to something but doesn't produce a login screen. using that give me the original API error

http://192.168.0.11:8088/fb6be238b74fc2aa4c40a7b44f7d5ea2/login is what it resolves to.

[swooshant]

Huh so how do you get to the omada login screen then? https://192.168.5.11:8043?

[ryaneford]

The hardware uses port 80 and 443

[ryaneford]

I found where i can change the portal and portal access being 80:443 and 8088:8843 respectively. I turned off both "Redirect HTTP to HTTPS" and still the same error persists.

[ryaneford]

Even more fun, there is a section called Platform integration that allows me to generate an OpenAPI ID that points to https of the controller IP. I created one but not a single idea how to deploy it so it works with homepage