Omada widget API error #743
Replies: 8 comments 12 replies
-
You checked off that you ran through the troubleshooting guide, can you post the output of your |
Beta Was this translation helpful? Give feedback.
-
Oops I missed it
|
Beta Was this translation helpful? Give feedback.
-
Issues are for bugs but the purpose of the troubleshooting guide and error display etc is all to see if folks can self-resolve. Of course that isnt always possible. That curl command isnt really correct, thats just the URL of your controller. The actual URLs depend on which controller version, etc. Again, this isnt obvious without looking at the code, I understand. So first of all, which Omada controller version are you using? What is the output of |
Beta Was this translation helpful? Give feedback.
-
I have the physical controller
|
Beta Was this translation helpful? Give feedback.
-
+1 here, same error message also have the physical controller |
Beta Was this translation helpful? Give feedback.
-
I am using the Software Controller. It runs on port 8043, so no docker container impacts. I am using Homepage built from pnpm. I have confirmed that it gets HTTP 200 when doing |
Beta Was this translation helpful? Give feedback.
-
This discussion has been automatically closed due to inactivity. |
Beta Was this translation helpful? Give feedback.
-
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. |
Beta Was this translation helpful? Give feedback.
-
Description
config:
Steps to reproduce
Maybe I'm wrong but for some reason it doesn't work for me.
homepage version
0.5.7
Installation method
Docker
Configuration
No response
Container Logs
in log file
Browser Logs
No response
Other
No response
Before submitting, I have made sure to
Beta Was this translation helpful? Give feedback.
All reactions