2020-10-30 10:07:40 -04:00
---
2021-03-13 13:06:18 -05:00
lang: en
2020-10-30 10:07:40 -04:00
layout: doc
2021-06-16 22:56:25 -04:00
permalink: /doc/vpn-troubleshooting/
2021-03-13 13:06:18 -05:00
ref: 240
2021-07-09 08:10:44 -04:00
title: VPN troubleshooting
2020-10-30 10:07:40 -04:00
---
2021-03-13 12:03:23 -05:00
## Tips
2020-10-30 10:07:40 -04:00
2020-11-01 08:50:05 -05:00
* If using qubes-vpn, check the VPN service's log in the VPN VM by running:
2021-03-13 12:03:23 -05:00
2020-10-30 10:07:40 -04:00
~~~
sudo journalctl -u qubes-vpn-handler
~~~
2021-03-13 12:03:23 -05:00
* Always test your basic VPN connection before adding scripts.
2020-10-30 10:07:40 -04:00
* Test DNS: Ping a familiar domain name from an appVM. It should print the IP address for the domain.
* Use `iptables -L -v` and `iptables -L -v -t nat` to check firewall rules. The latter shows the critical PR-QBS chain that enables DNS forwarding.
2021-03-13 12:03:23 -05:00
## VPN does not reconnect after suspend
2020-11-01 08:50:05 -05:00
2021-03-13 12:03:23 -05:00
This applies when using OpenVPN.
2020-11-01 08:50:05 -05:00
2021-03-13 12:03:23 -05:00
After suspend/resume, OpenVPN may not automatically reconnect. In order to get it to work, you must kill the OpenVPN process and restart it.
2020-10-30 10:07:40 -04:00
2021-03-13 12:03:23 -05:00
## VPN stuck at "Ready to start link"
2020-10-30 10:07:40 -04:00
2021-03-13 12:03:23 -05:00
After setting up OpenVPN and restarting the VM, you may be repeatedly getting the popup "Ready to start link", but the VPN isn't connected.
2020-10-30 10:07:40 -04:00
2021-03-13 12:03:23 -05:00
To figure out the root of the problem, check the VPN logs in `/var/logs/syslog` . The log may reveal issues like missing OpenVPN libraries, which you can then install.