this post was submitted on 22 Nov 2023
1 points (66.7% liked)

Self-Hosted Main

511 readers
1 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

For Example

We welcome posts that include suggestions for good self-hosted alternatives to popular online services, how they are better, or how they give back control of your data. Also include hints and tips for less technical readers.

Useful Lists

founded 1 year ago
MODERATORS
 

Hey all,

I think I got most of it to work using this guide: https://fossengineer.com/selfhosting-qBittorrent-with-docker-and-VPN/

I get the qBittorrent UI but login doesnt seem to be admin/adminadmin, it says invalid username or password. I haven't been able to log into this yet. I saw a guide saying I can just remove the following lines from conf file:

password= # this only appear on qBittorrent version < 4.2.0 password_PBKDF2= # this only appear on qBittorrent version ≥ 4.2.0

THE PROBLEM IS THOSE LINES DO NOT EXIST IN MY CONFIG FILE. My config files are at /home/myuserid/docker/qBittorrent/qBittorrent.conf and it only has Adress=* and ServerDomains=* for WebUI\. How do i reset it? I originally had my config files in /home/docker/ but reinstalled thinking it was due to permission issues. my qBittorrent.conf has -rw-r--r-- permissions right now. I tried changing it to 755 prior to reinstall and it still didn't seem to update. on my shell that I compose on, it says [custom-init] No custom files found, skipping...

Question #2 is my docker shell that i compose seems to say the right things? I get LSIO ascii art for qbittorrent. gluten says dns ready, healthcheck healthy, vpn 3 commits behind the msot recent latest, and my vpn ip and city. but why does this keep connecting to random servers? how do i specify to connect to my local ones? there's no line for that in the .yaml unlike the markus qbittorrentvpn one(which i also tried but failed miserably).

top 2 comments
sorted by: hot top controversial new old
[–] [email protected] 1 points 11 months ago

Just ran into this myself. I fixed it by disabling auth for my local network in the config file. IMPORTANT: Stop the container first because it overwrites config files on shutdown.

I was then able to log in and set the password. After that the login worked fine.

[–] [email protected] 1 points 11 months ago

Yo I tried to setup my ubuntu server w/o much knowledge in linux over the weekend. Got jellyfin with duckdns setup and now stuck on docker/qbit. This is so frustrating. Please help.