Troubleshooting

psql or pg_isready is missing

Cause: the PostgreSQL client package is not installed.

On Oracle Linux 9 the PostgreSQL client provides psql and pg_isready; the server package is separate. The production installer should provide the client automatically. Verify with:

command -v psql
command -v pg_isready
psql --version

server does not support SSL, but SSL was required

The PostgreSQL server has no SSL while require or verify-* was selected.

Resolution: rerun setup and select the correct SSL mode. For a protected internal connection without SSL, use disable.

bootstrap.key is missing

• With an HTTP listener, a TLS bootstrap key must not be required.
• With an HTTPS listener, installer/lifecycle must automatically create and validate a key/certificate pair.

Do not create an arbitrary key manually except through an official recovery procedure.

Desktop Client cannot log in

Check that:

• the server URL is an origin only, such as https://digivc.example;
• username/password are correct;
• the account is Active;
• no mandatory temporary-password change is pending;
• the certificate is trusted by the operating system.

needs update or tree-version conflict

The remote repository is newer. Run Update, resolve conflicts and retry commit.

Commit blocked by validation

Open Repository → Checks and review findings. Fix the syntax error, forbidden path or potential secret. Do not bypass the gate by manually changing server data.

Repository is read-only

This is an administrative state. Contact the owner/administrator and identify the repository and business reason for enabling commits.

CLI password file is rejected

Check:

ls -l ~/.digivc-password
chmod 600 ~/.digivc-password

The file must not be a symlink and must be owned by the current user.

Import is slow

Full source history may be large. Review active stage, progress and storage. Do not force-restart the server while the worker is active. If interrupted, the job should be marked interrupted/failed and a partial repository must not look successful.

What to send to support

• exact time;
• username and affected project/repository;
• correlation ID;
• operation being performed;
• screenshot or copy of the visible message;
• for builds, the target build log and build/release artifact name.

Do not send passwords, access tokens or private keys.