Navigation

    Netgate Discussion Forum
    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search

    Squid Reverse proxy HTTPS separate subdomains without wildcard SSL

    Cache/Proxy
    1
    1
    821
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • K
      Kerat last edited by

      hello, I am in the middle of implementing a reverse proxy to make a few disparate internal sites available on the public Internet and SSL secure it.  3 of the sites already connect via HTTPS internally.  The fourth website is running only on HTTP.  I setup a let's encrypt Acme client on my pfsense firewall and was able to get Squid reverse proxy to use it.  I was able to get one of the HTTPS internal web services working using the following URI format:
      https://sub-domain.domain.com/service

      Another of the HTTPS internal web services and the HTTP website seem to hiccup when using the above URI format.  When navigating in their sites the absolute URL links are overwriting my URI to: 
      https://sub-domain.domain.com/sub-containter
      when it should be configured this way:
      https://sub-domain.domain.com/service/sub-containter

      I was hoping to be able to get around this problem by using the separate subdomains for each of the 4 sites instead of a /service sub directory.  the URI format would then look like this:

      https://sub-domain2.domain.com

      I created a Cname record on my public DNS for sub-domain2.domain.com and pointed it to sub-domain.domain.com.  now i seem to be able to get there but i do see that i have a SSL mismatch.  Let's Encrypt does not support SSL wildcards.  I would like to stick with Let's Encrypt.  Is it possible to request that Squid reverse proxy for pfsense be configured such that we can override the SSL certificates listed in the "General - Squid Reverse HTTPS Settings" menu with the appropriate subdomain SSL in the "mappings - group name" menu?  this would allow me to continue using Let's encrypt and not have to worry about a Wildcard SSL.

      1 Reply Last reply Reply Quote 0
      • First post
        Last post

      Products

      • Platform Overview
      • TNSR
      • pfSense
      • Appliances

      Services

      • Training
      • Professional Services

      Support

      • Subscription Plans
      • Contact Support
      • Product Lifecycle
      • Documentation

      News

      • Media Coverage
      • Press
      • Events

      Resources

      • Blog
      • FAQ
      • Find a Partner
      • Resource Library
      • Security Information

      Company

      • About Us
      • Careers
      • Partners
      • Contact Us
      • Legal
      Our Mission

      We provide leading-edge network security at a fair price - regardless of organizational size or network sophistication. We believe that an open-source security model offers disruptive pricing along with the agility required to quickly address emerging threats.

      Subscribe to our Newsletter

      Product information, software announcements, and special offers. See our newsletter archive to sign up for future newsletters and to read past announcements.

      © 2021 Rubicon Communications, LLC | Privacy Policy