Skip to content
This repository has been archived by the owner on Nov 25, 2022. It is now read-only.

"Unauthorized" upon connecting to the web interface #32

Closed
0ze opened this issue Nov 6, 2020 · 5 comments
Closed

"Unauthorized" upon connecting to the web interface #32

0ze opened this issue Nov 6, 2020 · 5 comments
Assignees
Labels
bug Something isn't working

Comments

@0ze
Copy link

0ze commented Nov 6, 2020

Information

describe the issue

when trying to connect to the web interface, it just says Unauthorized. am i connecting to the wrong ip? feeling dumb. also, when I tried to use OPENVPN_PROVIDER as PIA, i couldnt get it to find any of the configs like US Chicago, US Texas, etc. yes, I properly escaped the spaces.

Current setup

information about your current setup

using a custom openvpn config, but its just generated from pia openvpn config generator tool. replaced sensitive info with &'s, but thats the exact run command im using. I changed the LAN to 10.0.0.0 from 192.168.0.0 since thats the format my lan uses.

docker-compose.yml file or docker run command

how did you start the container? (don't forget to use backticks for creating a proper code block)

docker run --cap-add=NET_ADMIN -d \
              -v /home/&&/ten/media/dl:/downloads \
              -v /home/&&/ten/media/tc:/config \
	      -v /home/&&/ten/media/tf:/torrents \
              -v /etc/localtime:/etc/localtime:ro \
	      --name qbit-vpn \
              -e OPENVPN_USERNAME=&&&&&&  \
              -e OPENVPN_PASSWORD=&&&&&& \
              -e PUID=1000 \
              -e PGID=1000 \
              -e LAN=10.0.0.0/16 \
              -p 8089:8080 \
              guillaumedsde/alpine-qbittorrent-openvpn:latest

Attempted Fix(es)

What you have tried in order to fix the issue (if anything)

changed openvpn config, run command, different browser, even calling curl/wget from the server running the docker container also results in the "unauthorized" response

@0ze 0ze added the bug Something isn't working label Nov 6, 2020
@cllu
Copy link

cllu commented Nov 9, 2020

The solution in qbittorrent/qBittorrent#8095 (comment) works for me.

@0ze
Copy link
Author

0ze commented Nov 9, 2020

The solution in qbittorrent/qBittorrent#8095 (comment) works for me.

edited my config and it works perfectly now, thank you so much

@0ze 0ze closed this as completed Nov 9, 2020
@shuffleznl
Copy link

For posterity; Decentraleyes chrome-extension also results in 'Unauthorized'.
Private browsing or whitelisting in extension worked for me.

@tamarindmonkey
Copy link

tamarindmonkey commented Aug 13, 2021

You are probably passing a referrer in your Request headers.
General -> Referrer Policy: strict-origin-when-cross-origin

Set:
WebUI\CSRFProtection=false

I couldn't care less about this stupid feature when I'm running qbittorrent on my LAN and nobody else could possibly get to it. Edit: 😳 I stand corrected; You can change the setting in the WebUI under Options -> Enable Cross-Site Request Forgery (CSRF) protection. Uncheck it.

@spencerthayer
Copy link

You can change the setting in the WebUI under Options -> Enable Cross-Site Request Forgery (CSRF) protection. Uncheck it.

Thank you!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

6 participants