Topic: OpenVPN-bridge error - read UDPv4: Connection reset by peer (WSAECONNRESET)

[pwgsc1]

Hi,

Getting this error when I try to login to OpenVPN. 

***Sun Feb 21 13:33:31 2010 read UDPv4: Connection reset by peer (WSAECONNRESET) (code=10054)

I thought it might be the way I setup the Server so I took another Server and followed the installation instructions to a T and am getting the exact same error on the second server.

- using PHPki to create the certificates
- Using XP from VirtualBox to  test
- Using OpenVPN GUI 1.03 as the client
- Fully updated SME Server

I did a search on the web and the only thing I could find was that I should open a UDP port. I assume if that was the case, the instructions would say so.

Thanks,

Craig

[pwgsc1]

More Info..

From the OpenVPN-Bridge Menu I click on the  "Display Connected Clients" button on the Bridged OpenVPN daemon configuration screen it says  "an error occurred while connecting to the manager. Check the Service is running"

When I run the:   tailf  /var/log/openvpn-bridge/current  command  here's the output...

Sun Feb 21 14:18:58 2010 OpenVPN 2.1_rc15 i386-redhat-linux-gnu [SSL] [LZO1] [EPOLL] built on Oct 25 2009
Sun Feb 21 14:18:58 2010 MANAGEMENT: TCP Socket listening on 127.0.0.1:11194
Sun Feb 21 14:18:58 2010 NOTE: when bridging your LAN adapter with the TAP adapter, note that the new bridge adapter will often take on its own IP address that is different from what the LAN adapter was previously set to
Sun Feb 21 14:18:58 2010 NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables
Sun Feb 21 14:18:58 2010 Cannot load DH parameters from pub/dh.pem: error:0906D06C:PEM routines:PEM_read_bio:no start line
Sun Feb 21 14:18:58 2010 Exiting

Hope it helps

[pwgsc1]

Hi,

After reading another post concerning OpenVPN is caused a spark and after rereading the instructions........I paid attention to the graphics.  When I copied the "Certificates" I did not copy the BEGIN................  and END............ parts.     Once I replaced them with the FULL copy of the certificate.........BAM!!   It works like a charm.

I only hope that someone reads this and learns from my mistake.

Thanks,

Craig