mirror of
https://github.com/QubesOS/qubes-doc.git
synced 2024-12-25 23:39:37 -05:00
Merge branch 'PROTechThor-vpn-troubleshooting'
This commit is contained in:
commit
6fd8d400fe
1
doc.md
1
doc.md
@ -131,6 +131,7 @@ Core documentation for Qubes users.
|
|||||||
* [GUI Troubleshooting](/doc/gui-troubleshooting/)
|
* [GUI Troubleshooting](/doc/gui-troubleshooting/)
|
||||||
* [Media Troubleshooting](/doc/media-troubleshooting/)
|
* [Media Troubleshooting](/doc/media-troubleshooting/)
|
||||||
* [Firewall Troubleshooting](/doc/firewall/#firewall-troubleshooting)
|
* [Firewall Troubleshooting](/doc/firewall/#firewall-troubleshooting)
|
||||||
|
* [VPN Troubleshooting](/doc/vpn-troubleshooting/)
|
||||||
|
|
||||||
### Reference Pages
|
### Reference Pages
|
||||||
|
|
||||||
|
4
external/configuration-guides/vpn.md
vendored
4
external/configuration-guides/vpn.md
vendored
@ -318,6 +318,4 @@ If you want to update your TemplateVMs through the VPN, you can enable the `qube
|
|||||||
Troubleshooting
|
Troubleshooting
|
||||||
---------------
|
---------------
|
||||||
|
|
||||||
* Always test your basic VPN connection before adding scripts.
|
See the [VPN Troubleshooting](/doc/vpn-troubleshooting/) guide for tips on how to fix common VPN issues.
|
||||||
* 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.
|
|
||||||
|
31
user/troubleshooting/vpn-troubleshooting.md
Normal file
31
user/troubleshooting/vpn-troubleshooting.md
Normal file
@ -0,0 +1,31 @@
|
|||||||
|
---
|
||||||
|
layout: doc
|
||||||
|
title: VPN Troubleshooting
|
||||||
|
permalink: /doc/vpn-troubleshooting/
|
||||||
|
---
|
||||||
|
|
||||||
|
# VPN Troubleshooting Guide #
|
||||||
|
|
||||||
|
## Tips
|
||||||
|
|
||||||
|
* If using qubes-vpn, check the VPN service's log in the VPN VM by running:
|
||||||
|
~~~
|
||||||
|
sudo journalctl -u qubes-vpn-handler
|
||||||
|
~~~
|
||||||
|
* Always test your basic VPN connection before adding scripts.
|
||||||
|
|
||||||
|
* 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.
|
||||||
|
|
||||||
|
## VPN does not reconnect after suspend
|
||||||
|
|
||||||
|
This applies when using OpenVPN.
|
||||||
|
|
||||||
|
After suspend/resume, OpenVPN may not automatically reconnect. In order to get it to work, you must kill the OpenVPN process and restart it.
|
||||||
|
|
||||||
|
## VPN stuck at "Ready to start link"
|
||||||
|
|
||||||
|
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.
|
||||||
|
|
||||||
|
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.
|
Loading…
Reference in New Issue
Block a user