Database could not be configured #482

Feuersteinium · 2022-06-06T19:33:38Z

Feuersteinium
Jun 6, 2022

Hello, i,ve got a problem whilst installing LinkAce. The installation works perfektly fine until i get to the page "Database Configuration"
I get an error like this (All Database information is correct):

Then i looked at the local IP adress of the Database:

The Docker Container cannot reach the Database, because the Database is every time i tried the installation not at the right ip address.
My docker-compose is:

version: "3"

services:

  
  # --- LinkAce Image with PHP 7.4 and nginx
  app:
    image: linkace/linkace:simple
    restart: unless-stopped
    depends_on:
      - db
    ports:
      - 19994:80
    volumes:
      - ./.env:/app/.env
      - linkace_logs:/app/storage/logs
   # --- MariaDB
  db:
    image: mariadb:10.5
    restart: unless-stopped
    command: mysqld --character-set-server=utf8mb4 --collation-server=utf8mb4_bin
    environment:
      - MYSQL_ROOT_PASSWORD=${DB_PASSWORD}
      - MYSQL_USER=${DB_USERNAME}
      - MYSQL_PASSWORD=${DB_PASSWORD}
      - MYSQL_DATABASE=${DB_DATABASE}
    volumes:
      - db:/var/lib/mysql

volumes:
  linkace_logs:
  db:
    driver: local

My .env file is

## LINKACE CONFIGURATION

## Basic app configuration
# The application name is used internally and may not be changed
APP_NAME=LinkAce
COMPOSE_PROJECT_NAME=linkace
# The URL should be set if you notice issues with URLs generated by Laravel, which might be an issue with
# nginx configuration or the proxy you use.
APP_URL=http://localhost
# The environment is usually 'production' but may be changed to 'local' for development
APP_ENV=production
# The app key is generated later, please leave it blank
APP_KEY=base64:wK9inf8o4KfYp7Jqx7iJA+2UJglSFzIxkozpGPR+gSs=
# Enable the debug more if you are running into issues or while developing
APP_DEBUG=false
# Set to true, if you are using a proxy that terminates SSL. Required to get the correct URLs for LinkAce
FORCE_HTTPS=false
# Indicates that the setup was completed and the app can be used now
SETUP_COMPLETED=false
# Set the time after a session expires automatically, in minutes. Default is 7 days.
SESSION_LIFETIME=10080


## Backup configuration
# Enable backups here
BACKUP_ENABLED=false
# Choose the destination of the backup. If you set up AWS S3 credentials below you may choose 's3' which is used
# as a synonym for AWS. Leave blank or set to 'local' if you want to store backups within /storage/app/backups.
BACKUP_DISK=s3
# Set to false if you do not want to be notified about successful or broken backups
BACKUP_NOTIFICATIONS=true
# The notification email may be used to get backup notifications
[email protected]
# Maximum size of all backups in megabytes
BACKUP_MAX_SIZE=512


## Amazon Web Services (AWS) S3 configuration
# Define the key ID, the access key, the region and your bucket name here if you want to use AWS S3 for backups
AWS_ACCESS_KEY_ID=
AWS_SECRET_ACCESS_KEY=
AWS_DEFAULT_REGION=us-east-1
AWS_BUCKET=


## Mail configuration
[email protected]
MAIL_FROM_NAME=LinkAce
# Set the driver used for sending email here, default is `smtp`
MAIL_DRIVER=smtp
# Set the SMTP host and its port here
MAIL_HOST=smtp.mailtrap.io
MAIL_PORT=2525
# Set the username used to connect to the SMTP server here
MAIL_USERNAME=null
# Set the password used to connect to the SMTP server here
MAIL_PASSWORD=null
# If your SMTP server uses encrypted connections, enable it here by setting the variable to `tls`
MAIL_ENCRYPTION=null


## Configuration of the database connection
## If you are using the standard configuration provided by LinkAce, you can leave all values except the password as
## they are. Docker will automatically create a linkace database and a corresponding user.
DB_CONNECTION=mysql
DB_HOST=db
DB_PORT=3306
DB_DATABASE=linkace
# Even if you use the standard configuration, please set a secure password here.
DB_USERNAME=linkace
DB_PASSWORD=


## Redis cache configuration
# Set the Redis connection here if you want to use it
REDIS_HOST=redis
REDIS_PASSWORD=
REDIS_PORT=6379


## You probably do not want to change any values blow. Only continue if you know what you are doing.
# Configure various driver
SESSION_DRIVER=file
LOG_CHANNEL=stack
BROADCAST_DRIVER=log
CACHE_DRIVER=file
QUEUE_DRIVER=database

## Using Redis sockets
# If you want to use Redis via a Unix socket, you can remove the hash before the following lines, but remove one before
# the "CACHE_DRIVER" line above. Also, set a proper path to your Redis socket.
#CACHE_DRIVER=redis-socket
#SESSION_CONNECTION=redis-socket
#REDIS_SCHEME=unix
#REDIS_PATH=/path/to/redis.sock

The Password is only written in capital letters, lowercase letters and in numbers (ca. 64 Charakters long)

What can i do tho fix this? How can Linkace use the right ip address to reach the Database

Thanks in advance.

Answered by Feuersteinium

Jun 6, 2022

I guess it wasn't the Problem, there is still the same issue:

The Config is now:

## LINKACE CONFIGURATION

## Basic app configuration
COMPOSE_PROJECT_NAME=linkace
# The app key is generated later, please leave it blank
APP_KEY=base64:sA8ozN00/orjfLu+tjJvcr9+/IMsdDtsMwjwUs/2rv4=

## Configuration of the database connection
## Attention: Those settings are configured during the web setup, please do not modify them now.
# Set the database driver (mysql, pgsql, sqlsrv)
DB_CONNECTION=mysql
# Set the host of your database here
DB_HOST=db
# Set the port of your database here
DB_PORT=3306
# Set the database name here
DB_DATABASE=linkace
# Set both username and password of the user accessing the…

View full answer

Kovah · 2022-06-06T19:54:52Z

Kovah
Jun 6, 2022
Maintainer

Those seem to be some old setup files. Please try it with the official package downloadable from the releases page: https://github.com/Kovah/LinkAce/releases/tag/v1.10.1

0 replies

Feuersteinium · 2022-06-06T21:35:42Z

Feuersteinium
Jun 6, 2022
Author

I guess it wasn't the Problem, there is still the same issue:

The Config is now:

## LINKACE CONFIGURATION

## Basic app configuration
COMPOSE_PROJECT_NAME=linkace
# The app key is generated later, please leave it blank
APP_KEY=base64:sA8ozN00/orjfLu+tjJvcr9+/IMsdDtsMwjwUs/2rv4=

## Configuration of the database connection
## Attention: Those settings are configured during the web setup, please do not modify them now.
# Set the database driver (mysql, pgsql, sqlsrv)
DB_CONNECTION=mysql
# Set the host of your database here
DB_HOST=db
# Set the port of your database here
DB_PORT=3306
# Set the database name here
DB_DATABASE=linkace
# Set both username and password of the user accessing the database
DB_USERNAME=linkace
DB_PASSWORD=

## Redis cache configuration
# Set the Redis connection here if you want to use it
REDIS_HOST=redis
REDIS_PASSWORD=
REDIS_PORT=6379

version: "3"

services:

  # --- MariaDB
  db:
    image: mariadb:10.7
    restart: unless-stopped
    command: mysqld --character-set-server=utf8mb4 --collation-server=utf8mb4_bin
    environment:
      - MYSQL_ROOT_PASSWORD=${DB_PASSWORD}
      - MYSQL_USER=${DB_USERNAME}
      - MYSQL_PASSWORD=${DB_PASSWORD}
      - MYSQL_DATABASE=${DB_DATABASE}
    volumes:
      - db:/var/lib/mysql

  # --- LinkAce Image with PHP and nginx
  app:
    image: linkace/linkace:simple
    restart: unless-stopped
    depends_on:
      - db
    ports:
      - "19994:80"
     # - "19443:443"
    volumes:
      - ./.env:/app/.env
      - linkace_logs:/app/storage/logs
      # Remove the hash of the following line if you want to use HTTPS for this container
      #- ./nginx-ssl.conf:/etc/nginx/conf.d/default.conf:ro
      #- /path/to/your/ssl/certificates:/certs:ro
      # Remove the hash of the following line if you want to use local backups
      #- ./backups:/app/storage/app/backups


volumes:
  linkace_logs:
  db:
    driver: local

And the logs of the Database are:

2022-06-06 21:29:02+00:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:10.7.4+maria~focal started.
2022-06-06 21:29:02+00:00 [Note] [Entrypoint]: Switching to dedicated user 'mysql'
2022-06-06 21:29:02+00:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:10.7.4+maria~focal started.
2022-06-06 21:29:03+00:00 [Note] [Entrypoint]: MariaDB upgrade not required
2022-06-06 21:29:03 0 [Note] mysqld (server 10.7.4-MariaDB-1:10.7.4+maria~focal) starting as process 1 ...
2022-06-06 21:29:03 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2022-06-06 21:29:03 0 [Note] InnoDB: Number of transaction pools: 1
2022-06-06 21:29:03 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions
2022-06-06 21:29:03 0 [Note] mysqld: O_TMPFILE is not supported on /tmp (disabling future attempts)
2022-06-06 21:29:03 0 [Note] InnoDB: Using Linux native AIO
2022-06-06 21:29:03 0 [Note] InnoDB: Initializing buffer pool, total size = 134217728, chunk size = 134217728
2022-06-06 21:29:03 0 [Note] InnoDB: Completed initialization of buffer pool
2022-06-06 21:29:03 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=44322,44322
2022-06-06 21:29:03 0 [Note] InnoDB: 128 rollback segments are active.
2022-06-06 21:29:03 0 [Note] InnoDB: Removed temporary tablespace data file: "./ibtmp1"
2022-06-06 21:29:03 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2022-06-06 21:29:03 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2022-06-06 21:29:03 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
2022-06-06 21:29:03 0 [Note] InnoDB: 10.7.4 started; log sequence number 44406; transaction id 16
2022-06-06 21:29:03 0 [Note] Plugin 'FEEDBACK' is disabled.
2022-06-06 21:29:03 0 [Warning] You need to use --log-bin to make --expire-logs-days or --binlog-expire-logs-seconds work.
2022-06-06 21:29:03 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
2022-06-06 21:29:03 0 [Note] Server socket created on IP: '0.0.0.0'.
2022-06-06 21:29:03 0 [Note] Server socket created on IP: '::'.
2022-06-06 21:29:03 0 [Note] InnoDB: Buffer pool(s) load completed at 220606 21:29:03
2022-06-06 21:29:03 0 [Note] mysqld: ready for connections.
Version: '10.7.4-MariaDB-1:10.7.4+maria~focal'  socket: '/run/mysqld/mysqld.sock'  port: 3306  mariadb.org binary distribution
2022-06-06 21:29:12 3 [Warning] Access denied for user 'linkace'@'192.168.96.3' (using password: YES)
2022-06-06 21:29:12 4 [Warning] Access denied for user 'linkace'@'192.168.96.3' (using password: YES)
2022-06-06 21:29:12 5 [Warning] Access denied for user 'linkace'@'192.168.96.3' (using password: YES)
2022-06-06 21:29:23 6 [Warning] Access denied for user 'linkace'@'192.168.96.3' (using password: YES)
2022-06-06 21:29:23 7 [Warning] Access denied for user 'linkace'@'192.168.96.3' (using password: YES)
2022-06-06 21:29:24 8 [Warning] Access denied for user 'linkace'@'192.168.96.3' (using password: YES)
2022-06-06 21:29:24 9 [Warning] Access denied for user 'linkace'@'192.168.96.3' (using password: YES)
2022-06-06 21:29:26 10 [Warning] Access denied for user 'linkace'@'192.168.96.3' (using password: YES)
2022-06-06 21:29:26 11 [Warning] Access denied for user 'linkace'@'192.168.96.3' (using password: YES)
2022-06-06 21:29:26 12 [Warning] Access denied for user 'linkace'@'192.168.96.3' (using password: YES)
2022-06-06 21:29:26 13 [Warning] Access denied for user 'linkace'@'192.168.96.3' (using password: YES)
2022-06-06 21:29:26 14 [Warning] Access denied for user 'linkace'@'192.168.96.3' (using password: YES)
2022-06-06 21:29:26 15 [Warning] Access denied for user 'linkace'@'192.168.96.3' (using password: YES)

4 replies

Kovah Jun 6, 2022
Maintainer

You could try to delete the database docker volume after stopping the database container and then try again. Maybe something was wrongly created.
docker-compose down > docker volume rm linkace_db > docker-compose up -d

martadinata666 Jun 7, 2022

DB_PASSWORD empty is it intended?

Feuersteinium Jun 7, 2022
Author

Yes the missing Password is intended, in my .env File on the Server its existing.
Now i deleted the volumes (instead of just deleting the containers and starting the docker-compose again) and the containers and started it again with the docker-compose. And i removed the App_Key and also generated a now one. Now everything is working seemless.
Thank you very much!

martadinata666 Jun 7, 2022

ah i see, because there is also another discussion, the password using special character, it also became issue. Glad you made it work.

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Database could not be configured #482

{{title}}

Replies: 2 comments 4 replies

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

Select a reply

Database could not be configured #482

Feuersteinium Jun 6, 2022

Replies: 2 comments · 4 replies

Kovah Jun 6, 2022 Maintainer

Feuersteinium Jun 6, 2022 Author

Kovah Jun 6, 2022 Maintainer

martadinata666 Jun 7, 2022

Feuersteinium Jun 7, 2022 Author

martadinata666 Jun 7, 2022

Feuersteinium
Jun 6, 2022

Replies: 2 comments 4 replies

Kovah
Jun 6, 2022
Maintainer

Feuersteinium
Jun 6, 2022
Author

Kovah Jun 6, 2022
Maintainer

Feuersteinium Jun 7, 2022
Author