Fallback deploy is reachable but uses a self-signed certificate
Warning recorded 1 times in PanelAlpha Engine deploys on Fallback. The deploy log below is the recorded failure output.
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.
Seen1 times
WhereFallback
StatusObservedOur team will look into this soon, verify the cause and try to fix it in an upcoming release.
Why it happens
The automatic CMake build failed because libweb has no CMakeLists.txt and the cJSON development package was not found. Engine then generated a basic fallback compose setup, which started and returned HTTP 200 on port 8080. The assigned hostname has no public IPv4 resolution, so it uses a PanelAlpha self-signed certificate.
What the log looks like
Deploy log
CMake Error at CMakeLists.txt:28 (add_subdirectory): The source directory /app/libweb does not contain a CMakeLists.txt file.Could not find a package configuration file provided by "cJSON"ERROR: failed to build: failed to solve: process "cmake -B /build -GNinja /app" did not complete successfullyNo compose file and automatic build unavailable, generating basic composeHealth check: http://[ip]:8080/ answered HTTP 200Deploy finished with warnings: certificate ... is self_signed