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

Setting up HAProxy for first time with SSL through certbot/letsencrypt

Scheduled Pinned Locked Moved Cache/Proxy
2 Posts 1 Posters 268 Views
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.
  • B
    Berzerk
    last edited by Aug 7, 2020, 8:24 PM

    Hello everyone.
    I've been using pfSense for a couple of months now, and just routing traffic to one ip which is hosting several websites via apache2 vhosts.
    I'm wanting to switch putting the sites on individual vMachine Hosts with unique IPs.

    I've followed various tutorials on how to do this, but I can't seem to get it to route traffic correctly. It is like when I set a condition, it just ignores it and sends it to the base site no matter what.

    Currently I am trying it out with a Emby server on one vmachine, and a website on another, just until I get it all working smoothly. I'm looking to have the vmachines handle the SSL, not pfSense, so I also need to set it up so that certbot can get passed through correctly for certification.

    If anyone can direct me to a guide that is up to date with the latest versions of haproxy and pfsense, that would be appreciated. Otherwise, I could give more details/ screen shots of exactly how I have it setup now.

    1 Reply Last reply Reply Quote 0
    • B
      Berzerk
      last edited by Aug 12, 2020, 10:44 PM

      Good news, I got it working. . . mostly. Found a setup guide that showed me what I was doing wrong.

      Only have one small issue left.
      I can't get Emby to work on SSL. I have a certificate setup, but, I get this error in my browser when going https. (http works fine.)

      R_END_OF_FILE_ERROR

      From searching the web, it is common for proxies to give this error, but I can't figure out what I need to change if haproxy to correct it.
      Emby is using a letsenecrypt certificate, and is is running remote access through 443.

      Any help would be appreciated.

      1 Reply Last reply Reply Quote 0
      2 out of 2
      • First post
        2/2
        Last post
      Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.
        This community forum collects and processes your personal information.
        consent.not_received