Skip to content

Self-Hosted GitFlic Troubleshooting

This section may help you diagnose and resolve issues with self-hosted GitFlic.

General Tips

Viewing Application Logs

For independent troubleshooting, you can open the application log file and find the necessary error information, or you can attach this file when contacting technical support.

The log file path is specified in the GitFlic configuration file (application.properties). The default path to the file is: /var/log/gitflic/server.log.

# ======= Logging settings =======

# Settings for the log file name and path
# The logging.file.name property should contain the file name. The default value is server.log.
# The file name can contain either a relative path from the application's launch directory
# or an absolute path if it starts with /
# Please note that each running instance can have its own log file; otherwise, one
# file will be used for all instances
#logging.file.name=/opt/gitflic/log/server.log

Below are errors that most frequently occurred for users

Issue 1

Unable to connect to Redis; nested exception is io.lettuce.core.RedisConnectionException: Unable to connect to example.com:6379

Solution: Check if Redis is running and provide correct credentials for connecting in the GitFlic application.properties file.

Issue 2

Repository creation error

You have exceeded the repository creation limit

Solution: This error occurs because the folder where repositories should be stored, as specified in application.properties, was not created.

Note: This problem is relevant only for GitFlic versions 2..

Running GitFlic in Docker

The project route in GitFlic running in docker is displayed incorrectly

In Docker, the transport.url route is set in three places (default-config/application.properties, docker-compose.yml, ENV). To change the transport.url, it is recommended to modify it in docker-compose.yml; by default, it is set as GITFLIC_TRANSPORT_URL: http://${GITFLIC_TRANSPORT_URL}:${SERVER_PORT}. If your service is accessible on port 443 or 80, change this parameter to GITFLIC_TRANSPORT_URL: https://gitflic.ru. There is no need to specify the port when using these ports.

Installing and Configuring postgresql

When configuring postgresql, the pgcrypto extension installation error occurs

  1. Make sure the command CREATE EXTENSION pgcrypto; is run for the correct database (for example, gitflic). (More information)
  2. Ensure that the postgresql-contrib package is installed.
  3. In the file: /var/lib/pgsql/data/pg_hba.conf or /etc/postgresql/12/main/pg_hba.conf, replace the line host all all 127.0.0.1/32 ident with host all all 127.0.0.1/32 md5 to use password authentication.
  4. If you get the error "pg_hba.conf not found," run the following commands:
sudo -i -u postgres
psql -t -P format=unaligned -c 'show hba_file';

Automated translation!

This page was translated using automatic translation tools. The text may contain inaccuracies.