Nginx runs, but cannot access running configuration

[ThePatricide]

I've been running the Nginx Proxy Manager add-on for quite some time now. I wanted to add an extra redirection host, so I wanted to login to Nginx. However, apparently it doesn't know my user anymore. So I was a bit startled and tried the default login (admin/changeme). That somehow worked and I ended up in a clean Nginx environment, without any redirects. However, all my current redirects still seem to be working. I wouldn't like trying to reset the database to see if that fixes it (and need to configure everything again) before asking for some support first.

I'd expect to come in my running environment configuration, most likely stored in my MariaDB add-on database. It seems however that it runs an instance in the background that actually uses my correct configuration, that I cannot approach. And when I login to Nginx admin panel, it access another, empty database that does not actually run the reverse proxy. The log seems to hint at least at the latter, but I cannot find any hint in the logging on the running config.

I've restarted the whole of Home Assistant and looking for the smartest thing to do. My config is clearly not gone, as it works fine, but I cannot access it.
To add to the below: 192.168.1.17 is my HASS OS machine, .72 is the machine I'm accessing HA from. With 192.168.1.17:81 I end up in the empty configuration.

It of course has worked perfectly before, as I've configured it and it is still running. I don't know how I can dig into MariaDB some more to see how things are running.

Log:

s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
cont-init: info: running /etc/cont-init.d/00-banner.sh
-----------------------------------------------------------
 Add-on: Nginx Proxy Manager
 Manage Nginx proxy hosts with a simple, powerful interface
-----------------------------------------------------------
 Add-on version: 0.12.3
 You are running the latest version of this add-on.
 System: Home Assistant OS 8.4  (amd64 / generic-x86-64)
 Home Assistant Core: 2023.3.3
 Home Assistant Supervisor: 2023.03.1
-----------------------------------------------------------
 Please, share the above information when looking for help
 or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
cont-init: info: /etc/cont-init.d/00-banner.sh exited 0
cont-init: info: running /etc/cont-init.d/01-log-level.sh
cont-init: info: /etc/cont-init.d/01-log-level.sh exited 0
cont-init: info: running /etc/cont-init.d/mysql.sh
cont-init: info: /etc/cont-init.d/mysql.sh exited 0
cont-init: info: running /etc/cont-init.d/nginx.sh
cont-init: info: /etc/cont-init.d/nginx.sh exited 0
cont-init: info: running /etc/cont-init.d/npm.sh
cont-init: info: /etc/cont-init.d/npm.sh exited 0
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
services-up: info: copying legacy longrun manager (no readiness notification)
services-up: info: copying legacy longrun nginx (no readiness notification)
s6-rc: info: service legacy-services successfully started
[10:19:00] INFO: Starting the Manager...
[10:19:00] INFO: Starting NGinx...
2023/03/21 10:19:00 [error] 292#292: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 192.168.1.72, server: nginxproxymanager, request: "GET /api/ HTTP/1.1", upstream: "http://127.0.0.1:3000/", host: "192.168.1.17:81", referrer: "http://192.168.1.17:81/settings"
[3/21/2023] [10:19:00 AM] [Global   ] › ℹ  info      No valid environment variables for database provided, using default SQLite file '/data/database.sqlite'
[3/21/2023] [10:19:00 AM] [Global   ] › ℹ  info      Generating SQLite knex configuration
[3/21/2023] [10:19:00 AM] [Global   ] › ⬤  debug     Wrote db configuration to config file: ./config/production.json
2023/03/21 10:19:01 [error] 292#292: *10 connect() failed (111: Connection refused) while connecting to upstream, client: 192.168.1.72, server: nginxproxymanager, request: "GET /api/ HTTP/1.1", upstream: "http://127.0.0.1:3000/", host: "192.168.1.17:81", referrer: "http://192.168.1.17:81/nginx/access"
2023/03/21 10:19:01 [error] 292#292: *10 connect() failed (111: Connection refused) while connecting to upstream, client: 192.168.1.72, server: nginxproxymanager, request: "GET /api/ HTTP/1.1", upstream: "http://127.0.0.1:3000/", host: "192.168.1.17:81", referrer: "http://192.168.1.17:81/nginx/redirection"
[3/21/2023] [10:19:03 AM] [Migrate  ] › ℹ  info      Current database version: none
[3/21/2023] [10:19:03 AM] [Setup    ] › ℹ  info      Logrotate Timer initialized
[3/21/2023] [10:19:03 AM] [Setup    ] › ℹ  info      Logrotate completed.
[3/21/2023] [10:19:03 AM] [IP Ranges] › ℹ  info      Fetching IP Ranges from online services...
[3/21/2023] [10:19:03 AM] [IP Ranges] › ℹ  info      Fetching https://ip-ranges.amazonaws.com/ip-ranges.json
2023/03/21 10:19:04 [error] 292#292: *10 connect() failed (111: Connection refused) while connecting to upstream, client: 192.168.1.72, server: nginxproxymanager, request: "GET /api/ HTTP/1.1", upstream: "http://127.0.0.1:3000/", host: "192.168.1.17:81", referrer: "http://192.168.1.17:81/nginx/access"
[3/21/2023] [10:19:05 AM] [IP Ranges] › ℹ  info      Fetching https://www.cloudflare.com/ips-v4
[3/21/2023] [10:19:06 AM] [IP Ranges] › ℹ  info      Fetching https://www.cloudflare.com/ips-v6
[3/21/2023] [10:19:06 AM] [SSL      ] › ℹ  info      Let's Encrypt Renewal Timer initialized
[3/21/2023] [10:19:06 AM] [SSL      ] › ℹ  info      Renewing SSL certs close to expiry...
[3/21/2023] [10:19:06 AM] [IP Ranges] › ℹ  info      IP Ranges Renewal Timer initialized
[3/21/2023] [10:19:06 AM] [Global   ] › ℹ  info      Backend PID 266 listening on port 3000 ...
`QueryBuilder#allowEager` method is deprecated. You should use `allowGraph` instead. `allowEager` method will be removed in 3.0
`QueryBuilder#eager` method is deprecated. You should use the `withGraphFetched` method instead. `eager` method will be removed in 3.0
QueryBuilder#omit is deprecated. This method will be removed in version 3.0
Model#$omit is deprected and will be removed in 3.0.
[3/21/2023] [10:19:10 AM] [Nginx    ] › ℹ  info      Reloading Nginx
[3/21/2023] [10:19:10 AM] [SSL      ] › ℹ  info      Renew Complete

[ThePatricide]

I know see this is an existing issue that was literally closed minutes before I was looking for this issue:
#344
Can that one be reopened? I'll try a reinstall.

[ThePatricide]

A reinstall has made it possible to reach the configuration again. Now the reverse proxy however seems broken. Will see if I can fix it and get back to the other topic.