I’m currently trying to spin up a new server stack including qBittorrent. when I launch the web UI, it asks for a login on first launch. According to the documentation, the default user id admin and the default password is adminadmin.
Solved:
For qBittorrent ≥ v4.1, a randomly generated password is created at startup on the initial run of the program. After starting the container, enter the following into a terminal:
docker logs qbittorrent or sudo docker logs qbittorrent (if you do not have access to the container)
The command should return:
******** Information ******** To control qBittorrent, access the WebUI at: http://localhost:5080 The WebUI administrator username is: admin The WebUI administrator password was not set. A temporary password is provided for this session: G9yw3qSby You should set your own password in program preferences.
Use this password to login for this session. Then create a new password by opening http://{localhost}:5080 and navigate the menus to -> Tools -> Options -> WebUI ->Change current password. Don’t forget to save.
Lol. Thank you. Part of the frustration of being a beginner in any space is that it’s not easy to discern which questions have simple answers and which are more complicated.
From the search you linked, it looks like this is as simple as typing the command
docker logs
I’ll give that a try, once I have access to the server again.
It looks like in this case the answer was a little deeper than a simple search, but no worries - you set me in the right direction. I’ll add the solution to the post.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !selfhosted@lemmy.world
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.
Rules:
Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it’s not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.
Resources:
selfh.st Newsletter and index of selfhosted software and apps
https://letmegooglethat.com/?q=docker+logs+command
Lol. Thank you. Part of the frustration of being a beginner in any space is that it’s not easy to discern which questions have simple answers and which are more complicated.
From the search you linked, it looks like this is as simple as typing the command
docker logsI’ll give that a try, once I have access to the server again.
Also if you’ve never seen it, lazydocker might be something up your alley.
It’s a TUI, but it provides easy access to docker containers, logs, updating/restarting/stopping/etc them and so on.
It looks like in this case the answer was a little deeper than a simple search, but no worries - you set me in the right direction. I’ll add the solution to the post.