"
This is a really big problem for me.
I cannot continue to work with OPNsense like this.
Is there really noone who can help here?
I cannot continue to work with OPNsense like this.
Is there really noone who can help here?
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Pages1
#2
18.1 Legacy Series / HaProxy Related server item not found
June 04, 2018, 10:57:58 AM
I am using Opnsense in version 18.1.9-amd64.
When i try to create a new Backend Pool and then try to select a server i always get "Related server item not found". So i can select it but when i try to save i get this error message.
The name of my "Real Server" is "blogctsrvde". So i have no special characters there.
In an older version of opnsense i never had this problem.
So a fix for that would be really important for me. I currently cannot add any backend pools.
When i try to create a new Backend Pool and then try to select a server i always get "Related server item not found". So i can select it but when i try to save i get this error message.
The name of my "Real Server" is "blogctsrvde". So i have no special characters there.
In an older version of opnsense i never had this problem.
So a fix for that would be really important for me. I currently cannot add any backend pools.
#3
18.1 Legacy Series / Re: Update to 18.1 breaks requests
May 08, 2018, 11:29:40 AMAll 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.
#4
18.1 Legacy Series / Update to 18.1 breaks requests
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:
The resulting response in the case of an 400 looks like this:
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?
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?
Pages1
