-
Notifications
You must be signed in to change notification settings - Fork 21
Understanding error messages
René Vollmer edited this page Mar 11, 2020
·
7 revisions
(First draft, to be continued)
- Library errors
- HTTP errors
- TR-064 errors
- µController errros
See http error messages for an overview. We mostly get 500 errors, when the request is not valid in some way (e.g. asking for details of a device with an unknown MAC address).
From first steps user guide, unless otherwise stated.
Code | Meaning | Note |
---|---|---|
503 | service unavailable | The service may use HTTP status code 503 instead of 401 if too many unauthenticated requests from one client are made |
401 | unauthorized, unknown or obsolete action | |
402 | number of arguments for an action is not as expected or an unexpected argument is used | |
606 | Action not authorized | user is authenticated but has not the needed rights |
866 | second factor authentication required | action needs 2FA (not supported yet) |
867 | second factor authentication blocked | action needs 2FA (not supported yet) |
868 | second factor authentication busy | action needs 2FA (not supported yet) |
For ESPs see here.