Archive > 20.1 Legacy Series

400 Bad Request + CARP

(1/1)

npiersma:
Dear all,

I encountered the following issue in OPNSense 19.7 & 20.1. It may not be an issue at all, but I am unsure why it is happening. It just could be by design, but then it was never documented. At least, I couldn't find it.

I am running a fully working CARP setup. Installed the CA certificates and selected that certificate to connect to the web interface.

The result it the following;
1. Connecting to the shared CARP public IP addresses work fine (of course certificate warning appears)
2. Connecting to the hostname mapped to the shared IP address works fine. No issue with certificate warning (as expected)
3. Connecting to the hostname mapped to the primary public IP address returns "400 Bad Request".

I would expect, connecting to the primary hostname would work the same as accessing the shared one.

Any clarification is more than welcome.

Cheers
Niels

npiersma:
Ignore post, our pfsense is suffering from the same headache ;)

Navigation

[0] Message Index