root@Server:~# curl --max-time 10 -v http://127.0.0.1:8089 * Trying 127.0.0.1:8089... *

Posted by SSJNobleSix

My question: root@Server:~ curl --max-time 10 -v http://127.0.0.1:8089 Trying 127.0.0.1:8089... Connection timed out after 10000 milliseconds Closing connection curl: (28) Connection timed out after 10000 milliseconds root@Server:~ sudo sparkbox up media / | | | | ) \ \| ' \ / | '| |/ / \ / \ \/ / ) | |) | (| | | | <| |) | () < |/| ./ \,|| ||\\/ \//\\ || SparkBox v1.6.660 - Self-Hosted Privacy Stack Created by Tom Spark | youtube.com/@TomSparkReviews Network profile: private [INFO] Starting SparkBox... [INFO] Targeted up: media [INFO] Tailscale is on — allowing the tailnet range (100.64.0.0/10) back out of the VPN tunnel so the apps behind it answer remotely. [+] up 13/13 ✔ Container sb-byparr Running 0.0s ✔ Container sb-sabnzbd Running 0.0s ✔ Container sb-chaptarr Running 0.0s ✔ Container sb-lidarr Running 0.0s ✔ Container sb-gluetun Healthy 0.7s ✔ Container sb-qbittorrent Running …(reply truncated — full chat sent to Tom)

2 replies

Chris wrote:

That "Connection timed out after 10000 milliseconds" result is useful: on 1.6.660, qBittorrent’s Media-bundle endpoint is 8089 and it should respond locally. Please don’t change the VPN or ports. I’ve logged this and our team is investigating the 8089 endpoint. Next, in your SparkBox dashboard select ? (bottom-right) → Open Tom AI and paste that result; it can inspect your live container state without you posting passwords or keys here.

Anthony wrote:

I checked the published 1.6.661–1.6.664 notes; none claims a fix for this 8089 timeout. The next safe check is: run sudo sparkbox logs qbittorrent, wait about 20 seconds, then press Ctrl+C. Please reply with only the final 20 lines after removing any URLs or tokens. This reads logs only—please do not change the VPN, firewall, or ports.