When I set sabnzbd on my domain and open it I get this error: Access denied - Hostname verification failed: https://sabnzbd.org/hostname-check
Posted by franciscus
My question: [custom-init] Files found, executing [custom-init] 01-set-port.sh: executing... [sab-preinit-port] sabnzbd.ini already on port=8081 — no-op [sab-preinit-port] hostwhitelist already current (sb-gluetun, sb-sabnzbd, ugreen-8800, ugreen-8800.local, vaultwardenxxxxxxx., 2cb894d4e067.local, vault.sparkbox.local, 807a08195dda.local, e71dceb70df8.local, 2695de937f2e.local) — no-op [sab-preinit-port] done [custom-init] 01-set-port.sh: exited 0 2026-09-22 11:41:41,477::INFO::[SABnzbd:1135] -------------------------------- 2026-09-22 11:41:41,478::INFO::[SABnzbd:1136] SABnzbd.py-5.1.3 2026-09-22 11:41:41,478::INFO::[SABnzbd:1137] Full executa …(cut here — the full chat went to Tom) SparkBox AI replied: Yep, same result. SABnzbd is healthy, but sabnzbd.xxxxxxx.de is still missing from hostwhitelist: text hostwhitelist already current (... vaultwarden.xxxxxxx.de, ...) The request reaches SAB through NPM, then SAB rejects it. The certificate isn’t the cause of this particular error. The important correction: adding the proxy host in NPM does not automatically add the hostname to SABnzbd’s whitelist. I don’t have a documented SparkBox setting that links an NPM hostname to that generated list, so I won’t send you hunting through menus that may not exist. For a direct workaround, use: text http://<NAS-IP:8186 …(cut here — the full chat went to Tom) What I still need help with: (describe what didn't work or what's still broken)
7 replies
Chris wrote:
I’m sorry—the earlier AI reply sent you toward a direct workaround and treated this as a manual whitelist entry. The supported SparkBox path rebuilds SABnzbd’s allowed host names when the media stack starts, including the box hostname, its .local name, a configured SparkBox custom domain, and the Tailscale name; you should not need to hand-edit sabnzbd.ini. The fix for this hostname-check problem is already shipped. Please run: sudo sparkbox update then sudo sparkbox up Then open the same domain again. If it still fails, tell me whether that domain was added through SparkBox’s Custom Domains page or manually in Nginx Proxy Manager, and share only the relevant error line with the domain redacted. I’ve corrected this guidance so the unsupported workaround is not repeated to the next person.
franciscus wrote:
Access denied - Hostname verification failed: https://sabnzbd.org/hostname-check I installed it through cloudflare, I have at least 11 apps who are working this way. In sabnzbd it gives this error: vor ein paar Sekunden Verbindung vom Host "sabnzbd.xxxxxx.de" abgelehnt von: ::ffff:172.20.0.1 (X-Forwarded-For: 91xxxxxx1) [Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/146.0.0.0 Safari/537.36]
franciscus wrote:
Got it: Über die SABnzbd-Oberfläche: Öffne SABnzbd zunächst über die lokale IP-Adresse, z. B. http://1xxxxxx:8080. Gehe zu Config/Einstellungen → Special/Spezial. Suche nach Host whitelist. Trage dort nur den Hostnamen deiner Domain ein, ohne https:// und ohne Pfad oder Port
Chris wrote:
Thanks for reporting this: d/sparkbox , franciscus. SparkBox's handling of that path was wrong, and it's fixed in the latest update. Your box will pick it up during its nightly update, or you can run sparkbox update now.
franciscus wrote:
Same thing happend when I connected paperless with my domain could not open it. Only in paperless is nothing where I can "whitelist" my domain.
Chris wrote:
I’m sorry—the earlier manual-whitelist advice was wrong for this Cloudflare Tunnel setup, and it did not address your Paperless follow-up. The released fix is for SABnzbd: SparkBox 1.6.774 adds the published Cloudflare hostnames to SAB’s generated allow-list. Please update SparkBox to 1.6.774, then run sudo sparkbox up. In the Cloudflare Tunnel app settings, enter the exact hostname you published for SABnzbd in CLOUDFLAREPUBLICHOSTNAMES (comma-separated if needed; do not include https://, a path, or a port), then try the SABnzbd address again. Paperless is a separate case, so this SABnzbd fix does not prove that Paperless uses the same check. If Paperless still fails, reply with only its exact error text and the domain redacted. I’ve corrected this guidance so the unsupported manual-whitelist step is not repeated.
Chris wrote:
A correction to my update instruction: sparkbox update refreshes app images but does not install a SparkBox release. The Cloudflare hostname allow-list fix is part of SparkBox 1.6.774; to install a SparkBox release use sudo sparkbox upgrade, followed by sudo sparkbox up to apply it. Your earlier reply says you installed SABnzbd through Cloudflare but does not give the current SparkBox version or confirm whether CLOUDFLAREPUBLICHOSTNAMES is configured. Before changing anything, please tell me your current SparkBox version and whether that hostname is entered in SparkBox's Cloudflare Tunnel settings. Keep the domain redacted. This fix only covers SABnzbd; it does not establish the Paperless cause. I've corrected what I know so the image-refresh command isn't confused with a release upgrade again.