search

jhonderson / actual-http-api

Basic Actual Budget API exposed through HTTP endpoints
MIT License
40 stars 9 forks source link

Permissions Issues Since Updating to Latest #18

Closed culpeppers closed 2 months ago

culpeppers commented 2 months ago

Since updating to latest version, seeing these errors in the actual-http-api logs:

PostError: PostError: unauthorized at throwIfNot200 (/usr/src/app/node_modules/@actual-app/api/dist/app/bundle.api.js:39687:31) at postBinary (/usr/src/app/node_modules/@actual-app/api/dist/app/bundle.api.js:39753:17) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) at async _fullSync (/usr/src/app/node_modules/@actual-app/api/dist/app/bundle.api.js:42602:35) at async /usr/src/app/node_modules/@actual-app/api/dist/app/bundle.api.js:42503:32 { type: 'PostError', reason: 'unauthorized', meta: undefined } PostError: PostError: unauthorized at throwIfNot200 (/usr/src/app/node_modules/@actual-app/api/dist/app/bundle.api.js:39687:31) at postBinary (/usr/src/app/node_modules/@actual-app/api/dist/app/bundle.api.js:39753:17) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) at async _fullSync (/usr/src/app/node_modules/@actual-app/api/dist/app/bundle.api.js:42602:35) at async /usr/src/app/node_modules/@actual-app/api/dist/app/bundle.api.js:42503:32 { type: 'PostError', reason: 'unauthorized', meta: undefined } unhandledRejection Error: We had an unknown problem opening “”. at handlers.api/sync (/usr/src/app/node_modules/@actual-app/api/dist/app/bundle.api.js:29500:27) at process.processTicksAndRejections (node:internal/process/task_queues:95:5)

Actual is on latest as well.

jhonderson commented 2 months ago

Hello @culpeppers , these errors are expected to happen from time to time (I am not really sure why, I am guessing some file or cache gets stuck or something). If you are running actual-http-api using docker, using the flag --restart=on-failure should take care of restarting the container whenever these failures happen.

Are you using docker?, if so, does this failure keep happening even after the container restarts?

I upgraded to latest (both containers) day before yesterday and it has been working for me. Initially it gave me some errors, I think it's because actual and actual-http-api needs to be upgraded at the same time, but after 1 min and 1 restart it started working again.

culpeppers commented 2 months ago

I'm using it on Unraid under Docker. Would I add that as an env variable, or as something else?

Thanks!

jhonderson commented 2 months ago

Reading few posts looks like there are extra parameters (or advanced options), where you can add the --restart=on-failure flag. Let me know if it works.

culpeppers commented 2 months ago

Sorry for the delay. Thank you for looking into that for me. Adding that did the trick, thank you!!