Error 500 After Docker installation

[Sn0wF0x]

Hello

I just installed a new arch linux and try to use docker to install leantime but everytime i try to use the install folder it throws me a 500 error? No mater which way I try?

[marcelfolaron]

Is that with 3.3.3 or a previous version? Any errors in storage/logs (inside of the container)?

…

On Wed, Nov 27, 2024 at 17:06 Sn0wF0x ***@***.***> wrote: Hello I just installed a new arch linux and try to use docker to install leantime but everytime i try to use the install folder it throws me a 500 error? No mater which way I try? — Reply to this email directly, view it on GitHub <#2836>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ALG4EFXDLLCXBNWJWZURGVL2CY66XAVCNFSM6AAAAABSTZS7AWVHI2DSMVQWIX3LMV43ERDJONRXK43TNFXW4OZXGU3DQMBQGE> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[xNS5]

I was having similar issues with the 500 error. I first tried to install with just a docker-compose file, which only resulted in a 500 response. I tried cloning the docker repo and I was only able to get it working after setting up the .env variables prior to creating the containers + volumes for the first time.

Are there any constraints for the *_PASSWORD .env variables? I tried setting a few passwords with characters, symbols, and numbers and Leantime didn't seem to like that.

[jeanGambit]

Hi, I installed Leantime with docker-compose and also getting 500 response trying to do Step 7 when accessing <yourdomain.com>/install using the guide. Both containers looks healthy: I successfully connected to DB with DBeaver and was able to shell into the Leantime container. In the default configuration I only changed DB username and password.
Here is containers log:

❯ docker logs leantime
2025-01-19 14:53:55,063 CRIT Supervisor is running as root.  Privileges were not dropped because no user is specified in the config file.  If you intend to run as root, you can set user=root in the config file to avoid this message.
2025-01-19 14:53:55,063 CRIT Supervisor is running as root.  Privileges were not dropped because no user is specified in the config file.  If you intend to run as root, you can set user=root in the config file to avoid this message.
2025-01-19 14:53:55,069 INFO supervisord started with pid 7
2025-01-19 14:53:55,069 INFO supervisord started with pid 7
2025-01-19 14:53:56,071 INFO spawned: 'php-fpm' with pid 8
2025-01-19 14:53:56,071 INFO spawned: 'php-fpm' with pid 8
2025-01-19 14:53:56,073 INFO spawned: 'httpd' with pid 9
2025-01-19 14:53:56,073 INFO spawned: 'httpd' with pid 9
2025-01-19 14:53:56,073 INFO spawned: 'cron' with pid 10
2025-01-19 14:53:56,073 INFO spawned: 'cron' with pid 10
[19-Jan-2025 14:53:56] NOTICE: fpm is running, pid 8
[19-Jan-2025 14:53:56] NOTICE: ready to handle connections
2025-01-19 14:53:57,157 INFO success: php-fpm entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2025-01-19 14:53:57,157 INFO success: php-fpm entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2025-01-19 14:53:57,157 INFO success: httpd entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2025-01-19 14:53:57,157 INFO success: httpd entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2025-01-19 14:53:57,157 INFO success: cron entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2025-01-19 14:53:57,157 INFO success: cron entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

What else I can investigate to resolve the issue? I really don't want to do non-docker installation as I don't have time to support it later.

[marcelfolaron]

No? If there is a 500 that is originating from Leantime it will be logged in /var/html/www/storage/logs/ If there is nothing there the 500 is caused by something other than Leantime. How did you create the container? The docker compose file and then how did you set the configuration file? You would need to set the db host in addition to the username and password since the db is in it's own container.

[jeanGambit]

Yep, found the logs, seems like mysql_native_password plugin is missing, Here is a top of stacktrace:

[2025-01-20 09:36:34] production.ERROR: Can't connect to database  
[2025-01-20 09:36:34] production.ERROR: PDOException: SQLSTATE[HY000] [1524] Plugin 'mysql_native_password' is not loaded in /var/www/html/vendor/laravel/framework/src/
Illuminate/Database/Connectors/Connector.php:65
Stack trace:
#0 /var/www/html/vendor/laravel/framework/src/Illuminate/Database/Connectors/Connector.php(65): PDO->__construct('mysql:host=mysq...', 'lean-user', Object(SensitivePara
meterValue), Array)
#1 /var/www/html/vendor/laravel/framework/src/Illuminate/Database/Connectors/Connector.php(44): Illuminate\Database\Connectors\Connector->createPdoConnection('mysql:hos
t=mysq...', 'lean-user', 'admin', Array)
#2 /var/www/html/vendor/laravel/framework/src/Illuminate/Database/Connectors/MySqlConnector.php(24): Illuminate\Database\Connectors\Connector->createConnection('mysql:h
ost=mysq...', Array, Array)
#3 /var/www/html/vendor/laravel/framework/src/Illuminate/Database/Connectors/ConnectionFactory.php(184): Illuminate\Database\Connectors\MySqlConnector->connect(Array)
#4 [internal function]: Illuminate\Database\Connectors\ConnectionFactory->Illuminate\Database\Connectors\{closure}()
#5 /var/www/html/vendor/laravel/framework/src/Illuminate/Database/Connection.php(1339): call_user_func(Object(Closure))
#6 /var/www/html/app/Core/Db/Db.php(68): Illuminate\Database\Connection->getPdo()
#7 [internal function]: Leantime\Core\Db\Db->__construct('mysql')
#8 /var/www/html/vendor/laravel/framework/src/Illuminate/Container/Container.php(952): ReflectionClass->newInstanceArgs(Array)
#9 /var/www/html/vendor/laravel/framework/src/Illuminate/Container/Container.php(293): Illuminate\Container\Container->build('Leantime\\Core\\D...')
#10 /var/www/html/vendor/laravel/framework/src/Illuminate/Container/Container.php(908): Illuminate\Container\Container->Illuminate\Container\{closure}(Object(Leantime\C
ore\Application), Array)

I crated containers with docker-compose up -d
Only thing that I changed, as was asked in the guide, is DB credentials and name as follows:

# Database - MySQL container
MYSQL_ROOT_PASSWORD = 'admin'                # MySQL root password
MYSQL_DATABASE = 'leantime-db'               # Database name
MYSQL_USER = 'lean-user'                     # Database username
MYSQL_PASSWORD = 'admin'                     # Database password

# Database - leantime container
LEAN_DB_HOST = 'mysql_leantime'              # Database host
LEAN_DB_USER = 'lean-user'                   # Database username (needs to be the same as MYSQL_USER)
LEAN_DB_PASSWORD = 'admin'                   # Database password (needs to be the same as MYSQL_PASSWORD)
LEAN_DB_DATABASE = 'leantime-db'             # Database name (needs to be the same as MYSQL_DATABASE)
LEAN_DB_PORT = '3306'                        # Database port

[marcelfolaron]

That would be related to the mysql database/container you are using. What docker image are you using for mysql?

[jeanGambit]

  leantime_db:
    image: mysql:8.4
    container_name: mysql_leantime

[marcelfolaron]

Seems mysql 8.4 is disabling the mysql_native_password by default so you'd need to turn that on as you launch the container: docker-library/mysql#1048

As we are upgrading Laravel we should see support for the plugin being disabled