Skip to main content

​
Goal

Identify why an Edge SSH endpoint, published HTTPS address, or custom domain is not working.

​
Prerequisites

  • Open Compute → your VPS → Publishing and note the affected route’s hostname, port, and status.

​
Workflow

1
Confirm the VPS is running and the route is Configured.
2
Identify whether the failure is SSH login, the StackShift HTTPS name, or a custom domain.
3
Use the matching symptom below to check the guest service and Publishing settings.

​
Route status

  • Pending: the route has been requested and is being applied. Wait for Configured before using the displayed endpoint.
  • Configured: StackShift has applied the route. Check the guest service, chosen port, IP restriction, and app hostname if traffic still fails.
  • Offline: the VPS is stopped or otherwise unavailable for publishing. Return it to a running, eligible state.
  • Web App health is a separate base-path probe. Healthy does not guarantee that every application page works; unknown may appear just after an edit.

​
SSH symptoms

  • Connection times out: use the assigned external port shown in Edge SSH, confirm the route is Configured, and check whether Allowed client IP ranges include your current public IP.
  • Permission denied (publickey): traffic reached the guest SSH server. Use the displayed username and a private key matching a public key authorized for that user in the VPS.
  • SSH host-key warning: compare the fingerprint against a trusted guest fingerprint before accepting a change. The edge forwards the VPS’s SSH service.
  • Direct guest IPv6 SSH times out but Edge SSH works: inspect the client network’s IPv6 support and the guest’s direct IPv6 firewall separately.

​
Web and DNS symptoms

  • HTTPS returns 502: check the selected guest HTTP port, the service listener, and the guest firewall. Run sudo ss -ltnp inside the VPS to inspect listeners.
  • HTTPS shows a default page or wrong app: configure the published hostname inside the guest app, Coolify, or Dokploy proxy.
  • HTTPS returns 403: check the publication’s Allowed client IP ranges. Leave the field empty for a public app.
  • Verify DNS reports a conflict: confirm the exact TXT token and that every A/AAAA answer for the custom hostname points directly to the edge address shown in Publishing.
  • The StackShift hostname works but a custom domain does not: check that the domain shows Verified, DNS still resolves to the edge, and the guest app recognizes that custom Host name.

​
What to send support

Provide the VPS name, publication hostname or assigned Edge SSH port, the displayed route status, the time of the failure, and the exact error text. Do not send a private SSH key, password, or DNS account credential.

​
Expected result

You can distinguish an edge route problem from a guest app, SSH key, DNS, or client-network problem.

Connect with Edge SSH

Enable a per-VPS SSH port on the StackShift edge and connect with your existing guest login and private key.

Publish a VPS web app

Map a StackShift HTTPS hostname to one selected HTTP port on a full-root Compute VPS.

Attach a custom domain

Prove ownership with DNS TXT, point A or AAAA directly at the edge, and attach the hostname to an existing web publication.