Added "common errors" page

content/faqs/_index.md

@@ -5,18 +5,6 @@ draft: false
 weight: 100
 ---
 
-## Common `docker` permission errors
-
-If you are getting errors like this when running the installer or running the `yams` cli:
-
-```sh
-permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock:
-```
-
-It might mean that you need to reload your user. This is fixed by logging out of your server and logging back in.
-
-This happens because your user needs to be part of the `docker` group in order to be able to execute `docker` without `sudo`
-
 ## I don't want to configure YAMS manually, is there a pre-made configuration?
 
 Yes, but **I do not recommend using this option if this is the first time you configure YAMS.** You can check the instructions here: [Easy mode](/config/easy-mode).
@@ -24,4 +12,3 @@ Yes, but **I do not recommend using this option if this is the first time you co
 ## Why did you choose <this_software> instead of <that_software>?
 
 Because. That's why it's _**opinionated**_, you don't _necessarily_ have to agree with me. This setup is aimed at noobs and first time media server enthusiasts. You can always use my sources and fork the project 🔥
-

content/faqs/common-errors.md

@@ -0,0 +1,61 @@
+---
+title: "Common issues"
+date: 2023-10-22T10:22:29-03:00
+draft: false
+weight: 1
+summary: How to fix common issues with YAMS.
+---
+
+# Docker
+
+## Common `docker` permission errors
+
+If you encounter errors like the one below when running the installer or the `yams` CLI:
+
+```sh
+permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock:
+```
+
+It might indicate that you need to refresh your user permissions. This issue can typically be resolved by logging out of your server and then logging back in.
+
+This problem arises because your user must be part of the `docker` group to execute `docker` commands without using `sudo`.
+
+# qBittorrent
+
+## qBittorrent has suddenly lost its internet connection
+
+Sometimes, Gluetun disconnects with no apparent reason. It usually comes back after a minute or so, but qBittorrent may not recover as expected.
+
+A helpful workaround is to create a cron job that monitors the status of qBittorrent and restarts it if necessary.
+
+To open your crontab, use the following command: `crontab -e`
+
+Now, paste the following line at the bottom:
+
+```bash
+* * * * * /usr/bin/docker exec qbittorrent curl -s https://am.i.mullvad.net/connected || /usr/bin/docker restart qbittorrent
+```
+
+This script will check every minute whether qBittorrent has an internet connection. If it doesn't, the script will automatically restart it.
+
+## qBittorrent is not accessible
+
+If you [configured the VPN](/install/steps/#vpn), go to [Gluetun does not connect](#gluetun-does-not-connect)
+
+# Gluetun
+
+## Gluetun does not connect
+
+After installing YAMS, there are instances when Gluetun fails to connect, resulting in qBittorrent becoming inaccessible.
+
+To debug this issue, start by checking Gluetun's logs:
+
+```bash
+docker logs -n 100 gluetun
+```
+
+This command will display the last 100 lines of the Gluetun logs.
+
+Many of the issues arise due to misconfigurations in your VPN setup. Please review the documentation for your VPN by clicking [here](/advanced/vpn).
+
+Review the logs to try and find a solution. If you require assistance, feel free to join our Matrix chat and ask for help!

content/install/steps.md

@@ -44,7 +44,7 @@ Make sure you can run `docker` **without** `sudo`!
 
 If you run `docker` with `sudo` and another user other than `root` you'll encounter multiple permission errors. You can find instructions on how to run `docker` without `sudo` here: https://docs.docker.com/engine/install/linux-postinstall/#manage-docker-as-a-non-root-user.
 
-If you can run `docker run hello-world` without `sudo`, you can continue. If you encounter any other `docker` issue, go to the [FAQs](/faqs/), there's a section on "Common `docker` permission errors".
+If you can run `docker run hello-world` without `sudo`, you can continue. If you encounter any other `docker` issue, go here: [Common docker permission errors](/faqs/common-errors/#common-docker-permission-errors).
 
 ### Inspecting the `install` script by yourself (optional).