Chris wrote:
Hi mrga — I see your post didn't fully come through. When you ran the diagnostic commands, can you let me know which part failed or didn't work? For example: - Did the ping time out (no response from the IP)? - Or did one of the docker commands show that cloudflared and onlyoffice are not on the same network? - Or something else? Paste the output that showed the problem, and I can point you to the fix.
Chris wrote:
Hi mrga — sorry, we sent you down the wrong path, twice. The ping command can't work: the tunnel container is a stripped-down image with no shell and no ping tool in it, so it will only error out with "executable file not found" and tells us nothing. And the earlier suggestion to point the Cloudflare hostname at an IP was wrong too. Here's how it actually works: the tunnel sits on SparkBox's internal network alongside every app, so on the Cloudflare tunnel page the hostname's service should point at the app by its container name and its inside port — not an IP, and not the port you use on your home network. For the Document Server that is type HTTP, service sb-onlyoffice:80 (port 80, not 8790 — 8790 only applies on your home network). One check: confirm the Document Server toggle is on under Settings → Apps → Cloud Storage ("Enable Document Server") — if it's off, the sb-onlyoffice container doesn't exist at all, so nothing can route to it. Then save the hostname route as sb-onlyoffice:80 and reload the public address. If it still fails, tell me the exact error code Cloudflare shows on the page and I'll take it from there. We've corrected what the assistant knows about the tunnel container so the next person isn't sent the same way. Thanks for your patience — we're learning from this.