Qbittorent-nox service breaks automouting of network share at boot time on Debian

[WizardKnight]

qBittorrent & operating system versions

qBittorrent v4.5.2
Debian GNU/Linux 12 (bookworm)

What is the problem?

I have a basic CLI Debian server for running qbittorrent-nox. I also have a separate NAS (Ubuntu server) running a fully accessible share for public use without a username/password (samba 1.0 access) . No other devices have any issues accessing the NAS.
At boot I have a fstab entry to mount the NAS share to a local directory. This directory stores torrents that have completely downloaded.
If I have qbittorrent-nox set to start as a service, the system will fail to mount the fstab network share as expected.
If I disable the same service the fstab network drive mounts fine.
If I boot with the qbittorrent-nox service I can force the same fstab command to work with a sudo mount-a command. If I do this, I have to force a recheck of all the downloaded torrents as they were not available when qbittorrent started.
If I boot without the qbittorrent service enabled at boot, the fstab entry will mount my NAS. I can then manually start the qbittorrent service. This is not ideal, but at least it doesn't require me to force a recheck of all downloaded torrents.

Please let me know if there is more info you need, and I will do my best to provide it. If you include the locations of files that you want, it will speed up the process as I am not 100% familiar with the locations of everything.

Steps to reproduce

1. Build a Ubuntu based NAS with a Samba share with 1.0 access.
2. Build a separate Debian server with a qbittorrent-nox install, an autostart service for qbittorent-nox, and a fstab automount for the NAS.
3. Set the download directory of qbittorrent to the NAS share.
4. Download some torrents.
5. Reboot the Debian server.
6. Observe the fstab automount fail to mount.
7. Disable the autostart of the qbittorent service.
8. Reboot the Debian server.
9. Observe the fstab automount work.
10. Start the qbittorent service manualy, and see everything work as expected.

Additional context

My Debian configs:
Fstab entry (works fine if I don't start the qbittorent service)
//192.168.15.150/15tb_NAS/Data/ /mnt/NAS cifs vers=1.0,rw,user=,password=,file_mode=0777,dir_mode=0777,async,x-systemd.automount 0 0

Qbittorent-nox.service file:
[Unit]
Description=qBittorrent NoX Terminal Application
Wants=network-online.target
After=network-online.target

[Service]
Type=forking
User=qbittorrent-nox
Group=qbittorrent-nox
UMask=007
ExecStart=/usr/bin/qbittorrent-nox -d --webui-port=8080
Restart=on-failure

[Install]
WantedBy=multi-user.target

Log(s) & preferences file(s)

qBittorrent.conf

[AutoRun]
OnTorrentAdded\Enabled=true
OnTorrentAdded\Program=" chmod -R 766 /mnt/downloads/"
enabled=true
program=" chmod -R 766 /mnt/downloads/"

[BitTorrent]
Session\AddExtensionToIncompleteFiles=true
Session\AnnounceToAllTrackers=true
Session\DefaultSavePath=/mnt/NAS/Media/Torrent_Downloads
Session\DisableAutoTMMByDefault=false
Session\DisableAutoTMMTriggers\CategorySavePathChanged=false
Session\DisableAutoTMMTriggers\DefaultSavePathChanged=false
Session\ExcludedFileNames=
Session\GlobalMaxRatio=0.01
Session\GlobalMaxSeedingMinutes=1
Session\GlobalUPSpeedLimit=50
Session\Port=41442
Session\Preallocation=true
Session\QueueingSystemEnabled=false
Session\TempPath=/mnt/downloads
Session\TempPathEnabled=true

[Core]
AutoDeleteAddedTorrentFile=Never

[Meta]
MigrationVersion=4

[Network]
Cookies=@invalid()
Proxy\OnlyForTorrents=false

[Preferences]
Advanced\RecheckOnCompletion=false
Advanced\trackerPort=9000
Advanced\trackerPortForwarding=false
Connection\ResolvePeerCountries=true
DynDNS\DomainName=changeme.dyndns.org
DynDNS\Enabled=false
DynDNS\Password=
DynDNS\Service=DynDNS
DynDNS\Username=
General\Locale=en
MailNotification\email=
MailNotification\enabled=false
MailNotification\password=
MailNotification\req_auth=true
MailNotification\req_ssl=false
MailNotification\sender=qBittorrent_notification@example.com
MailNotification\smtp_server=smtp.changeme.com
MailNotification\username=
WebUI\Address=*
WebUI\AlternativeUIEnabled=false
WebUI\AuthSubnetWhitelist=192.168.15.0/24, 10.7.0.0/24
WebUI\AuthSubnetWhitelistEnabled=true
WebUI\BanDuration=3600
WebUI\CSRFProtection=true
WebUI\ClickjackingProtection=true
WebUI\CustomHTTPHeaders=
WebUI\CustomHTTPHeadersEnabled=false
WebUI\HTTPS\CertificatePath=/home/qbittorrent-nox/.config/qBittorrent/ssl/cert.crt
WebUI\HTTPS\Enabled=true
WebUI\HTTPS\KeyPath=/home/qbittorrent-nox/.config/qBittorrent/ssl/key.key
WebUI\HostHeaderValidation=true
WebUI\LocalHostAuth=false
WebUI\MaxAuthenticationFailCount=5
WebUI\Port=8080
WebUI\ReverseProxySupportEnabled=false
WebUI\RootFolder=
WebUI\SecureCookie=true
WebUI\ServerDomains=*
WebUI\SessionTimeout=3600
WebUI\TrustedReverseProxiesList=
WebUI\UseUPnP=false
WebUI\Username=admin

[RSS]
AutoDownloader\DownloadRepacks=true
AutoDownloader\SmartEpisodeFilter=s(\d+)e(\d+), (\d+)x(\d+), "(\d{4}[.\-]\d{1,2}[.\-]\d{1,2})", "(\d{1,2}[.\-]\d{1,2}[.\-]\d{4})"

[Chocobo1]

In the title you mentioned "Qbittorent-nox service" however in the paragraph you used your own Qbittorent-nox.service file. It seems to me that this is more of a support request and not actually a bug in qbt.

Anyway qbt has an official service file which might help you: https://github.com/qbittorrent/qBittorrent/blob/master/dist/unix/systemd/qbittorrent-nox%40.service.in

[WizardKnight]

I cut and pasted your official file into my system, and this is the output:

sudo systemctl start qbittorrent-nox
Failed to start qbittorrent-nox.service: Unit qbittorrent-nox.service has a bad unit file setting.
See system logs and 'systemctl status qbittorrent-nox.service' for details.

systemctl status qbittorrent-nox.service
○ qbittorrent-nox.service - qBittorrent-nox service for user
Loaded: bad-setting (Reason: Unit qbittorrent-nox.service has a bad unit file setting.)
Active: inactive (dead)
Docs: man:qbittorrent-nox(1)

So that is worse as qBitTorrent never starts at all.

[WizardKnight]

So I came up with a work around for the issue noted above.
I will leave it here in case someone else has this same issue.

1. Create a cifs helper service. - replace x.x.x.x with your cifs server's IP

[Unit]
Description=Wait for CIFS network share to be available
After=network-online.target

[Service]
Type=oneshot
ExecStart=/bin/sh -c 'until ping -c1 x.x.x.x; do sleep 1; done'

[Install]
WantedBy=multi-user.target

2. Make the CIFS service a requirement for your qBitTorrent service.

[Unit]
Description=qBittorrent NoX Terminal Application
Wants=network-online.target cifs-wait.service
After=network-online.target cifs-wait.service

[Service]
Type=forking
User=qbittorrent-nox
Group=qbittorrent-nox
UMask=007
ExecStart=/usr/bin/qbittorrent-nox -d --webui-port=8080
Restart=on-failure

[Install]
WantedBy=multi-user.target