Error Code -1 (General Error) on External Portal Server authorize API (Omada Controller v.5.7.6)
local.INFO: Time value sent for authorization: {"time":"2592000000"}
local.INFO: Authentication Omada: [{"stdClass":{"errorCode":-1,"msg":"General error."}}]
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Hi @stha
Thanks for posting here.
Issue Analysis:
- Time Value:
2592000000milliseconds = 30 days (which seems like a very long session/authorization time) - Error Response: Omada API returned
errorCode: -1with message"General error."
Potential Causes:
- Invalid/Expired Token: The authorization token might be expired or invalid
- Session Timeout: 30-day authorization might exceed system limits
- API Configuration: Incorrect API endpoint or credentials
- Network/Connectivity: Issues reaching the Omada authentication server
- Rate Limiting: Too many authentication attempts
BTW, Omada Controller v.5.7.6 is really old; you may update to the latest version.
- Copy Link
- Report Inappropriate Content
Hi @stha
Thanks for posting here.
Issue Analysis:
- Time Value:
2592000000milliseconds = 30 days (which seems like a very long session/authorization time) - Error Response: Omada API returned
errorCode: -1with message"General error."
Potential Causes:
- Invalid/Expired Token: The authorization token might be expired or invalid
- Session Timeout: 30-day authorization might exceed system limits
- API Configuration: Incorrect API endpoint or credentials
- Network/Connectivity: Issues reaching the Omada authentication server
- Rate Limiting: Too many authentication attempts
BTW, Omada Controller v.5.7.6 is really old; you may update to the latest version.
- Copy Link
- Report Inappropriate Content
Regarding the 30-day (2592000000 ms) authorization time, we have been using this setting consistently, and it has been working without any issues. Therefore, we do not believe the session duration itself is the cause.
The "General error" (errorCode: -1) does not occur for all devices. It happens only for certain specific devices, while others are authorized successfully under the same configuration.
- Copy Link
- Report Inappropriate Content
Hi @stha
To understand the situation better, please give us the following info:
1. A screenshot of the Device page of the controller, showing the firmware version of the SDN devices;
2. What kind of controller are you using? What's the firmware version?
3. What configuration are you trying to do? Please describe some backgrounds.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 199
Replies: 3
Voters 0
No one has voted for it yet.