Unrecognised project deploys with the fallback strategy and serves a placeholder
The site answers, but it is serving the PanelAlpha placeholder rather than your application. ~/project holds 28 files, so an application was uploaded and no recipe recognised it. Check the deploy log for the detected project type. A type of "Unknown" means nothing matched and the engine served its own page instead.
TypeWarningAn issue PanelAlpha Engine catches around a deploy that does not break it. It tells you, before or after, that you may need to do something.
Seen189 times · 2 variants
WhereFallback, Python
StatusObservedOur team will look into this soon, verify the cause and try to fix it in an upcoming release.
Why it happens
The repository was cloned, but the project detector could not recognise its type and chose the fallback strategy. The fallback container starts and answers HTTP 200, but it serves the PanelAlpha placeholder instead of the application.
What the log looks like
Deploy log
Detected project type: UnknownUsing strategy: fallbackDetected application port: 8080Using default environment variables (source: none)Starting application (docker compose up -d)Health check: http://[ip]:8080/ answered HTTP 200Check failed: The site answers, but it is serving the PanelAlpha placeholder rather than your application.