[Solved] Captive Portal https Problem (works with Http)
-
Hi,
A common name of one word ?
Normally, it should be "CapAdmins.Simulation.com".At least, true (trusted) certificates should be "Simulation.com" and/or "CapAdmins.Simulation.com".
I'm using a certificate from the ACME package. Just plain rocks.
For the DNS, the Resolverw as activated by default, never touched it. I added a host override like
portal brit-hotel-fumel.net 192.168.2.1
where 192.168.2.1 is my captive portal NIC and portal..brit-hotel-fumel.net the common name of the cert (I own brit-hotel-fumel.net of course). -
here i changed to the followings :
Cert commun name : CapAdmins.Simulation.com
https Server name : CapAdmins.Simulation.com
DNS resolution CapAdmins : 10.1.10.1 (the captive portal interface) with the domain : Simulation.com
Still problem :/
-
When you connected your device to the captive portal interface, could you resolve :
CapAdmins.Simulation.com ?
It should return "10.1.10.1"And your cert contains "CapAdmins.Simulation.com" ?
And what do you mean by "problems" ?
Any portal and captive webs server logs ?You use the default captive portal login page, right ?
-
yes the default web page.
and yes for the certificate (name and also commun name)
yes it resolves with 10.1.10.1 for the logs i'll get them right away for u
Edit : The logs are for authentication i dont even get there i get "bad gateway" in microsoft edge, and "The page isn't redirecting properly" with firefox
Edit 2 : I tried the host override thing like u nothing changed
-
No clues from me.
Witrhout further details, I'll go for a VLAN issue. -
Thanks a lot i guess it might be related to that…
can u like test it ? if you have some time
-
…
can u like test it ? if you have some timeWell, I'm using the captive portal for the last 10 years or so.
I guess tests are over for me ;) -
you mean its working with vlans ? the https redirection works correctly if the interface is a vlan interface in ur case ?
-
Never used vlan's.
Portal has a dedicated NIC. -
Captive portal doesn't care if it is on a VLAN interface.
-
solved : i have to not use cap letters