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

    VPN client does not connect to OpenVPN server (error).

    Scheduled Pinned Locked Moved OpenVPN
    5 Posts 3 Posters 680 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.
    • I
      IrixOS
      last edited by IrixOS

      Hi,

      I can't connect to my OpenVPN server. It should work with the current configuration because I have done it before in the far past and it wasn't that hard, unless they changed something overtime.

      This is the error I get, I think this is a general error, which basically means it can be anything. I double checked the basic settings, gone through the manual over and over again. It is quite possible I might have overseen something. I am using a dynamic host name (no-ip) instead of an Interface address (Export key tab).

      It is worth to mention and I included it in another screenshot, the OpenVPN server does not seem to be running, the green start button does not respond. As far as I can remember, this should be on prior connecting.

      0_1530382576793_Screenshot_2018-06-30_18-28-32.png

      0_1530382596458_Error.jpg

      Can you guys help me out? Or can someone give me a lead where to start?

      Other screenshots can be provided if necessary, but please God no,...

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

        As the server is not running it's naturally clear that the client can't connect.

        The OpenVPN log on the server should provide the reason for the server cannot start.

        1 Reply Last reply Reply Quote 0
        • I
          IrixOS
          last edited by

          Hmm, indeed, apparently the error was related to a wrong combination of a network statement and its subnet mask. The tunnel network does not accept /16 so I used /24. Very odd I must say the least. 172.16.1.0/16 is valid one right and therefore should work.

          Thank you

          1 Reply Last reply Reply Quote 0
          • jimpJ
            jimp Rebel Alliance Developer Netgate
            last edited by

            (a) There is no reason to use a /16 for a VPN tunnel network, especially not with topology subnet. You are not going to get 65,500+ clients connected to a single OpenVPN server.

            (b) 172.16.1.0/16 is not a valid network specification, 172.16.0.0/16 is where that /16 starts, which is the cause of that error.

            Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

            Need help fast? Netgate Global Support!

            Do not Chat/PM for help!

            1 Reply Last reply Reply Quote 0
            • I
              IrixOS
              last edited by

              Hmm, yes indeed.

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