Can't access webUI

[tessierp]

No description provided.

[tessierp]

The service appears to start however, I am unable to access the webui externally. I did a curl on the localhost 8080 and able to see the login page however I am unable to get anything externally and tried various ports just in case 8080 was used.

[tessierp]

Update on this situation.

In my docker-compose.yml, I set both the internal and external ports to 6080 and then deployed the service. The container initially fails once because it is missing something, I'm guessing config files from the logs and then it restarts as per my fail rules and then it is OK. Then I looked at qBittorrent.conf in the config folder and the port was set to 8080. I scaled down the server (stopped it) and set WebUI\Port=6080 and then scaled back up (started) the service. That value changed back to 8080.

So it seems there is no way to change this and what is really missing is an ENVIRONMENT variable to allow us to set the port. I already have another service on this machine at 8080. It would be super awesome if in the future you could add an environment variable to set the port internally as well.

Also, as I said before, even if I set ports 8080:8080 or 6080:8080, I'm unable to reach the WebUI so there is something else that is wrong. Here is my compose file :

``
version: '3.8'
services:
qbittorrent-openvpn:
deploy:
restart_policy:
condition: any
max_attempts: 5
image: guillaumedsde/alpine-qbittorrent-openvpn:latest
cap_add:
- NET_ADMIN
networks:
- tools-net
volumes:
- /mnt/Downloads/torrents/qbittorrent:/data
- qbittorrent-openvpn-config:/config
- /etc/localtime:/etc/localtime:ro
environment:
- OPENVPN_PROVIDER=PIA
- OPENVPN_CONFIG=ca_toronto
- PGID=1000
- PUID=1000
- OPENVPN_USERNAME=xxxxx
- OPENVPN_PASSWORD=xxxxx
- LAN=192.168.20.0/23
ports:
- 6080:8080

networks:
tools-net:
driver: overlay
attachable: true

volumes:
qbittorrent-openvpn-config:
external: true
``

I apologize in advance, the code insert seems to cancel the indentation....

[tessierp]

Tried the new release.. No change, still can't access the webUI if I map 6080->8080

[darkxfuneral]

an unsolvable problem. same here for a long time :-(

[chrisdowey]

There is already a config value to control this, I tested out the following and it worked for me:
docker run -d --cap-add=NET_ADMIN \ -v /path:/downloads \ -v /configpath:/config \ -v /etc/localtime:/etc/localtime:ro \ -e OPENVPN_PROVIDER=xxx \ -e OPENVPN_CONFIG=xxx \ -e OPENVPN_USERNAME=xxx \ -e OPENVPN_PASSWORD=xxx \ -e PUID=1000 \ -e PGID=1000 \ -e LAN=192.168.2.0/24 \ -e QBT_WEBUI_PORT=6080 \ -p 0.0.0.0:6080:6080 \ guillaumedsde/alpine-qbittorrent-openvpn:latest

[tessierp]

No can do.. Doesn't work for me from a swarm, ports just wont map at all.

The container still reports 8080 even if the service itself by way of the docker-compose.yml definition was asked to map to 6080.

`---
version: '3.8'
services:
qbittorrent-openvpn:
deploy:
restart_policy:
condition: any
max_attempts: 5
image: guillaumedsde/alpine-qbittorrent-openvpn:latest
cap_add:
- NET_ADMIN
networks:
- tools-net
volumes:
- /mnt/Downloads/torrents/qbittorrent:/data
- qbittorrent-openvpn-config:/config
- /etc/localtime:/etc/localtime:ro
environment:
- OPENVPN_PROVIDER=PIA
- OPENVPN_CONFIG=ca_toronto
- PGID=1000
- PUID=1000
- OPENVPN_USERNAME=xxx
- OPENVPN_PASSWORD=xxx
- LAN=192.168.20.0/23
- QBT_WEBUI_PORT=6080
ports:
- "6080:6080"

networks:
tools-net:
driver: overlay
attachable: true

volumes:
qbittorrent-openvpn-config:
external: true`

[tessierp]

I did go in the container to run curl on port 6080 and qbittorrent returned the login page however something is not mapping the ports right but the issue is still open. Have you tried running this through swarm?

[chrisdowey]

No sorry I don't use swarm

[tessierp]

Alright so I confirm this is still broken, no matter what I do I can't access the external ports at all.

[thre3eye]

Ok, I just stumbled across this and think it's a simple 'typo' in the docker-compose file. I fiddled with a few more settings and don't have the time to narrow it down but this is probably it: Instead of 'LOCAL_NETWORK' it should say 'LAN', i.e.

• LAN=192.168.0.0/24

Hope that helps...