Skip to content

Fix Traefik API/ACME issues, seerr mount, qBittorrent env + README improvements#9

Open
kevinstsauveur wants to merge 9 commits intoLackoftactics:mainfrom
kevinstsauveur:fix/7
Open

Fix Traefik API/ACME issues, seerr mount, qBittorrent env + README improvements#9
kevinstsauveur wants to merge 9 commits intoLackoftactics:mainfrom
kevinstsauveur:fix/7

Conversation

@kevinstsauveur
Copy link
Copy Markdown

Small fixes and documentation updates addressing the issues reported in #7 :

Traefik

  • Set Docker API compatibility to avoid "client version too old" errors and update Traefik config to work with tested Docker/Traefik combo (v3 example).
  • Fix ACME-related settings introduced by the Traefik upgrade so certificate issuance succeeds with Cloudflare DNS-01.

Seerr

  • Correct volume mapping to persist config: /mnt/user/appdata/seerr/config:/app/config

qBittorrent

  • Remove misleading default credentials from README and compose that were not applied.
  • Ensure environment variables for username/password/port are read from .env (document behavior and where to check container logs on first startup).

README

  • Add "Subdomains" section listing FQDNs to register (traefik, bazarr, jellyfin, prowlarr, qbit, radarr, seerr, sonarr).
  • Add brief internal routing tip with example internal URLs for container-to-container access.
  • Clarify DNS/hosts note: create FQDNs or use hosts file pointing to Tailscale IP.

Fix traefik version and minimal API version
Added configuration details for service networking and DNS.
Removed default username and password for qBittorrent.
Added sections for configuring services, domains, and qBittorrent in the README.
Removed QB_USERNAME, QB_PASSWORD and WG_PUBLIC_KEY from example.
Copy link
Copy Markdown
Owner

@Lackoftactics Lackoftactics left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

just some small comments

Comment thread arr/docker-compose.yml
VPN_SERVICE_PROVIDER: protonvpn
VPN_TYPE: wireguard
WIREGUARD_PRIVATE_KEY: ${WG_PRIVATE_KEY}
WIREGUARD_PUBLIC_KEY: ${WG_PUBLIC_KEY}
Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

https://github.com/qdm12/gluetun-wiki/blob/main/setup/options/wireguard.md shouldn't that be still here? Might be wrong, but some providers require it

Copy link
Copy Markdown
Author

@kevinstsauveur kevinstsauveur Apr 14, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You're probably right that some service need it.

I had problems to connect to protonvpn with the default stack. I'm not sure if it's this part or the other changes to gluetun service that resolve the problem. Maybe we can comment it by default?

Feel free to commit some change, it's your stack after all!

Comment thread README.md
Comment on lines +71 to +81
This is the list of subdomains for which you must create `A` records pointing to the Tailscale IP of the machine that hosts Traefik:
- traefik
- bazarr
- jellyfin
- prowlarr
- qbit
- radarr
- seerr
- sonarr

Note: create full FQDNs (e.g., traefik.example.com) in your DNS zone (alternatively, add them to your hosts file), each pointing to your host's Tailscale IP.
Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

wildcard option would be more elegant

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh well, that's exactly what I was running against with this section. I have at least 20 other subdomains that are not routed through this stack and I would not want the people following this guide to introduce problems with a wildcard (If they already have a domain, they probably already have some subdomains registered).

In fact, in this section, I wanted to list the subdomains so that people would know and understand which one to use to access each service (the qbit one was a bit of a surprise for me since I was trying "qbittorrent" at first)!

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

those are good comments, I will try to improve them a bit and merge

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants