Jump to content

Dyon

Members
  • Content Count

    59
  • Joined

  • Last visited

Community Reputation

21 Good

About Dyon

  • Rank
    Advanced Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. The 4.2.5 tag is now online. In Unraid, select my container, select Edit, and change the 'Repository' from 'dyonr/qbittorrentvpn' to 'dyonr/qbittorrentvpn:v4_2_x'
  2. In my opinion a new official release version is not cutting edge, it has been in development for months by the qBittorrent team. I will add a tag for the latest 4.2.x version later. I'll reply to you again later to you know when it's added. I also encourage you to contact your trackers to add to support for qBittorrent 4.3.x
  3. On one if my servers a script checks every hour to see if Jackett has released a new version, which happens quite often since it does index a lot of websites, these websites often maken changes in how items are indexed. So, my code on GitHub is the code of the files and how to build the Docker. The Dockerfile just takes the last release from the Jackett GitHub page. Because of that, I do not need to change the source code to hard code a new release, but only check if they released a new version. That's why there are almost daily updates to the docker, but not the GitHub. I hope it makes sense 😃
  4. I've replied this on Github to you: This shouldn't be possible since the lines that did the checking for the IP range got commented out on commit of the 3rd of August. See lines 26 to 36 in this file: https://github.com/DyonR/docker-Jackettvpn/blob/master/jackett/iptables.sh Please make sure you are using the latest version of the Docker container
  5. Odd, I will look at it in a moment. Does the log of qbittorrentvpn show that the ports got added to the IP tables? Edit: I've just tested this with a nginx webserver (linuxserver/nginx), and it works perfectly fine for me. On the additional dockers, you don't need to change anything about the ports, but only need to know which, so 6077 and 8089. In the qbittorrentvpn Docker, you need to add those as '6077,8089' and also add port mappings. At the bottom of the 'edit' of the qbittorrentvpn Docker select 'Add another Part, Port, Variable, Label or Device' Set the following: Config Type: Port Name: ChannelsDVR Container Port: 8089 Host Port: 8797 (example, change this to the port you like to use, 8089 would also be possible) Connection Type: TCP (doubt you need TCP) Click add, and apply. Also, don't forget to add the '--net=container:qbittorrentvpn' to the other containers. Please check if you did all the steps of this video correctly:
  6. I think this may be related to qBittorrent's settings. Please open the qBittorrent options > BitTorrent > Uncheck Torrent Queueing Also check if the Connections Limits are set properly in the Connection tab, you could increase, double or triple those maybe, or just disable all connections by unchecking it all. Also please verify what qBittorrents connection status is at the bottom like how many DHT nodes you are connected with and if the connection status is green,
  7. Nope. Normally you just install the Docker, set the settings. Add the WireGuard config to the WireGuard folder, with renaming the config 'wg0.conf'. After that you just click the 'WebUI' button in Unraid and you should have a working qBittorrent routed through the WireGuard VPN of your VPN Provider.
  8. @Mattti1912 I sorry, I would love to help you, but I do not see anything wrong with the log files or the configurations. From looking at the log files and you configuration it should be possible to connect to qBittorrent's webui without problems.
  9. I do not see anything wrong in the qbittorrent.log.txt or in the Container log. Does the container keep restarting continuously and you are not able to connect to the Web UI? Is the IP correct that you try to access the container on, also note https:// Just to be sure everything is clean: Stop the container Delete the appdata/qbittorrentvpn/qBittorrent folder (so it will do a full clean config and https install of qBittorrent) Check if the LAN_NETWORK is correct for your IP-range - Try again If it still does not work: Stop the container Delete the appdata/qbittorrentvpn/qBittorrent folder (so it will do a full clean config and https install of qBittorrent) Check if the LAN_NETWORK is correct for your IP-range Edit the container again, click 'show more settings...' and set ENABLE_SSL to no - Try again
  10. Alright, WireGuard seems to be working now, but after qBittorrent starts it seems to crash, which is weird since it's kinda the 2nd last action of the start up script, after that it should keep on checking the connection. Because of this I think qBittorrent might have a corrupted config file. Can you stop the container, and delete `appdata/qbittorrentvpn/qBittorrent/config/qBittorrent.conf` After that, if it still does not work, could you send `appdata/qbittorrentvpn/qBittorrent/data/logs/qbittorrent.log` Warning: This file MIGHT contain sensitive information about your IP (mainly the lines with the text 'Detected external IP:') or the torrent loaded in qBittorrent, so please be careful whens ending this over.
  11. The log says the following: 2020-09-26 16:10:01.325265 [ERROR] WireGuard config filename is not 'wg0.conf' 2020-09-26 16:10:01.342769 [ERROR] Rename /config/wireguard/Europe-NL1.conf to 'wg0.conf' Please rename the file Europe-NL1.conf to wg0.conf and restart the container
  12. What doesn't work exactly? Opening the WebUI? Are you using a bridge network? Can you post the log?
  13. @microbassIf you update the container, the issue should be fixed
  14. A TOML parser might be nice, I also used a JSON parser for reading GitHub releases in the Docker File (jq). But, I only need to read 1 line from the WireGuard config file, for the iptables, so I don't think it would be worth switching. The only inconsistency that I could think of, would be this use-case. However, Mullvad, might be here to blame, since the TOML-spec doesn't give any examples without spaces around '='-signs. I might look into it, but no promises 😉