These cover repository checks, dependency/build stages where relevant, output validation, publishing and preview validation.
Documentation
Read deployment and runtime logs.
Logs show the managed work Host Luma performed for the selected deployment type. They are the starting point for a focused correction, not a reason to make several untracked server changes.
Know which log you are reading
Static releases and managed Node releases have different evidence.
These cover the configured Node deployment path, start preparation and the required health check.
Use runtime logs and the Portal restart control to investigate a running Node application after it has deployed.
A short recovery loop
Find the first relevant failure, then change one thing.
Do not diagnose a Node application as a static build, or describe a static output problem as a runtime failure.
The last line can be a consequence. Look first for the repository, dependency, build, start, port or health-check message that caused the failure.
Run the normal production build locally, or for Node verify npm start, a supplied port and GET /health without exposing secrets.
Make one GitHub correction and use the next deployment record to verify that it addressed the actual cause.
Health, restart and previous versions
Use the controls without overstating what they restore.
A supported managed Node application must respond to GET /health; an unhealthy response is a runtime condition to investigate in its logs and source. The Portal provides a managed restart control for that application type.
For a previous successful Git commit, the Portal can queue a new deployment through the standard path. Previous-version redeployment is not a rollback of a database, a runtime environment or a snapshot.
When the logs show a product-fit issue
Stop retrying the wrong architecture.
AI Hosting does not add PHP, customer databases, Docker, queues or arbitrary background workers. If a failure requires one of these services, treat it as a product-fit finding. A server-driven JavaScript project is a fit only when it meets the managed Node 22 HTTP contract.
For hosting-side account, connection, domain or deployment-state help, contact support with the project name, time and non-sensitive error context. Do not send tokens, deploy keys or credentials.