Dedicated Server And Docker

Start with the server

If you run SoulFire as a dedicated server, fix the server-side access path first. Do not keep changing GUI settings while the remote stack itself is unhealthy.

Make sure that the access mode matches

Your client URL needs to match the way the server is exposed:

Cloudflared tunnel
Traefik with a domain
Traefik with public-IP HTTPS
plain HTTP

If they do not match, the client cannot connect even when SoulFire works.

If you used the automated dedicated-server installer, re-run it and use the management menu.

The menu shows:

the expected access URL
container health
logs
update/reconfigure actions

If the management menu already shows the stack is unhealthy, troubleshoot there before touching the GUI client.

Use HTTPS when possible

Use HTTPS with Cloudflared and Traefik. If you chose HTTP-only mode, remember:

traffic is unencrypted
some environments behave worse over plain HTTP
some clients work poorly with HTTP-only deployments

Use HTTP-only mainly for LAN or controlled testing.

If Cloudflared is the failing layer

Make sure that these Cloudflared settings are correct:

the tunnel token
the Cloudflare-side tunnel configuration
that the URL you use in the client is the tunnel URL, not a local container address

If the tunnel is healthy but SoulFire still does not respond, inspect the app container next.

If Traefik is the failing layer

Make sure that these Traefik settings are correct:

the domain or IP you actually configured
whether ports 80 and 443 are reachable from the internet
certificate issuance status
container logs for Traefik and the app

Do not assume a certificate problem is a SoulFire application problem.

If Docker is the failing layer

Start simple:

Make sure that the app container is running.
Make sure that the container is healthy.
Read the logs.
retry a basic GUI or CLI login with a fresh token

After the basic login works, enable proxies, automation, and external integrations one at a time.

Generate a fresh API token from the server side:

generate-token api

Then retry with the normal base server URL. Do not use /mcp, /webdav, or /docs as the normal client login address.

SoulFire uses the public server address to create links and related endpoints.

If related URLs are wrong, make sure that the public server address is correct.

After an update, test the basic GUI or CLI login first. Then add proxies, automation, WebDAV, and MCP one at a time.