Need correct configuration for SSL vHosts



  • I am new to pfSense and Linux.  Please provide detailed answers.

    I installed the vHosts package on my pfSense 2.1.5 RELEASE box.

    I have one WAN with DHCP configuration to the ISP router
    LAN with x.x.x.1 Static IP and OPT1 with x.x.x.3 Static IP on the same subnet

    Computers can ping both IPs In and Out.

    I need to create a vHost wth HTTPS configuration to run on the same pfSense box.  The webGui runs on HTTPS.

    I added the required definitions (Certificate and key) in the vHost create page, but I do not know which port should I use for it to work as HTTPS.

    I tried 443 and user port 8001, but it does not work.  I need the correct port and maybe some Firewall rules.

    If I have to move the webGui to HTTP please advise in detail because I tried to change it on the Advanced Config, but then can not connect.



  • @jetberrocal:

    I am new to pfSense and Linux.  Please provide detailed answers.

    I installed the vHosts package on my pfSense 2.1.5 RELEASE box.

    I have one WAN with DHCP configuration to the ISP router
    LAN with x.x.x.1 Static IP and OPT1 with x.x.x.3 Static IP on the same subnet

    Computers can ping both IPs In and Out.

    I need to create a vHost wth HTTPS configuration to run on the same pfSense box.  The webGui runs on HTTPS.

    I added the required definitions (Certificate and key) in the vHost create page, but I do not know which port should I use for it to work as HTTPS.

    I tried 443 and user port 8001, but it does not work.  I need the correct port and maybe some Firewall rules.

    If I have to move the webGui to HTTP please advise in detail because I tried to change it on the Advanced Config, but then can not connect.

    :-[ I found a way to use HTTP instead of HTTPS with my WebGui.  I needed a firewall rule for my configuration.

    In case someone have similar problem the firewall rule is:
    Allow
    proto IPv4 TCP
    source LAN net
    Port *
    Destination "pfsense IP"
    Port 80 (HTTP)
    Gateway *
    QUeue none
    Squedule "empty"

    Anyway I also change the port from 80 to 9000 for the WebGui, so now I do not need the rule.


  • Banned

    @jetberrocal:

    I found a way to use HTTP instead of HTTPS with my WebGui.

    Congrats on digging holes into your firewall. Sigh…  ::)


Log in to reply