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

    Can't get certificate using haproxy on local network, but can get a certificate if I am using external network

    Scheduled Pinned Locked Moved HA/CARP/VIPs
    5 Posts 2 Posters 339 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.
    • T
      terrorbyte704
      last edited by terrorbyte704

      As the post says, i Followed Lawrence Systems video on setting up a reverse proxy multiple times, but when i tried to make a internal dns to my truenas, it keeps not being certified, its instead keeps showing ixsystems as and local instead of *.mydomain.com, i am not sure what to do, i tried ticking off different checkmarks but still the same problem

      for example i tried to do a local haproxy to my truenas and instead of i am getting this as in the images shows as well as my config
      alt text

      V 1 Reply Last reply Reply Quote 0
      • V
        viragomann @terrorbyte704
        last edited by

        @terrorbyte704 said in Can't get certificate using haproxy on local network, but can get a certificate if I am using external network:

        but when i tried to make a internal dns to my truenas

        This bypasses HAproxy and directs the browser directly to the backend server.

        If you want to use the certificate installed on pfSense and HAproxy point the local DNS to the IP, which the frontend is listening on.
        If you use a public domain, there is no need for a DNS override anyway.

        T 1 Reply Last reply Reply Quote 0
        • T
          terrorbyte704 @viragomann
          last edited by

          @viragomann sorry i meant i setup a dns resolver, so i am able to go to the nas via dns, but it doens't get a dns, i turned off secure dns on my browers

          T 1 Reply Last reply Reply Quote 0
          • T
            terrorbyte704 @terrorbyte704
            last edited by

            @terrorbyte704 to anyone seeing this I was able to solve this problem by setting my dns resolver to my gateway instead of my server (in this case pfsense) i am not sure why i haven't seen anyone say this yet

            V 1 Reply Last reply Reply Quote 0
            • V
              viragomann @terrorbyte704
              last edited by

              @terrorbyte704
              This is, what I was trying to tell you.

              1 Reply Last reply Reply Quote 0
              • First post
                Last post
              Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.