diff --git a/doc.md b/doc.md
index 9c8b3e0d..9b5982ab 100644
--- a/doc.md
+++ b/doc.md
@@ -131,6 +131,7 @@ Core documentation for Qubes users.
  * [GUI Troubleshooting](/doc/gui-troubleshooting/)
  * [Media Troubleshooting](/doc/media-troubleshooting/)
  * [Firewall Troubleshooting](/doc/firewall/#firewall-troubleshooting)
+ * [VPN Troubleshooting](/doc/vpn-troubleshooting/)
 
 ### Reference Pages
 
diff --git a/external/configuration-guides/vpn.md b/external/configuration-guides/vpn.md
index 1f843215..002a28f3 100644
--- a/external/configuration-guides/vpn.md
+++ b/external/configuration-guides/vpn.md
@@ -318,6 +318,4 @@ If you want to update your TemplateVMs through the VPN, you can enable the `qube
 Troubleshooting
 ---------------
 
-* 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.
+See the [VPN Troubleshooting](/doc/vpn-troubleshooting/) guide for tips on how to fix common VPN issues. 
diff --git a/user/troubleshooting/vpn-troubleshooting.md b/user/troubleshooting/vpn-troubleshooting.md
new file mode 100644
index 00000000..67882f7b
--- /dev/null
+++ b/user/troubleshooting/vpn-troubleshooting.md
@@ -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.