SQLLite issue - NOW

[jsk01]

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

[syrabo]

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

[RndmJoker]

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

[redghc]

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

[sleighton]

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().

[ajoosten]

The issue is coming from this commit: 77662b4

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 ...

[N0tronic]

+1

[Shaalan15]

+1

[mudora23]

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".

[malammar]

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

[robertschrs]

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.