Troubleshooting

Deploying#

This project has no environment yet — create one first.

A deploy runs in an environment. Add one from Projects→Add environment, then reopen New deploy.

This project has no build yet — create a build first.

Create a build in the same project from Builds→New build. The Build list only shows builds from the selected project.

The selected build has no container port — set one on the Builds page to enable exposing.

Publicly expose this deploy needs the port your container listens on. Edit the build, set Container port, then edit the deploy and tick expose.

Pods stay Pending

The pod hasn't started. Common causes: the location has no room yet (the deploy's placement.state is PENDING and it retries on its own), the image can't be pulled (check the image name, the tag, and that the image is public), or a dedicated machine type isn't offered in that location. See Deployment status.

Restarts keep climbing

The container starts and then exits. Check Watch logs for the last lines before each exit. Compare Memory usage with the allocation in View metrics, because a workload that runs out of memory may be restarted. Also check that the app listens on the build's Container port.

The image runs locally but not on DevLyft

Check the image has a variant for the node's architecture (the Arch column on Nodes), and that it reads its configuration from environment variables set on the deploy.

Secrets#

Use only letters, numbers, and . _ = - (no spaces, slashes, or other characters).

Secret names accept A–Z a–z 0–9 . _ = - and up to 253 characters. DATABASE_URL works. database url and db/url don't.

The Set a secret form is missing

Only Admins and Managers can set or delete secrets. Other members see the list of keys but not the form.

"Secrets referenced by deploys"

Secret listing couldn't be loaded, so the page shows the keys your deploys reference instead. Values are never shown either way.

A secret isn't offered in the deploy form

Secrets belong to one environment. The deploy's Secret picker only lists secrets in the deploy's environment. Set it there first.

Domains and HTTPS#

DNS TXT record not found yet — it can take a while to propagate. Try again shortly.

Check the TXT record's name and value match the dashboard exactly, wait for DNS to propagate, then choose Verify now again.

This claim expired before the DNS record was found.

A claim has 72 hours to verify before it's marked Failed. Delete it and claim the domain again to get a fresh challenge.

No verified domains yet.

Routes can only use a verified domain. Claim and verify one on Domains first.

DNS target pending…

The deploy isn't publishing edge DNS yet, so there's no CNAME target to show. Make sure the deploy is exposed, then reopen Routes shortly.

The hostname resolves to Cloudflare addresses, or HTTPS never works

The record is proxied (orange cloud). Set it to DNS only. Certificates can only be issued once the CNAME resolves to DevLyft. See Custom domains.

Access and accounts#

view-only (managers and admins can make changes)

Your role is User. Ask an admin to change your role on Team. See Members and permissions.

Only managers and admins can change resources.

The CPU and memory controls are locked for the User role.

Billing is admin-only

Only organisation admins can open Billing.

No DevLyft user has that email.

Teammates need a DevLyft account before they can be added. Ask them to sign up, then add them by the same email.

You're sent to confirm your email

Creating organisations and other resources needs a confirmed email address. Follow the link in your confirmation email, then retry.

Couldn't load your workspace

The dashboard couldn't reach the DevLyft API. Choose Retry. If it keeps happening, contact support.

Node data / Pod data is currently unavailable

Those listings couldn't be loaded for your login. Your workloads aren't affected. Use deploy logs and metrics in the meantime.

Contact support#

Open Organisation→Support and fill in Email, Subject and Message, then choose Send to support. A ticket ID is generated, so include it if you follow up. The team usually replies within one business day. You can also email info@devlyft.io.

It helps to include the organisation, project, environment and deploy names, the time the problem started, and the exact text of any message.