Re: [PacketFence-users] Captive Portal not accessible

2019-05-03 Thread Eric Rolleman via PacketFence-users
No, haproxy was not started. It was complaining about my server.pem file. I had edited the /usr/local/pf/conf/httpd.conf.d/ssl-certificates.conf with: SSLCertificateFile %%install_dir%%/conf/ssl/server.pem SSLCertificateKeyFile %%install_dir%%/conf/ssl/server.key SSLCertificateChainFile

Re: [PacketFence-users] Captive Portal not accessible

2019-05-02 Thread Thomas OLIVIER via PacketFence-users
Is haproxy started ? My case: tcp    10.22.0.1:443  (registration network) 0.0.0.0:*   LISTEN  103191/*haproxy* Thomas. On 02/05/2019 06:20, Eric Rolleman via PacketFence-users wrote: After I join wifi I am placed in the registration Vlan, however no Captive Portal

[PacketFence-users] Captive Portal not accessible

2019-05-02 Thread Eric Rolleman via PacketFence-users
After I join wifi I am placed in the registration Vlan, however no Captive Portal appears. I can't bring up the Captive Portal page by typing in the URL manually either ( https://). My management interface IP address is 192.168.1.22/16, my registration Vlan interface IP is 10.0.21.252/24 .