Skip to content

Authorization issues

Service returns HTTP 503 ServiceUnavailable

Problem

Authorization service returns HTTP 503 Service Unavailable error to all request. The response contains below message in the body:

Error calling Authorization server.Status code: ServiceUnavailable, Url: {ServerUrl} , Error: Error on startup, see health checks for details.

Solution

As described by the error, check the response from the health checks endpoint. Usually the error is related to connectivity problems with the message bus. Typical causes of the problem:

  • Misconfiguration in the connection settings: URI, user name and password.
  • Network errors: server is not reachable.
  • RabbitMQ is not working properly, allows to start the connectivity but fails before accepting to complete the connection; causing an error in the caller. Check health on RabbitMQ.
  • If security is stored in containers (ECS) message bus will notify RabbitMQ that the queues and exchanges are going to be temporal but RabbitMQ will not change his topology unless you delete the related queues and exchanges and re-create them again.