guillaumedsde / alpine-qbittorrent-openvpn

qBittorrent docker container with OpenVPN client running as unprivileged user on alpine linux
https://guillaumedsde.gitlab.io/alpine-qbittorrent-openvpn/
GNU General Public License v3.0
215 stars 39 forks source link

No webUI in synology #67

Open HiiiiiHa opened 3 years ago

HiiiiiHa commented 3 years ago

Information

I was able to confire and run the container, looks like connection to MULLVAD is OK But Web UI does not show up

Current setup

Synology NAS DS216+II Latest docker image

docker-compose.yml file or docker run command

I do not have docker compose but directly using the synology docker app

volumes:
  - "Download:/downloads"
  - "docker/qtorrent:/config"
environment:
  - OPENVPN_PROVIDER=MULLVAD
  - OPENVPN_CONFIG=fr_all
  - OPENVPN_USERNAME=***********
  - OPENVPN_PASSWORD=m
  - PUID=1026
  - PGID=1000
  - LAN=192.168.0.0/16
ports:
  - "9092:8080"
cap_add:
  - NET_ADMIN
image: guillaumedsde/alpine-qbittorrent-openvpn:latest

NAS2

Logs: Logs2.xlsx

HiiiiiHa commented 3 years ago

tried by directly providing openvpn and crt files with OPENVPN_CONFIG= but still web ui is not accessible

Callisbot commented 3 years ago

I am already using port 8080 for another container, so I would like to do exactly what you are attempting by forwarding port 8080 to something else. In linuxserver.io's container for qbittorrent, they talk about why it's not that simple

I don't have a solution for you, but I hope this helps.

EDIT: Add "- QBT_WEBUI_PORT=9092" under environment and change "9092:8080" to "9092:9092"

istbarp commented 3 years ago

Try running the following after the start of the container;

sudo iptables -t nat -F || iptables -t nat -X

darkxfuneral commented 3 years ago

I have the same issue. I did change "8080:8080" to "9092:9092" also changed "QBT_WEBUI_PORT=8080" to 9092 but still no WebUI. the connection is OK. Noone has a solution yet?!

istbarp commented 3 years ago

I have the same issue. I did change "8080:8080" to "9092:9092" also changed "QBT_WEBUI_PORT=8080" to 9092 but still no WebUI. the connection is OK. Noone has a solution yet?!

Hi, I indeed found a solution , atleast for my issue.

My issue was with the LAN_NETWORK. My server, which was hosting the container was using 192.168.50.XX and the container LAN_NETWORK was set to 192.168.1.0/24 Setting the LAN_NETWORK variable properly, to 192.168.50.0/24 solved my issue with the container.

guillaumedsde commented 2 years ago

Hi, is anyone still having this issue?

adamporter1 commented 2 years ago

Hi Guillaume! Thanks so much for sharing your work, it looks great! I'm so close to getting it working I think, but running into a similar problem here. Viewing the logs, it looks like the OpenVPN is running (not sure about qbittorrent.) But I can't connect to the web interface. I am configuring the container like this:

alpine-qbittorrent-openvpn:
    volumes:
        - "/volume1/Downloads/:/downloads"
        - "/volume1/apps/alpine-qbittorrent-openvpn/:/config"
        - "/etc/localtime:/etc/localtime:ro"
    environment:
        - OPENVPN_PROVIDER=WINDSCRIBE
        - OPENVPN_CONFIG=NewJersey-Situation-tcp
        - OPENVPN_USERNAME=xx
        - OPENVPN_PASSWORD=xx
        - PUID=1027
        - PGID=100
        - LAN=192.168.0.0/16
    ports:
        - "8081:81"
    cap_add:
        - NET_ADMIN
    image: guillaumedsde/alpine-qbittorrent-openvpn:latest

and I'm seeing these errors amongst all the VPN messages, possibly it keeps dying and restarting?

alpine-qbittorrent-openvpn_1 | 2021-09-16 21:00:53 [ewr-181.windscribe.com] Peer Connection Initiated with [AF_INET]173.205.85.163:1194 alpine-qbittorrent-openvpn_1 | 2021-09-16 21:00:54 WARNING: You have specified redirect-gateway and redirect-private at the same time (or the same option multiple times). This is not well supported and may lead to unexpected results alpine-qbittorrent-openvpn_1 | 2021-09-16 21:00:54 Outgoing Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key alpine-qbittorrent-openvpn_1 | 2021-09-16 21:00:54 Incoming Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key alpine-qbittorrent-openvpn_1 | 2021-09-16 21:00:54 ERROR: Cannot ioctl TUNSETIFF tun: Operation not permitted (errno=1) alpine-qbittorrent-openvpn_1 | 2021-09-16 21:00:54 Exiting due to fatal error alpine-qbittorrent-openvpn_1 | 2021-09-16 21:00:55 Note: Treating option '--ncp-ciphers' as '--data-ciphers' (renamed in OpenVPN 2.5). alpine-qbittorrent-openvpn_1 | 2021-09-16 21:00:55 OpenVPN 2.5.2 x86_64-alpine-linux-musl [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [MH/PKTINFO] [AEAD] built on May 4 2021 alpine-qbittorrent-openvpn_1 | 2021-09-16 21:00:55 library versions: OpenSSL 1.1.1l 24 Aug 2021, LZO 2.10

darkxfuneral commented 2 years ago

I have the same issue. I did change "8080:8080" to "9092:9092" also changed "QBT_WEBUI_PORT=8080" to 9092 but still no WebUI. the connection is OK. Noone has a solution yet?!

Hi, I indeed found a solution , atleast for my issue.

My issue was with the LAN_NETWORK. My server, which was hosting the container was using 192.168.50.XX and the container LAN_NETWORK was set to 192.168.1.0/24 Setting the LAN_NETWORK variable properly, to 192.168.50.0/24 solved my issue with the container.

thanks for your reply, My LAN network is Okay and set to LAN=10.10.0.0/16, but still no connection to the web interface.

jonk999 commented 2 years ago

In the General Settings of the container on the Synology, try ticking the checkbox for 'Execute container using high privelege'