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

    Openvpn client fails to start

    Scheduled Pinned Locked Moved 2.0-RC Snapshot Feedback and Problems - RETIRED
    5 Posts 3 Posters 4.3k 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
      clarknova
      last edited by

      2.0-RC1 (amd64)
      built on Sun Feb 13 23:53:14 EST 2011

      I see the following messages in my system log about 9 times immediately after updating to the RC:

      Feb 14 00:14:31	check_reload_status: syncing firewall
      Feb 14 00:14:31	php: : WARNING! Configuration written on bootup. This can cause stray openvpn and load balancing items in config.xml
      Feb 14 00:14:31	check_reload_status: syncing firewall
      Feb 14 00:14:30	php: : WARNING! Configuration written on bootup. This can cause stray openvpn and load balancing items in config.xml
      

      I had openvpn running as a client, connecting to a remote server. It worked until the system update, but not since. Status | Services says openvpn is not running and I have not access to the remote network.

      db

      1 Reply Last reply Reply Quote 0
      • AhnHELA
        AhnHEL
        last edited by

        Check your OpenVPN logs, does it give you this error?

        Feb 14 01:59:29    openvpn[62233]: Use –help for more information.
        Feb 14 01:59:29    openvpn[62233]: Options error: Bad local port number: 0

        http://forum.pfsense.org/index.php/topic,33277.0.html

        AhnHEL (Angel)

        1 Reply Last reply Reply Quote 0
        • C
          clarknova
          last edited by

          Indeed.

          db

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

            I'm looking into a fix… for now you can get around it by putting in a distinct, random port number in the 'local port' box for each client.

            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
            • C
              clarknova
              last edited by

              Thanks, that worked. I'll follow the other thread.

              db

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