502 Bad Gateway on the Public Bug Tracker

Here you can provide suggestions on how to improve the product, website, etc.
Air Force One
Posts: 109
Joined: 6. Oct 2017, 16:54
Primary OS: MS Windows other
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: Windows
Location: Germany

Re: 502 Bad Gateway on the Public Bug Tracker

Post by Air Force One »

klaus wrote: 15. Apr 2024, 16:32 Try clearing the cookies for www.virtualbox.org (some months ago there was a change to the SameSite cookie attribute which should've made things more compatible with the browsers out there, maybe you still have the old state in your cookie collection).
I don't think that this is trouble on the client side, like cookies and so on. As you wrote last year, the cause is in the backend, like a load balancer, a thread pool or some issues with the database. Could it be that yesterday we also had something like this for a short time, and afterward it was gone? Maybe somebody could see something in the logs?
klaus
Oracle Corporation
Posts: 1205
Joined: 10. May 2007, 14:57

Re: 502 Bad Gateway on the Public Bug Tracker

Post by klaus »

Could check the logs... not today, but hopefully in the next days. The load balancer control (which is needed during authentication) is actually relying on cookies, one which is set at the beginning of auth and cleared again when the response has reached the same backend server. It is done to mitigate between the needs of the auth solution (which has to be handled by a single backend server, no matter which one) and spreading the normal application load (which means that every connection goes to a different backend server).
Air Force One
Posts: 109
Joined: 6. Oct 2017, 16:54
Primary OS: MS Windows other
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: Windows
Location: Germany

Re: 502 Bad Gateway on the Public Bug Tracker

Post by Air Force One »

klaus wrote: 16. Apr 2024, 13:37 The load balancer control (which is needed during authentication) is actually relying on cookies, one which is set at the beginning of auth and cleared again when the response has reached the same backend server.
My Firefox is set up to not have any history and so on, it is in permanent private mode. So there should be no cookies and no troubles with cookies. Am I wrong here?
What I also like to tell - the changes in configuration are working. Previously I got this situation more often; now it came first after like 6 months. I just wanted to inform you.
Post Reply