New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Connection keeps restarting (firewalled network) #180
Comments
Few things could be happening. Since it seems to only occur when you're on client's sites, it's likely their firewall or NAT router is killing your connection and sending a reset. For more information, try running the openvpn server with more verbosity, something like:
And grab the OpenVPN server log file with:
If both the client and server get a connection reset at the same time and neither sent it, it's likely to be a corporate firewall complicating your situation. |
@kylemanna
It goes on with the same segment between resets. So what does that mean? Is there any way to avoid those resets? corresponding logs from client, in case they are useful
|
I'm guessing that since they both client and server appear to see resets at the same time and neither appear to send them, that the firewall is sending them. This is supported by the same server and client working on a different network. You might try confirming this isn't related to openvpn by running opensshd on port 443/tcp and connecting to it with an ssh client. I suspect the ssh connection will reset as well, running Another option might be to try different ports or udp to try and dodge the firewall rules. There maybe some stateful inspection on port 443/tcp expecting to see the beginning of HTTPs negotiation, and when there isn't any it kills it. I'd encourage you to try another port if any are open. Probably need to do some port scanning of a remote host you own with a a few ports open to test. As always, using udp if possible is recommended. :) |
Thanks for the help. So any quick way to check ports that are open and accept UDP? |
Not that I know of off the top of my head. Could try setting up a openvpn container and using iptables port redirects to redirect a ton of ports to your server and check if any work. |
@kylemanna client -> server ( with openvpn container running and listening on 1001 )
from server -> client
Still openvpn never gets to connect and process keeps restarting. |
Perhaps the firewall is detecting OpenVPN. I've seen similar things by the great firewall of China. ExpressVPN has a modified OpenVPN client and server that managed to succeed. That's all I can think of other then trying to reach the network admins on the network with issues. |
Closing due to no updates in a few months. |
I bump into this topic after I got In my situation it was, that openVPN was connected twice. One on the one computer, and other one (which keeps disconnecting) on another one. It was set up like that on server. Maybe this will helps somebody - you can not have two connections to server. |
What a lifesaver! |
Just to be sure: An OpenVPN server does only allow one connection at a time, no matter how configured? |
I've got two simultaneous connections all day (TCP/443) and no issues. (Phone/PC) |
Hi.
I'm using the docker image for more than a year now ( thanks for your work ).
Works perfectly fine, except when I go to work on big corporations where their networks are firewalled. ( I'm a contractor so I go to many different client sites )
I've tried to change the config to listen to TCP, and then have the docker container mapped from port 80 or 443 to 1194.
What happens ( I tried that at least in two different companies ) is that I can see in the logs that the connections are being reset and it's stuck in a loop of trying to connect.
I use tunnelblick and
OSXmacOSI'll paste the logs here, in case it helps.
( actual IP masked with xxx.xxx.xxx )
The part after
keeps looping again and again until I stop it.
Any idea on how to make it work?
My networks knowledge stops at port mapping and selecting the protocol :/
The text was updated successfully, but these errors were encountered: