github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-03-10 12:12:39 -05:00
Code Issues 250 Packages Projects Releases 53 Wiki Activity

[Bug]: SqliteError: no such table: auth #861

New Issue
Closed
opened 2026-02-28 19:22:25 -06:00 by GiteaMirror · 5 comments
GiteaMirror commented 2026-02-28 19:22:25 -06:00
Owner
Copy Link

Originally created by @stwalser on GitHub (Jan 8, 2024).

Verified issue does not already exist?

  • I have searched and found no existing issue

What happened?

After a fresh install upon choosing the server I get the message:
Server does not look like an Actual server. Is it set up correctly? in the web interface and the log of my local Docker container shows:

What error did you receive?

ERROR SqliteError: no such table: auth
at Database.prepare (/app/node_modules/better-sqlite3/lib/methods/wrappers.js:5:21)
at WrappedDatabase.all (file:///app/src/db.js:13:24)
at needsBootstrap (file:///app/src/account-db.js:24:24)
at file:///app/src/app-account.js:25:28
at Layer.handle [as handle_request] (/app/node_modules/express/lib/router/layer.js:95:5)
at next (/app/node_modules/express/lib/router/route.js:144:13)
at Route.dispatch (/app/node_modules/express/lib/router/route.js:114:3)
at Layer.handle [as handle_request] (/app/node_modules/express/lib/router/layer.js:95:5)
at /app/node_modules/express/lib/router/index.js:284:15
at Function.process_params (/app/node_modules/express/lib/router/index.js:346:12) {
code: 'SQLITE_ERROR'
}

Where are you hosting Actual?

Docker

What browsers are you seeing the problem on?

Safari

Operating System

Linux

Originally created by @stwalser on GitHub (Jan 8, 2024). ### Verified issue does not already exist? - [X] I have searched and found no existing issue ### What happened? After a fresh install upon choosing the server I get the message: _Server does not look like an Actual server. Is it set up correctly?_ in the web interface and the log of my local Docker container shows: ### What error did you receive? > ERROR SqliteError: no such table: auth > at Database.prepare (/app/node_modules/better-sqlite3/lib/methods/wrappers.js:5:21) > at WrappedDatabase.all (file:///app/src/db.js:13:24) > at needsBootstrap (file:///app/src/account-db.js:24:24) > at file:///app/src/app-account.js:25:28 > at Layer.handle [as handle_request] (/app/node_modules/express/lib/router/layer.js:95:5) > at next (/app/node_modules/express/lib/router/route.js:144:13) > at Route.dispatch (/app/node_modules/express/lib/router/route.js:114:3) > at Layer.handle [as handle_request] (/app/node_modules/express/lib/router/layer.js:95:5) > at /app/node_modules/express/lib/router/index.js:284:15 > at Function.process_params (/app/node_modules/express/lib/router/index.js:346:12) { > code: 'SQLITE_ERROR' > } ### Where are you hosting Actual? Docker ### What browsers are you seeing the problem on? Safari ### Operating System Linux
GiteaMirror added the bug label 2026-02-28 19:22:25 -06:00
GiteaMirror commented 2026-02-28 19:22:26 -06:00
Author
Owner
Copy Link

@purepani commented on GitHub (Feb 5, 2024):

@stwalser I've also been getting this error. Did you end up fixing it?

@purepani commented on GitHub (Feb 5, 2024): @stwalser I've also been getting this error. Did you end up fixing it?
GiteaMirror commented 2026-02-28 19:22:26 -06:00
Author
Owner
Copy Link

@stwalser commented on GitHub (Feb 6, 2024):

@purepani To be honest I am not sure anymore, but I think I just ended up deleting all files in the docker volumes.
The error occurred to me, when I tried to migrate the data from one device to another. Instead of copying the content of the /data and /config folders, I then exported the data in the GUI and imported it in the new instance.

@stwalser commented on GitHub (Feb 6, 2024): @purepani To be honest I am not sure anymore, but I think I just ended up deleting all files in the docker volumes. The error occurred to me, when I tried to migrate the data from one device to another. Instead of copying the content of the /data and /config folders, I then exported the data in the GUI and imported it in the new instance.
GiteaMirror commented 2026-02-28 19:22:26 -06:00
Author
Owner
Copy Link

@purepani commented on GitHub (Feb 11, 2024):

Hmm im getting this even after just deleting everything in the folders

@purepani commented on GitHub (Feb 11, 2024): Hmm im getting this even after just deleting everything in the folders
GiteaMirror commented 2026-02-28 19:22:26 -06:00
Author
Owner
Copy Link

@RyanHaoo commented on GitHub (Oct 16, 2024):

@stwalser I've also been getting this error. Did you end up fixing it?

Hi I got the same problem during a fresh install today and deleting all data on the server don't fix. Then I cleared all the cache and local storage in the browser and thing are going normally. BTW, I triggered the issue by assign customized serverFiles and userFiles configuration but forgot to manually set up the path.

Hope this may help!

@RyanHaoo commented on GitHub (Oct 16, 2024): > @stwalser I've also been getting this error. Did you end up fixing it? Hi I got the same problem during a fresh install today and deleting all data on the server don't fix. Then I cleared all the cache and local storage in the browser and thing are going normally. BTW, I triggered the issue by assign customized `serverFiles` and `userFiles` configuration but forgot to manually set up the path. Hope this may help!
GiteaMirror commented 2026-02-28 19:22:26 -06:00
Author
Owner
Copy Link

@tekumara commented on GitHub (Dec 21, 2024):

This happens when the bootstrap fails and is partially complete, so it isn't triggered again.

For me it happened because I had an empty server-files/ directory.

I had to remove server-files/ and also .migrate to prevent the migrations erroring with:

TypeError: Cannot open database because the directory does not exist

@tekumara commented on GitHub (Dec 21, 2024): This happens when the bootstrap fails and is partially complete, so it isn't triggered again. For me it happened because I had an empty `server-files/` directory. I had to remove `server-files/` and also `.migrate` to prevent the migrations erroring with: > TypeError: Cannot open database because the directory does not exist
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
AI generated
API
bank sync
budgeting
bug
can’t replicate
dependencies
docker
documentation
electron
experimental feature
feature
feedback
goal templates
good first issue
help wanted
importers
maintenance
needs info
needs testing
needs triage
needs votes
openid
payees
pull-request
Mirrored from GitHub Pull Request
 regression
reports
responsive
rules
schedules
server
✨ merged
split transactions
tech debt
theme
transaction import
transaction reconciliation
transactions
translations
upstream
user interface
✅ approved
wontfix
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/actual#861
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?