OPNsense Forum

Archive => 18.1 Legacy Series => Topic started by: dschilling on May 08, 2018, 11:10:38 am

Title: Update to 18.1 breaks requests
Post by: dschilling on May 08, 2018, 11:10:38 am
I have an OPNsense Setup where three installations are working together.
Our DNS Record points to all three of these installations so that we have a dns load balancing.
We use HaProxy on OPNsense to proxy the requests to our application servers.

I updated two of these installations from version 17.7.12_1-amd64 to 18.1.7-amd64.
After the update some of our requests start failing.
It is reproducable if i do a lot of requests in parallel to one of the OPNsense installations and it only fails if i send the requests to one of the updated installations.
Some of the requests then start failing with a Status Code of 400 or 502.

The resulting response in the case of an 400 looks like this:

Code: [Select]
<html><body><h1>400 Bad request</h1>
Your browser sent an invalid request.
</body></html>

The resulting response in the case of an 400 looks like this:

Code: [Select]
<html><body><h1>502 Bad Gateway</h1>
The server returned an invalid or incomplete response.
</body></html>

Running the same requests to the not updated OPNsense installation works without any problems.

Is there something in OPNsense 18.1 that changed, that may have produced this problem?
Title: Re: Update to 18.1 breaks requests
Post by: dschilling on May 08, 2018, 11:29:40 am
I just compared the HAProxy config of an updated installation with a not updated installation.

All previously selected servers in the Backend Pools are not selected anymore for the Backend Pool. But strangely most of the requests still work. I also cannot select any server there although there are servers configured in the "Real Servers" tab. So there seems to be some kind of bug, that does not let me select my servers.

The same thing is showing up in "Public Services". There all my previously selected Rules are gone and i cannot assign any rule there because it shows me no rule there to select  although i have created some rules.


Edited: I just figured out that an update to 18.1.7_1-amd64 fixed this issue. The issue described above still remains.