Page 1 of 1

HTTP-Status 401: Unauthorized - User could not be authorized

PostPosted: Tue Apr 09, 2019 3:23 pm
by Bernd Welter
Hi there,

quite often cloud users face the error message "HTTP-Status 401: Unauthorized - User could not be authorized."

There are several potential reasons and countermeasures for this behaviour:
  • You didn't try to authenticate. Congratulations: our cloud services require username and password. Without them you will not gain access.
    Countermeasure: send a token. If you don't have one: register for a trial and you get one ;-)
  • You tried to authenticate. So you sent username and password but still don't get access?
    • Maybe the token you use has expired? For example you used the token successful few weeks after registering as test user and now it doesn't work anymore?
      Countermeasure: get in touch with your sales representative to prolong it.
    • The token did work on service alpha but does not work on service beta. E.g. it works for TEST and INTEGRATION but not for PRODUCTION? A valid token grants access to some or even all cloud services. Maybe your token has never been activated for the service you couldn't connect to?
      Countermeasure: get in touch with sales.
Best regards,

Re: HTTP-Status 401: Unauthorized - User could not be author

PostPosted: Wed Apr 10, 2019 10:40 am
by Oliver Heilig

you can check if your token has access to a service here:

https://xserverinternet.azurewebsites.n ... index.html

These rights also apply to API version 2 services. ... formation/