Common Issues and Troubleshooting

---

"failed to read expected number of bytes: unexpected EOF"

This error relates to Docker registry operations and was fixed in GitFlic version 3.3.0.

If you encounter this error in GitFlic 3.3.0 or later:

1. Use the bundled CLI tool
2. Follow these steps:

# 1. Extract GitFlic package
unzip gitflic_3.3.0_free.zip

# 2. Navigate to CLI directory
cd /path/to/archive/cli

# 3. Make script executable
chmod +x ./gitflic-cli.sh

# 4. Run CLI with your config
./gitflic-cli.sh /path/to/application.properties

After launch (when you see shell:> prompt):
5. Execute: fix docker manifest
6. Exit with ctrl+c when complete

---

"psql: error obtaining MAC configuration for user"

This indicates the database cannot properly determine user security labels.

Solution:

1. Verify PostgreSQL user has proper permissions:
   

   sudo getfacl /etc/parsec/macdb/
   sudo getfacl /etc/parsec/capdb/
   

   Look for user:postgres:r-x in output

2. If missing, set permissions:
   

   sudo setfacl -R -m u:postgres:rx /etc/parsec/capdb
   sudo setfacl -R -m u:postgres:rx /etc/parsec/macdb
   

3. Restart application

If error persists
Configure proper confidentiality levels per official guide

---

"Missing PKCS8 RSA keys"

These keys are required for:
- Vault operations
- SAML/OIDC
- Container signing
- CI token signing

For upgrades from 3.x.x:

Use keys-retriever.jar to extract keys from existing installation.
Upgrade details

For new 4.x.x installations:

1. Generate private key:
   

   openssl genpkey -algorithm RSA -out private_key.pem -pkeyopt rsa_keygen_bits:2048
   

2. Generate public key:
   

   openssl rsa -pubout -in private_key.pem -out public_key.pem
   

3. Update application.properties:

gitflic.vault.cert.privateKey=/path/to/private_key.pem
gitflic.vault.cert.publicKey=/path/to/public_key.pem

Automatic translation!

This page has been automatically translated. The text may contain inaccuracies.