HTTP 403 Forbidden when going through LB
search cancel

HTTP 403 Forbidden when going through LB

book

Article ID: 220423

calendar_today

Updated On:

Products

Clarity PPM On Premise Clarity PPM SaaS

Issue/Introduction

Some scenarios below:

  • After migration to MS Azure, we are able to connect directly to Clarity server but not via load balancer (LB).
  • We are getting error pop-up: [en - Unable to process request - Server or Network error]
  • In Dev Tools we can see error HTTP 403 Forbidden
  • This can manifest with other setups - on premise and with other cloud vendors such as AWS or Google Cloud
  • There can be issues working with Modern UX. Logging into it, updating instances etc.
  • Browser trace shows POST requests getting blocked

Resolution

  • The issue is not with Clarity product but with Azure/Network configuration, which out of scope for support
  • Our suggestion would be to work with Microsoft Support and IT team to use wireshark or similar to trace where exactly (at which layer) the HTTP 403 is thrown
  • Check load balancer logs.