Repository cloning failed because GitHub authentication was unavailable
The repository could not be read. Check that it is public, or that the access token is valid.
TypeErrorAn error that occurred in the deployed application. It is not necessarily a PanelAlpha Engine error, but we keep working on improvements so you run into fewer of them.
Seen1 times
StatusObservedOur team will look into this soon, verify the cause and try to fix it in an upcoming release.
Why it happens
The deploy reached the cloning stage, but Git could not read the repository over HTTPS. GitHub requested credentials, and no usable username or access token was available to the non-interactive deploy process. Although the repository was recorded as public, the configured URL or repository access may still be incorrect or restricted.
What the log looks like
Deploy log
Starting stage: cloningCloning repository https://github.com/<account>/<account>-comCloning into '/home/<account>/project'...fatal: could not read Username for 'https://github.com': No such device or addressDeploy failed: The repository could not be read.