Reverse proxy in Qbit 3.2

Other platforms, generic questions.
Post Reply
eddie4

Reverse proxy in Qbit 3.2

Post by eddie4 »

Hi,

I have been using apache to reverse proxy to Qbittorrent-nox. Apache takes care of encryption and access control. However with the new upgrade of the web interface links are no longer dynamic.

Reverse proxy adres
https://www.*.info/qbit/

Current url's:
https://www.*.info/css/style.css
https://www.*.info/login

Should be:
https://www.*.info/qbit/css/style.css
https://www.*.info/qbit/login

Any chance you could fix this by adding a reverse proxy prefix? Or tell me if it already exists and is undocumented.

Cheers
Eddie
eddie4

Re: Reverse proxy in Qbit 3.2

Post by eddie4 »

Seems It already has been fixed just hasn't gotten it way into the repository. See screenshot
Attachments
photo63008759826460539.jpg
User avatar
Peter
Administrator
Administrator
Posts: 3049
Joined: Wed Jul 07, 2010 6:14 pm

Re: Reverse proxy in Qbit 3.2

Post by Peter »

Wait for merge, or git clone + apply patch + compile.
(It's easy to do the latter on Linux.)
cpressland

Re: Reverse proxy in Qbit 3.2

Post by cpressland »

Hey Guys,

I've just compiled the latest build from Github, specifically

Code: Select all

[root@dl01 ~]# qbittorrent-nox --version
qBittorrent v3.3.0beta
And this doesn't seem to work, was there ever an officially released patch / fix for this? Trying to proxy with Nginx with this:

Code: Select all

location /qbittorrent {
    proxy_pass http://127.0.0.1:8080;
    proxy_set_header Host $host;
    proxy_set_header X-Real-IP $remote_addr;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
  }
Accessing the box directly on port 8080 works fine, so I know the WebServer is working perfectly, it's just reverse proxying with /qbittorrent breaks it.

Any ideas?

Thanks!
Post Reply