[BUG] Updated Bookstack/MariaDB and cannot access the container anymore at set APP URL

[samschultzponsys]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

I had an update for the Linuxserv.io MariaDB container that is tied to my Linuxserver.io Bookstack instance. After performing the image update and the update command shown in the logs:
An upgrade is required on your databases. #

Stop any services that are accessing databases

in this container, and then run the command

mariadb-upgrade -u root -p

My Bookstack instance is no longer reachable and I am getting a 502 error.

Expected Behavior

Update images as normal and continue to use Bookstack.

Steps To Reproduce

1. Unraid environment with community apps, Utilizing MariaDB and Bookstack linuxserver.io images
2. Update MariaDB image
3. Restart MariaDB and Bookstack containers and lose access with 502 error.
4. Cannot post image of setup below please see here:
   

Environment

- OS: Unraid
- How docker service was installed: Native Docker implementation, not compose

CPU architecture

x86-64

Docker creation

Relevant settings for containers:

Container logs

MariaDB logs:

User UID:    99
User GID:    100
───────────────────────────────────────
Linuxserver.io version: 11.4.4-r1-ls167
Build-date: 2025-01-09T10:59:53+00:00
───────────────────────────────────────
    
[custom-init] No custom files found, skipping...
UMASK corrected from 022 to 0640 ...
250109 17:43:42 mysqld_safe Logging to '/config/databases/6d5b3c4b1fd8.err'.
250109 17:43:42 mysqld_safe Starting mariadbd daemon with databases from /config/databases
[ls.io-init] done.

Bookstack logs:

GID/UID
───────────────────────────────────────

User UID:    99
User GID:    100
───────────────────────────────────────
Linuxserver.io version: v24.12.1-ls186
Build-date: 2025-01-05T10:11:29+00:00
───────────────────────────────────────
    
using keys found in /config/keys
**** The following active confs have different version dates than the samples that are shipped. ****
**** This may be due to user customization or an update to the samples. ****
**** You should compare the following files to the samples in the same folder and update them. ****
**** Use the link at the top of the file to view the changelog. ****
┌────────────┬────────────┬────────────────────────────────────────────────────────────────────────┐
│  old date  │  new date  │ path                                                                   │
├────────────┼────────────┼────────────────────────────────────────────────────────────────────────┤
│ 2022-08-16 │ 2024-12-17 │ /config/nginx/nginx.conf                                               │
│ 2022-10-04 │ 2024-07-16 │ /config/nginx/site-confs/default.conf                                  │
│ 2022-08-20 │ 2024-12-06 │ /config/nginx/ssl.conf                                                 │
└────────────┴────────────┴────────────────────────────────────────────────────────────────────────┘
Waiting for DB to be available

   INFO  Nothing to migrate.  

[custom-init] No custom files found, skipping...
[ls.io-init] done.

[github-actions]

Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.

[j0nnymoe]

Have you ran through the update that mariadb is telling you to do?

[Roxedus]

You need to do the steps.

#           An upgrade is required on your databases.           #
#                                                               #
#         Stop any services that are accessing databases        #
#          in this container, and then run the command          #
#                                                               #
#             mariadb-upgrade -u root -p<PASSWORD>     

[samschultzponsys]

Yes since performing that I have been unable to access Bookstack, I tried redploying and the same thing happens.

[samschultzponsys]

If I redploy with the same db but to a different bookstack container at a different port and local IP, then run the commands to update the URL I can access the instance over the local IP but the login page is all broken and says there a problem.

[samschultzponsys]

Looking through some logs I am seeing this in the nginx log:

[samschultzponsys]

php logs:

[samschultzponsys]

I missed this at the top of the terminal log output:

2025/01/09 18:34:56 [warn] 304#304: the "listen ... http2" directive is deprecated, use the "http2" directive instead in /config/nginx/site-confs/default.conf:7
2025/01/09 18:34:56 [warn] 304#304: the "listen ... http2" directive is deprecated, use the "http2" directive instead in /config/nginx/site-confs/default.conf:8
[migrations] started
[migrations] 01-nginx-site-confs-default: skipped
[migrations] 02-default-location: skipped
[migrations] done
───────────────────────────────────────

[j0nnymoe]

Your container logs show that your nginx logs need updating, try that.

[thespad]

The combination definitely works because I've upgraded my own instance without issue.

The nginx errors look like standard bot spam rather than being related to any issue with the upgrade.

[samschultzponsys]

@j0nnymoe can you elaborate on what update I need to do? @thespad good to know the logs look ok. I am still at an impass on what to do.

My NPM Proxy logs do not look good:
2025/01/10 10:24:47 [error] 2933#2933: *777 connect() failed (111: Connection refused) while connecting to upstream, client: 192.168.0.1, server: kb.ponsys.com, request: "GET / HTTP/2.0", upstream: "http://192.168.0.5:6875/", host: "kb.ponsys.com", referrer: "https://192.168.0.252:81/"
2025/01/10 10:24:47 [error] 2933#2933: *777 connect() failed (111: Connection refused) while connecting to upstream, client: 192.168.0.1, server: kb.ponsys.com, request: "GET /favicon.ico HTTP/2.0", upstream: "http://192.168.0.5:6875/favicon.ico", host: "kb.ponsys.com"
2025/01/10 10:24:49 [error] 2933#2933: *777 connect() failed (111: Connection refused) while connecting to upstream, client: 192.168.0.1, server: kb.ponsys.com, request: "GET / HTTP/2.0", upstream: "http://192.168.0.5:6875/", host: "kb.ponsys.com"
2025/01/10 10:24:49 [error] 2933#2933: *777 connect() failed (111: Connection refused) while connecting to upstream, client: 192.168.0.1, server: kb.ponsys.com, request: "GET /favicon.ico HTTP/2.0", upstream: "http://192.168.0.5:6875/favicon.ico", host: "kb.ponsys.com"
2025/01/10 10:25:05 [error] 2933#2933: *777 connect() failed (111: Connection refused) while connecting to upstream, client: 192.168.0.1, server: kb.ponsys.com, request: "GET / HTTP/2.0", upstream: "http://192.168.0.5:6875/", host: "kb.ponsys.com"
2025/01/10 10:25:06 [error] 2933#2933: *777 connect() failed (111: Connection refused) while connecting to upstream, client: 192.168.0.1, server: kb.ponsys.com, request: "GET /favicon.ico HTTP/2.0", upstream: "http://192.168.0.5:6875/favicon.ico", host: "kb.ponsys.com"
2025/01/10 10:25:19 [error] 2933#2933: *777 connect() failed (111: Connection refused) while connecting to upstream, client: 192.168.0.1, server: kb.ponsys.com, request: "GET / HTTP/2.0", upstream: "http://192.168.0.5:6875/", host: "kb.ponsys.com"
2025/01/10 10:25:19 [error] 2933#2933: *777 connect() failed (111: Connection refused) while connecting to upstream, client: 192.168.0.1, server: kb.ponsys.com, request: "GET /favicon.ico HTTP/2.0", upstream: "http://192.168.0.5:6875/favicon.ico", host: "kb.ponsys.com"
2025/01/10 10:27:01 [error] 2934#2934: *816 connect() failed (111: Connection refused) while connecting to upstream, client: 185.165.44.39, server: kb.ponsys.com, request: "GET / HTTP/1.1", upstream: "http://192.168.0.5:6875/", host: "kb.ponsys.com"

Wouldnt this rejection be from the bookstack container itself?

[samschultzponsys]

This is in my custom nginx config:
#Hide info from server
proxy_hide_header Upgrade;
proxy_hide_header X-Powered-By;
#Security
add_header Content-Security-Policy "upgrade-insecure-requests";
add_header X-Frame-Options "SAMEORIGIN";
add_header X-XSS-Protection "1; mode=block" always;
add_header X-Content-Type-Options "nosniff" always;
add_header Cache-Control "no-transform, no-cache, no-store, must-revalidate" always;
add_header Pragma "no-cache" always;
add_header Expires "0" always;
add_header Referrer-Policy no-referrer always;
add_header X-Robots-Tag none;
add_header Strict-Transport-Security "max-age=31536000; includeSubDomains" always;
#Stop buffering from proxy server
proxy_request_buffering off;
#Streaming buffering off
proxy_buffering off;
#Specific url requests if you have any
rewrite ^/seafhttp(.*)$ $1 break;
#Bigger files request data
client_max_body_size 0;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-Proto $scheme;
#Increase Time-outs
proxy_connect_timeout 36000s;
proxy_send_timeout 36000s;
proxy_read_timeout 36000s;

[thespad]

A quick test is to expose the bookstack ports directly and see if you can connect to it that way (or if it gives you some kind of error)

Also check the laravel.log in /config/log to see if that contains anything that might indicate a cause.