Connection refused after docker pull

I am using the dockerfile to host the application.
I wanted to update to the latest version using docker-compose down && docker-compose pull && docker-compose up -d
Only by doing this I am no longer able to access the application through browser or smartphone app.

In a panic I did start modifying a ton of things, but with no success.
In firefox, I get the following network information

The laravel.log does not contain any recent errors, only the daily updating currencies and performing autobilling info’s

I attempted using the latest origin/master, and updating what is required in the README
I tried adjusting the nginx ports (but am not very experienced with nginx, so might have been useless)
I could not find nginx error logs

Any help would be hugely appreciated

EDIT

I was able to retrieve the nginx error logs and it seems to be an issue with the in-vhost.conf where http2 needed to be added differently.

The error has now changed to a 502 bad gateway. In the nginx error.log I find
connect() failed (error 111: Connection refused) while connecting to upstream

Hi,

@david do you have any suggestions?

@didier

You’ll want to do

docker-compose up

And watch the output in your terminal, the reason for the db not coming up will present in the logs.

Hi @david ,
Thank you for your reply.
I indeed do get db errors:

db_1       | 2023-07-16 07:08:39+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 8.0.33-1.el8 started.
db_1       | 2023-07-16 07:08:40+00:00 [Note] [Entrypoint]: Switching to dedicated user 'mysql'
db_1       | 2023-07-16 07:08:40+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 8.0.33-1.el8 started.
db_1       | '/var/lib/mysql/mysql.sock' -> '/var/run/mysqld/mysqld.sock'
db_1       | 2023-07-16T07:08:41.415540Z 0 [Warning] [MY-011068] [Server] The syntax '--skip-host-cache' is deprecated and will be removed in a future release. Please use SET GLOBAL host_cache_size=0 instead.
db_1       | 2023-07-16T07:08:41.418885Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.33) starting as process 1
db_1       | 2023-07-16T07:08:41.438030Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
db_1       | 2023-07-16T07:08:41.850403Z 1 [ERROR] [MY-012526] [InnoDB] Upgrade is not supported after a crash or shutdown with innodb_fast_shutdown = 2. This redo log was created with MySQL 5.7.42, and it appears logically non empty. Please follow the instructions at http://dev.mysql.com/doc/refman/8.0/en/upgrading.html
db_1       | 2023-07-16T07:08:41.851233Z 1 [ERROR] [MY-012930] [InnoDB] Plugin initialization aborted with error Generic error.
db_1       | 2023-07-16T07:08:42.188811Z 1 [ERROR] [MY-010334] [Server] Failed to initialize DD Storage Engine
db_1       | 2023-07-16T07:08:42.189303Z 0 [ERROR] [MY-010020] [Server] Data Dictionary initialization failed.
db_1       | 2023-07-16T07:08:42.189337Z 0 [ERROR] [MY-010119] [Server] Aborting
db_1       | 2023-07-16T07:08:42.190290Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 8.0.33)  MySQL Community Server - GPL.
db_1       | 2023-07-16 07:08:43+00:00 [Note] [Entrypoint]: Switching to dedicated user 'mysql'
db_1       | 2023-07-16 07:08:44+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 8.0.33-1.el8 started.
app_1      | 2023-07-16T07:08:44Z [INFO] [Entrypoint]: Initialising Invoice Ninja...
db_1       | '/var/lib/mysql/mysql.sock' -> '/var/run/mysqld/mysqld.sock'
db_1       | 2023-07-16T07:08:44.670990Z 0 [Warning] [MY-011068] [Server] The syntax '--skip-host-cache' is deprecated and will be removed in a future release. Please use SET GLOBAL host_cache_size=0 instead.
db_1       | 2023-07-16T07:08:44.673388Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.33) starting as process 1
db_1       | 2023-07-16T07:08:44.683381Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
db_1       | 2023-07-16T07:08:45.000417Z 1 [ERROR] [MY-012526] [InnoDB] Upgrade is not supported after a crash or shutdown with innodb_fast_shutdown = 2. This redo log was created with MySQL 5.7.42, and it appears logically non empty. Please follow the instructions at http://dev.mysql.com/doc/refman/8.0/en/upgrading.html
db_1       | 2023-07-16T07:08:45.001384Z 1 [ERROR] [MY-012930] [InnoDB] Plugin initialization aborted with error Generic error.
db_1       | 2023-07-16T07:08:45.391640Z 1 [ERROR] [MY-010334] [Server] Failed to initialize DD Storage Engine
db_1       | 2023-07-16T07:08:45.392967Z 0 [ERROR] [MY-010020] [Server] Data Dictionary initialization failed.
db_1       | 2023-07-16T07:08:45.393668Z 0 [ERROR] [MY-010119] [Server] Aborting
db_1       | 2023-07-16T07:08:45.394994Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 8.0.33)  MySQL Community Server - GPL.
app_1      | In Connection.php line 760:
app_1      |
app_1      |   SQLSTATE[HY000] [2002] php_network_getaddresses: getaddrinfo for db failed:
app_1      |    Name does not resolve (SQL: select * from information_schema.tables where
app_1      |   table_schema = ninja and table_name = accounts and table_type = 'BASE TABLE
app_1      |   ')
app_1      |
app_1      |
app_1      | In Connector.php line 70:
app_1      |
app_1      |   SQLSTATE[HY000] [2002] php_network_getaddresses: getaddrinfo for db failed:
app_1      |    Name does not resolve
app_1      |
app_1      |
app_1      | In Connector.php line 70:
app_1      |
app_1      |   PDO::__construct(): php_network_getaddresses: getaddrinfo for db failed: Na
app_1      |   me does not resolve

Looks like a dns resolution issue from within your container.

Hi @david ,
I was unable to resolve the issue. I restored the system using a recent backup instead.