Milage may vary. GOLDEN RULE: BACK YOU DATA UP NO IF ANDS OR BUTS BEFORE ATTEMPTING! (Options Least to Most invasive) 1: Roll the docker image back to prior version, until image issue is resolved. 2: In the NGINX Proxy Manager UI, go to your proxy hosts, disable the cert, save, enable the cert save and check mark all 4 of the main boxes (or your flavor) this forces the .conf to update - Check proxy. 3: Confirm Port mappings in the container. 4. If that fails move check your DB for merge locks etc. This was causing my database version to be :none check DB version: docker logs <container_name> | grep "Current database version" # Set your database path here DB_PATH="/your/custom/path/to/database.sqlite" # 1. Back up the database cp "$DB_PATH" "${DB_PATH}.bak" # 2. Sync migrations sqlite3 "$DB_PATH" "INSERT INTO knex_migrations SELECT * FROM migrations;" # 3. Clear the lock sqlite3 "$DB_PATH" "UPDATE knex_migrations_lock SET is_locked = 0;" Some like this direct format more: # 1. Back up the existing database cp /path/to/nginxproxymanager/database.sqlite /path/to/nginxproxymanager/database.sqlite.bak # 2. Sync the old migrations table to the new knex_migrations table sqlite3 /path/to/nginxproxymanager/database.sqlite "INSERT INTO knex_migrations SELECT * FROM migrations;" # 3. Ensure the migration lock is cleared so NPM can boot sqlite3 /path/to/nginxproxymanager/database.sqlite "UPDATE knex_migrations_lock SET is_locked = 0;" #check DB version docker logs <container_name> | grep "Current database version" **If that is now showing a proper version and still failing do/check steps 2/3 again! Hope this help, this got me up and running, I obviously cant account for all scenarios & will advise once more BACK UP YOUR DATA!