starred/nginx-proxy-manager-NginxProxyManager
1
0
Fork 0
mirror of https://github.com/NginxProxyManager/nginx-proxy-manager.git synced 2026-04-25 17:35:52 +03:00
Code Issues 937 Projects Releases 10 Packages Wiki Activity

[GH-ISSUE #5284] SQLLite issue - NOW #3159

New issue
Closed
opened 2026-02-26 07:37:59 +03:00 by kerem · 19 comments
kerem commented 2026-02-26 07:37:59 +03:00
Owner
Copy link

Originally created by @jsk01 on GitHub (Feb 6, 2026).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/5284

Issue creating a new setup with latest (v2.13.7). Upon submitting the new user there is a failure in the log related to the use of the NOW function which no longer exists in the version of sqllite used. I changed to version 2.13.6 and the new user was created.

Checklist

  • Have you pulled and found the error with jc21/nginx-proxy-manager:latest docker image?
    • Yes
  • Are you sure you're not using someone else's docker image?
    • Yes
  • Have you searched for similar issues (both open and closed)?
    • Yes

Operating System
Docker on Synology

Originally created by @jsk01 on GitHub (Feb 6, 2026). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/5284 Issue creating a new setup with latest (v2.13.7). Upon submitting the new user there is a failure in the log related to the use of the NOW function which no longer exists in the version of sqllite used. I changed to version 2.13.6 and the new user was created. **Checklist** - Have you pulled and found the error with `jc21/nginx-proxy-manager:latest` docker image? - Yes - Are you sure you're not using someone else's docker image? - Yes - Have you searched for similar issues (both open and closed)? - Yes **Operating System** Docker on Synology
kerem 2026-02-26 07:37:59 +03:00
  • closed this issue
  • added the
    bug
         label
kerem commented 2026-02-26 07:37:59 +03:00
Author
Owner
Copy link

@syrabo commented on GitHub (Feb 7, 2026):

I'm also seeing the following in the Docker logs: SQLITE_ERROR: no such function: NOW

I can't delete a certificate or edit an entry on the web interface, let alone create one.

Version: jc21/nginx-proxy-manager:latest
2.13.7

<!-- gh-comment-id:3864338671 --> @syrabo commented on GitHub (Feb 7, 2026): I'm also seeing the following in the Docker logs: SQLITE_ERROR: no such function: NOW I can't delete a certificate or edit an entry on the web interface, let alone create one. Version: jc21/nginx-proxy-manager:latest 2.13.7
kerem commented 2026-02-26 07:37:59 +03:00
Author
Owner
Copy link

@RndmJoker commented on GitHub (Feb 7, 2026):

I have the same bug. I cant create new hosts or update my ssl certificates. I alwas geht this error:

SQLITE_ERROR: no such function: NOW

Version jc21/nginx-proxy-manager:latest
2.13.7

<!-- gh-comment-id:3864983704 --> @RndmJoker commented on GitHub (Feb 7, 2026): I have the same bug. I cant create new hosts or update my ssl certificates. I alwas geht this error: SQLITE_ERROR: no such function: NOW Version jc21/nginx-proxy-manager:latest 2.13.7
kerem commented 2026-02-26 07:37:59 +03:00
Author
Owner
Copy link

@redghc commented on GitHub (Feb 7, 2026):

Same error here on user register onboarding.

- ℹ  info      Creating a new user in setup mode
- ⚠  warning   insert into `user` (`avatar`, `created_on`, `email`, `is_disabled`, `modified_on`, `name`, `nickname`, `roles`) values ('//www.gravatar.com/avatar/b642b4217b34b1e8d3bd915fc65c4452?default=mm', NOW(), 'test@test.com', 0, NOW(), 'test test', 'test', '["admin"]') - SQLITE_ERROR: no such function: NOW
<!-- gh-comment-id:3865113548 --> @redghc commented on GitHub (Feb 7, 2026): Same error here on user register onboarding. ``` - ℹ info Creating a new user in setup mode - ⚠ warning insert into `user` (`avatar`, `created_on`, `email`, `is_disabled`, `modified_on`, `name`, `nickname`, `roles`) values ('//www.gravatar.com/avatar/b642b4217b34b1e8d3bd915fc65c4452?default=mm', NOW(), 'test@test.com', 0, NOW(), 'test test', 'test', '["admin"]') - SQLITE_ERROR: no such function: NOW ```
kerem commented 2026-02-26 07:37:59 +03:00
Author
Owner
Copy link

@sleighton commented on GitHub (Feb 7, 2026):

sqlite3 never had a function NOW(). There's probably a UDF that got dropped or moved in the code that was there to keep the SQL statements compatible with mysql and postgres, which do have NOW().

<!-- gh-comment-id:3865190320 --> @sleighton commented on GitHub (Feb 7, 2026): sqlite3 never had a function NOW(). There's probably a UDF that got dropped or moved in the code that was there to keep the SQL statements compatible with mysql and postgres, which do have NOW().
kerem commented 2026-02-26 07:37:59 +03:00
Author
Owner
Copy link

@ajoosten commented on GitHub (Feb 7, 2026):

The issue is coming from this commit: github.com/NginxProxyManager/nginx-proxy-manager@77662b4e7f

The name of the sqliteClientName is changed from sqlite3 to better-sqlite3, and now the test in backend/models/now_helper.js is failing and the result is that the Now() function is returned also for SQLite databases. I could solve this locally by changing the name back.

@jc21 can you check this? You might have overseen this consequence ...

<!-- gh-comment-id:3865710778 --> @ajoosten commented on GitHub (Feb 7, 2026): The issue is coming from this commit: https://github.com/NginxProxyManager/nginx-proxy-manager/commit/77662b4e7f15f48c5fce4e2734444cb985e3c7b7 The name of the sqliteClientName is changed from sqlite3 to better-sqlite3, and now the test in backend/models/now_helper.js is failing and the result is that the Now() function is returned also for SQLite databases. I could solve this locally by changing the name back. @jc21 can you check this? You might have overseen this consequence ...
kerem commented 2026-02-26 07:37:59 +03:00
Author
Owner
Copy link

@N0tronic commented on GitHub (Feb 8, 2026):

+1

<!-- gh-comment-id:3867545351 --> @N0tronic commented on GitHub (Feb 8, 2026): +1
kerem commented 2026-02-26 07:37:59 +03:00
Author
Owner
Copy link

@Shaalan15 commented on GitHub (Feb 8, 2026):

+1

<!-- gh-comment-id:3867716479 --> @Shaalan15 commented on GitHub (Feb 8, 2026): +1
kerem commented 2026-02-26 07:37:59 +03:00
Author
Owner
Copy link

@mudora23 commented on GitHub (Feb 8, 2026):

Updating the config JSON file used from "client": "sqlite3" to "client": "better-sqlite3" fixes the issue. It is because isSqlite() was updated to only return true if the client name is "better-sqlite3".

<!-- gh-comment-id:3867877807 --> @mudora23 commented on GitHub (Feb 8, 2026): Updating the config JSON file used from `"client": "sqlite3"` to `"client": "better-sqlite3"` fixes the issue. It is because `isSqlite()` was updated to only return true if the client name is "better-sqlite3".
kerem commented 2026-02-26 07:37:59 +03:00
Author
Owner
Copy link

@malammar commented on GitHub (Feb 9, 2026):

This feels like a regression. Unless the docs specifically mention the need for better-sqlite3.

<!-- gh-comment-id:3869818449 --> @malammar commented on GitHub (Feb 9, 2026): This feels like a regression. Unless the docs specifically mention the need for `better-sqlite3`.
kerem commented 2026-02-26 07:37:59 +03:00
Author
Owner
Copy link

@robertschrs commented on GitHub (Feb 10, 2026):

Updating the config JSON file used from "client": "sqlite3" to "client": "better-sqlite3" fixes the issue. It is because isSqlite() was updated to only return true if the client name is "better-sqlite3".

Same issue on my end, "better-sqlite3" solved it. Running NPM in a docker container on a TrueNAS server.

<!-- gh-comment-id:3875167334 --> @robertschrs commented on GitHub (Feb 10, 2026): > Updating the config JSON file used from `"client": "sqlite3"` to `"client": "better-sqlite3"` fixes the issue. It is because `isSqlite()` was updated to only return true if the client name is "better-sqlite3". Same issue on my end, "better-sqlite3" solved it. Running NPM in a docker container on a TrueNAS server.
kerem commented 2026-02-26 07:37:59 +03:00
Author
Owner
Copy link

@7heMech commented on GitHub (Feb 14, 2026):

Huh, it seems like I can't reproduce this issue.
Is this vaild for new installations only?

<!-- gh-comment-id:3901335963 --> @7heMech commented on GitHub (Feb 14, 2026): Huh, it seems like I can't reproduce this issue. Is this vaild for new installations only?
kerem commented 2026-02-26 07:37:59 +03:00
Author
Owner
Copy link

@mudora23 commented on GitHub (Feb 14, 2026):

Huh, it seems like I can't reproduce this issue. Is this vaild for new installations only?

I remember someone reported that the issue also happens when creating additional users, which supposedly also calls NOW().

<!-- gh-comment-id:3901450622 --> @mudora23 commented on GitHub (Feb 14, 2026): > Huh, it seems like I can't reproduce this issue. Is this vaild for new installations only? I remember someone reported that the issue also happens when creating additional users, which supposedly also calls `NOW()`.
kerem commented 2026-02-26 07:37:59 +03:00
Author
Owner
Copy link

@7heMech commented on GitHub (Feb 14, 2026):

Huh, it seems like I can't reproduce this issue. Is this vaild for new installations only?

I remember someone reported that the issue also happens when creating additional users, which supposedly also calls NOW().

Yes, I tried everything mentioned above and more: creating, editing and deleting on hosts, certificates (no edits here) and users on a new and existing updated instance.

<!-- gh-comment-id:3901592375 --> @7heMech commented on GitHub (Feb 14, 2026): > > Huh, it seems like I can't reproduce this issue. Is this vaild for new installations only? > > I remember someone reported that the issue also happens when creating additional users, which supposedly also calls `NOW()`. Yes, I tried everything mentioned above and more: creating, editing and deleting on hosts, certificates (no edits here) and users on a new and existing updated instance.
kerem commented 2026-02-26 07:37:59 +03:00
Author
Owner
Copy link

@jsk01 commented on GitHub (Feb 14, 2026):

I had the issue on a new install. Went to previous version and got logged
in. Then updated to the latest version and had the same issue adding hosts
so I went back to the previous version. I haven't tried making the change
to the config file.

<!-- gh-comment-id:3902074329 --> @jsk01 commented on GitHub (Feb 14, 2026): I had the issue on a new install. Went to previous version and got logged in. Then updated to the latest version and had the same issue adding hosts so I went back to the previous version. I haven't tried making the change to the config file.
kerem commented 2026-02-26 07:37:59 +03:00
Author
Owner
Copy link

@YTKme commented on GitHub (Feb 15, 2026):

Updating the config JSON file used from "client": "sqlite3" to "client": "better-sqlite3" fixes the issue. It is because isSqlite() was updated to only return true if the client name is "better-sqlite3".

hi @mudora23, i am encountering the same issue, but where's the config JSON file located?

<!-- gh-comment-id:3903548954 --> @YTKme commented on GitHub (Feb 15, 2026): > Updating the config JSON file used from `"client": "sqlite3"` to `"client": "better-sqlite3"` fixes the issue. It is because `isSqlite()` was updated to only return true if the client name is "better-sqlite3". hi @mudora23, i am encountering the same issue, but where's the config JSON file located?
kerem commented 2026-02-26 07:37:59 +03:00
Author
Owner
Copy link

@RndmJoker commented on GitHub (Feb 16, 2026):

Huh, it seems like I can't reproduce this issue. Is this vaild for new installations only?

No i dont think so. My installation ist a few months old and it worked before.

<!-- gh-comment-id:3909745253 --> @RndmJoker commented on GitHub (Feb 16, 2026): > Huh, it seems like I can't reproduce this issue. Is this vaild for new installations only? No i dont think so. My installation ist a few months old and it worked before.
kerem commented 2026-02-26 07:37:59 +03:00
Author
Owner
Copy link

@7heMech commented on GitHub (Feb 17, 2026):

Should be fixed in the latest release. @jsk01 can you confirm and if so, close the issue?

<!-- gh-comment-id:3912786345 --> @7heMech commented on GitHub (Feb 17, 2026): Should be fixed in the latest release. @jsk01 can you confirm and if so, close the issue?
kerem commented 2026-02-26 07:37:59 +03:00
Author
Owner
Copy link

@jc21 commented on GitHub (Feb 17, 2026):

Interestingly, the CI builds perform complete setups using all 3 supported database types. And all passed with the better-sqlite3 change.

Is/was this only affecting users who have their own config json file in their data folder?

<!-- gh-comment-id:3917318665 --> @jc21 commented on GitHub (Feb 17, 2026): Interestingly, the CI builds perform complete setups using all 3 supported database types. And all passed with the `better-sqlite3` change. Is/was this only affecting users who have their own config json file in their `data` folder?
kerem commented 2026-02-26 07:37:59 +03:00
Author
Owner
Copy link

@jc21 commented on GitHub (Feb 17, 2026):

The commit above should resolve any lingering NOW issues regardless.

<!-- gh-comment-id:3917420320 --> @jc21 commented on GitHub (Feb 17, 2026): The commit above should resolve any lingering NOW issues regardless.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
develop
dependabot/npm_and_yarn/backend/liquidjs-10.25.7
dependabot/npm_and_yarn/frontend/prod-minor-updates-2a16bf3987
dependabot/npm_and_yarn/frontend/dev-patch-updates-754666cf41
dependabot/npm_and_yarn/backend/basic-ftp-5.3.0
dependabot/npm_and_yarn/test/follow-redirects-1.16.0
dependabot/npm_and_yarn/test/axios-1.15.0
dependabot/npm_and_yarn/frontend/lodash-4.18.1
dependabot/npm_and_yarn/backend/lodash-4.18.1
dependabot/npm_and_yarn/test/lodash-4.18.1
dependabot/npm_and_yarn/frontend/vite-7.3.2
dependabot/npm_and_yarn/backend/prod-minor-updates-5ec19a7f21
dependabot/npm_and_yarn/frontend/lodash-es-4.18.1
dependabot/npm_and_yarn/frontend/happy-dom-20.8.9
dependabot/npm_and_yarn/backend/path-to-regexp-8.4.0
dependabot/npm_and_yarn/frontend/picomatch-4.0.4
dependabot/npm_and_yarn/backend/picomatch-2.3.2
dependabot/npm_and_yarn/frontend/yaml-1.10.3
dependabot/npm_and_yarn/test/flatted-3.4.2
dependabot/npm_and_yarn/test/tar-7.5.11
dependabot/npm_and_yarn/frontend/immutable-5.1.5
master
dependabot/npm_and_yarn/test/glob-10.5.0
dependabot/npm_and_yarn/frontend/mdast-util-to-hast-13.2.1
dependabot/npm_and_yarn/test/form-data-4.0.4
v3-abandoned
bump-freedns
openidc
ssl-passthrough-hosts
static-content
v2.14.0
v2.13.7
v2.13.6
v2.13.5
v2.13.4
v2.13.3
v2.13.2
v2.13.1
v2.13.0
v2.12.6
v2.12.5
v2.12.4
v2.12.3
v2.12.2
v2.12.1
v2.12.0
v2.11.3
v2.11.2
v2.11.1
v2.11.0
v2.10.4
v2.10.3
v2.10.2
v2.10.1
v2.10.0
v2.9.22
v2.9.21
v2.9.20
v2.9.19
v2.9.18
v2.9.17
v2.9.16
v2.9.15
v2.9.14
v2.9.13
v2.9.12
v2.9.11
v2.9.10
v2.9.9
v2.9.8
v2.9.7
v2.9.6
v2.9.5
v2.9.4
v2.9.3
v2.9.2
v2.9.1
v2.9.0
v2.8.1
v2.8.0
v2.7.3
v2.7.2
v2.7.1
v2.7.0
v2.6.2
v2.6.1
v2.6.0
v2.5.0
v2.4.0
v2.3.1
v2.3.0
v2.2.4
v2.2.3
v2.2.2
v2.2.1
v2.2.0
v2.1.2
v2.1.1
v2.1.0
2.0.14
2.0.13
2.0.12
2.0.11
2.0.10
2.0.9
2.0.8
2.0.7
2.0.6
2.0.5
2.0.4
2.0.3
2.0.2
2.0.0
v2.0.0
1.1.2
1.1.1
1.0.1
Labels
Clear labels   
awaiting feedback

   
bug

   
cannot reproduce

   
dns provider request

   
duplicate

   
enhancement

   
enhancement

   
enhancement

   
good first issue

   
help wanted

   
invalid

   
need more info

   
no certbot plugin available

   
product-support

   
pull-request

Mirrored from GitHub Pull Request

  
question

   
stale

   
troll

   
upstream issue

   
v2

   
v2

   
v2

   
v3

   
wontfix
No labels
awaiting feedback
bug
cannot reproduce
dns provider request
duplicate
enhancement
enhancement
enhancement
good first issue
help wanted
invalid
need more info
no certbot plugin available
product-support
pull-request
question
stale
troll
upstream issue
v2
v2
v2
v3
wontfix
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/nginx-proxy-manager-NginxProxyManager#3159
No description provided.