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

    OpenVPN Remote Access (SSL/TLS + User Auth) stopped working

    Scheduled Pinned Locked Moved 2.2 Snapshot Feedback and Problems - RETIRED
    3 Posts 3 Posters 1.4k 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.
    • C
      cl
      last edited by

      I upgraded to

      2.2-RC (amd64) built on Sun Jan 11 17:57:26 CST 2015 FreeBSD 10.1-RELEASE-p3

      and after that OpenVPN Remote access stopped working. Maybe this excerpt from the log file can help identifying the problem:

      Jan 12 09:55:09 openvpn: user 'XX' could not authenticate.
      Jan 12 09:55:09 openvpn[18274]: XXX.XXX.XXX.XXX:59601 WARNING: Failed running command (–auth-user-pass-verify): external program exited with error status: 1
      Jan 12 09:55:09 openvpn[18274]: XXX.XXX.XXX.XXX:59601 TLS Auth Error: Auth Username/Password verification failed for peer
      Jan 12 09:55:09 openvpn[18274]: XXX.XXX.XXX.XXX:59601 [cl] Peer Connection Initiated with [AF_INET]XXX.XXX.XXX.XXX:59601

      To be sure I also resetted the passwork for user XX, but that had no effect.

      1 Reply Last reply Reply Quote 0
      • P
        phil.davis
        last edited by

        You might have the build where there was a testing password accidentally in the code.
        Try the very latest build. The debug code was removed 19 hours ago, as at time of my posting.

        As the Greek philosopher Isosceles used to say, "There are 3 sides to every triangle."
        If I helped you, then help someone else - buy someone a gift from the INF catalog http://secure.inf.org/gifts/usd/

        1 Reply Last reply Reply Quote 0
        • E
          eri--
          last edited by

          For this issue to be fixed wait for a snapshot of later today.
          The issue has been fixed just now and the status is on #4177

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