Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Search
    • Register
    • Login
    Introducing Netgate Nexus: Multi-Instance Management at Your Fingertips.

    https not working with wireguard

    Scheduled Pinned Locked Moved WireGuard
    5 Posts 2 Posters 455 Views 2 Watching
    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.
    • D
      DD4711
      last edited by

      Hello,

      I have a strange problem with one wireguard client connected to my home.

      There are several clients connecting via wireguard to the home pfsense. With one I have problems at the moment. All other run normal. The wireguard connection is configured to route all traffic to pfsense.

      The client with the problems is a Linux Mint Computer. Sometimes everything seems to be good for a while. But then I have trouble while browsing:

      Websites in my home network and internet cannot be accessed via HTTPS.
      Firefox shows "TLS Handshake is being performed" (translated to english). Then timeout.

      Websites in my home network and internet can still be accessed via HTTP.

      Currently I have no idea what to search for to narrow down the problem.

      I'd really appreciate any tips.

      M 1 Reply Last reply
      Reply Quote 0
      • M
        mcury Rebel Alliance @DD4711
        last edited by

        @DD4711 Try settings this at the client side:

        [Interface]
        PrivateKey = CLIPPED
        Address = CLIPPED
        MTU = 1400

        If that doesn't work, try 1300 just to confirm if the problem is indeed MTU.
        Then, I'll help you to identify the correct value.

        dead on arrival, nowhere to be found.

        D 2 Replies Last reply
        Reply Quote 0
        • D
          DD4711 @mcury
          last edited by

          @mcury Thank you for your help! It seems to work after adding the MTU value and reconnect. I'll test it for while and post the result.
          😀

          1 Reply Last reply
          Reply Quote 0
          • D
            DD4711 @mcury
            last edited by

            @mcury Sorry for late answer, i was off for some days.
            Seems to work with MTU 1400.
            Could an ISP change on client side be respnosible for that?

            M 1 Reply Last reply
            Reply Quote 0
            • M
              mcury Rebel Alliance @DD4711
              last edited by

              @DD4711 said in https not working with wireguard:

              Sorry for late answer, i was off for some days.

              np.

              Could an ISP change on client side be respnosible for that?

              yeap.

              dead on arrival, nowhere to be found.

              1 Reply Last reply
              Reply Quote 0

              Hello! It looks like you're interested in this conversation, but you don't have an account yet.

              Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

              With your input, this post could be even better 💗

              Register Login
              • First post
                Last post
              Copyright 2026 Rubicon Communications LLC (Netgate). All rights reserved.
              Privacy Policy · Cookie Policy