Error When Deleting a Proxy Host

[Discolor3182]

Getting this error when deleting a proxy host on version 2.14.0.

Any ideas what is causing this?

Thanks.

[nishchayjeet]

Can you share console logs?

[Discolor3182]

This is the error in the log when I delete a proxy host

[2/26/2026] [7:43:00 AM] [Express ] › ⚠ warning update proxy_host set is_deleted = 1, modified_on = NOW() where id = 131 - SQLITE_ERROR: no such function: NOW

[nishchayjeet]

It looks like the SQLite error might be related to a database migration issue. To help troubleshoot further, could you provide the following?

1. Docker logs — Can you run the following command and share the output?

docker logs > npm_logs.txt

This will save the full container logs to a file so we can review them.

2. Is the error happening on all proxy hosts or just specific ones? Try deleting a different proxy host and let me know if you get the same error.

3. Volume mapping — Can you share your docker-compose.yml file (or the relevant volume section)? I want to make sure the data directory is mapped correctly and not pointing to a stale or leftover database from a previous installation.

[Schu-]

Hi. I also have noticed this as well when trying to update, delete a host after upgrade. Here is some more information to help. It seems to happen on any host. Not just the one I provided the error on.

Errors in the log:
ngxpm STDOUT [2/27/2026] [2:11:20 PM] [Express ] › ⚠ warning update proxy_hostsetid= 43,created_on= '2025-12-06 18:10:38',modified_on= NOW(),owner_user_id= 1,domain_names= '["patchmon.domain.com"]',forward_host= 'patchmon-fe',forward_port= 3000,access_list_id= 0,certificate_id= '6',ssl_forced= 1,caching_enabled= 0,block_exploits= 0,advanced_config= '',meta= '{"nginx_online":true,"nginx_err":null}',allow_websocket_upgrade= 1,http2_support= 1,forward_scheme= 'http',enabled= 1,locations= '[]',hsts_enabled= 0,hsts_subdomains= 0,trust_forwarded_proto= 0 whereid` = 43 - SQLITE_ERROR: no such function: NOW

ngxpm
STDOUT
[2/27/2026] [2:11:32 PM] [Express ] › ⚠ warning update proxy_host set id = 23, created_on = '2022-07-05 20:33:14', modified_on = NOW(), owner_user_id = 1, domain_names = '["home.domain.com"]', forward_host = 'HACore', forward_port = 8123, access_list_id = 0, certificate_id = '6', ssl_forced = 1, caching_enabled = 0, block_exploits = 0, advanced_config = 'proxy_bind 172.22.0.150;', meta = '{"letsencrypt_agree":false,"dns_challenge":false,"nginx_online":true,"nginx_err":null}', allow_websocket_upgrade = 0, http2_support = 0, forward_scheme = 'http', enabled = 1, locations = '[]', hsts_enabled = 0, hsts_subdomains = 0, trust_forwarded_proto = 0 where id = 23 - SQLITE_ERROR: no such function: NOW
`

services: ngxpm: image: jc21/nginx-proxy-manager:latest container_name: ngxpm restart: always networks: docker: ipv4_address: IP ngxpm: ipv4_address: IP volumes: - /docker/ngxpm/config/config.json:/app/config/production.json - /docker/ngxpm/data:/data - /docker/ngxpm/letsencrypt:/etc/letsencrypt - /docker/ngxpm/html:/html - /docker/ngxpm/ssl:/ssl environment: # if you want pretty colors in your docker logs: - FORCE_COLOR=1 networks: docker: external: true ngxpm: external: true

Just to add. This instance has been working w/o issues for over 1 year now, and I had made some updates to this host the other day before the upgrade to the new release. Not sure if others are having this issue or its somehow just setup related.

[Schu-]

Just to add to this bug since I currently have 5 minutes to look more. I did check my other NGXPM instance and that one works without issues. No real difference between the hosts. I am wondering if the upgrade did not run correctly on the host in question with the issues.

[Schu-]

Just another update to this issue. I have restored my ngxpm instance back to 2.13.6. On this version it works without issues. When upgrading to version 2.13.7 or 2.14.0 the DB errors and problems start. For right now I am going to stick on 2.13.6. Either this is a larger issue that needs to be worked out or for some reason these builds are not working on my host. Just wanted to leave this hear for anyone else having issues.

[Discolor3182]

Just another update to this issue. I have restored my ngxpm instance back to 2.13.6. On this version it works without issues. When upgrading to version 2.13.7 or 2.14.0 the DB errors and problems start. For right now I am going to stick on 2.13.6. Either this is a larger issue that needs to be worked out or for some reason these builds are not working on my host. Just wanted to leave this hear for anyone else having issues.

Reverted to 2.13.6 and it is now working.