After updating the public address to the Load Balancer VIP on Cloud Director, the user interface is no longer accessible
Article ID: 397155
Updated On:
Products
Issue/Introduction
Users observe a continuous spinning logo on the screen, and the browser's developer tools indicate a 502 Bad Gateway error.
In the application log we see the request with an HTTP 204. We see the request reaching the cell, and it returns HTTP 204, this confirms Cloud Director is not at fault.
192.xxx.x.xxx - - [07/May/2025:09:50:18 +0000] "GET /cloudapi HTTP/1.1" 204 0 "https://vcd-loadbalancer-ip/provider/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/135.0.0.0 Safari/537.36" 52
Environment
10.x
Cause
The root cause of the issue was identified as the default header size setting. The new brand of LB FortiADC has this hidden away and is under a section where the default was 8096.
Resolution
By increasing the header size from the default 8096 to 65536, the system was able to handle the necessary header information, and Cloud Director started working as expected.
Feedback
