Skip to main content

​
Goal

Connect an external Coolify or Dokploy manager to a Compute VPS and publish one of its web apps.

​
Prerequisites

  • A running Compute VPS with Publishing available.
  • The guest SSH service and key required by the remote manager, plus an app configured in Coolify or Dokploy.

​
Workflow

1
If Coolify or Dokploy manages the VPS from another machine, enable Edge SSH on the VPS.
2
Add the VPS as a remote server in Coolify or Dokploy using the Edge SSH hostname, assigned port, displayed username, and a key trusted by the guest.
3
Choose a new web hostname in StackShift and add that exact hostname to the app’s domain or routing configuration in Coolify or Dokploy.
4
In StackShift Web publishing, enter that hostname label and the HTTP port exposed by the guest proxy, then save and open the HTTPS URL.

​
Connect the manager over SSH

  • Use ssh.compute.stackshift.cloud as the remote server host. Use the assigned Edge SSH port shown for this VPS, not the guest’s port 22 as the external port.
  • Use the VPS username displayed in Publishing and a private key whose public key is in the guest user’s authorized_keys. StackShift does not issue a new SSH identity to Coolify or Dokploy.
  • If the manager itself runs on this same VPS and already administers it locally, you do not need Edge SSH merely to publish its apps.

​
Publish an app served by the guest proxy

  • Choose a StackShift name such as myapp.compute.stackshift.cloud and add it to that app inside Coolify or Dokploy so its reverse proxy recognizes the Host name.
  • Publish the guest proxy’s plain HTTP listener using the actual port configured on your VPS. A container-only port or a TLS-only port is not the correct target unless it exposes plain HTTP on a host-reachable address.
  • If the app redirects repeatedly between HTTP and HTTPS, review its trusted proxy and HTTPS redirect settings. Public TLS terminates at StackShift’s edge while the edge forwards HTTP to the guest proxy.
  • Existing Coolify or Dokploy domains keep working on their current route. Add a custom domain to StackShift only when you intend to change that domain’s DNS to the edge.

​
If the app does not open

  • A 502 points to the guest proxy or selected HTTP port. Check that the proxy listens on an address reachable from the compute host and that the guest firewall permits the connection.
  • A default proxy page or a different app indicates the guest proxy does not match the new hostname. Add that hostname to the correct app in Coolify or Dokploy.
  • An SSH publickey error from the manager indicates a guest user/key mismatch. The edge does not manage guest authorized keys.

​
Expected result

The manager can reach the full-root VPS over SSH, while visitors reach the selected app through a StackShift HTTPS hostname.

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.