Container outbound HTTPS was broken in 1.5.115/117 — fixed in 1.5.118
Posted by tomspark
We shipped a change two releases ago that disabled Docker's iptables management to let UFW take over. Turns out that broke container egress entirely: without Docker's MASQUERADE rules, outbound traffic from containers left with private source IPs and got silently dropped upstream. This killed license activation and any HTTPS call from your dashboard. Version 1.5.118 reverts that mistake — Docker's iptables management is back on by default, and it plays fine with UFW. If you're on 1.5.115 or 1.5.117, the upgrade will strip the bad iptables: false setting from your existing daemon.json. Fresh installs won't write it at all. We also fixed the post-install egress check to test against the real sbproxy network your dashboard uses, so it won't mask this kind of breakage again. If you hit stale NAT rules after a Docker daemon restart, or you're migrating from an older broken install, try sparkbox repair-network — it'll tear down and rebuild your network stack from scratch. Head to the Updates tab in your dashboard to pull 1.5.118. If you hit any issues, post here in d/sparkbox. --- Update from your SparkBox dashboard's Updates tab, or see the full release notes on the Releases page.