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

[Bug]: cannot connect using OpenID #2401

New Issue
Closed
opened 2026-02-28 20:12:53 -06:00 by GiteaMirror · 3 comments
GiteaMirror commented 2026-02-28 20:12:53 -06:00
Owner
Copy Link

Originally created by @AlexT59 on GitHub (Aug 18, 2025).

Verified issue does not already exist?

  • I have searched and found no existing issue

What happened?

I'm unable to connect to the server using the OpenID option.

I configured it two weeks ago using PocketID, and it worked correctly immediately after configuration. I havn't used it since.

logs from the server

Logging in via openid
Error setting up OpenID client: RPError: outgoing request timed out after 3500ms
    at /app/node_modules/openid-client/lib/helpers/request.js:140:13
    at async Issuer.discover (/app/node_modules/openid-client/lib/issuer.js:144:22)
    at async setupOpenIdClient (file:///app/src/accounts/openid.js:53:11)
    at async loginWithOpenIdSetup (file:///app/src/accounts/openid.js:101:18)
    at async file:///app/src/app-account.js:75:36
info: POST 400 /account/login

screenshot of the browser

Image

the error sais: "an error occured: openid-setup-failed"

How can we reproduce the issue?

  1. Setup the OpenID option
  2. wait some days / weeks ? ^^
  3. try to login

Where are you hosting Actual?

Docker

What browsers are you seeing the problem on?

Other

Operating System

Linux

Originally created by @AlexT59 on GitHub (Aug 18, 2025). ### Verified issue does not already exist? - [x] I have searched and found no existing issue ### What happened? I'm unable to connect to the server using the OpenID option. I configured it two weeks ago using PocketID, and it worked correctly immediately after configuration. I havn't used it since. ### logs from the server ```log Logging in via openid Error setting up OpenID client: RPError: outgoing request timed out after 3500ms at /app/node_modules/openid-client/lib/helpers/request.js:140:13 at async Issuer.discover (/app/node_modules/openid-client/lib/issuer.js:144:22) at async setupOpenIdClient (file:///app/src/accounts/openid.js:53:11) at async loginWithOpenIdSetup (file:///app/src/accounts/openid.js:101:18) at async file:///app/src/app-account.js:75:36 info: POST 400 /account/login ``` ### screenshot of the browser <img width="630" height="514" alt="Image" src="https://github.com/user-attachments/assets/cc086b18-765a-410f-99ae-c08476e3aef3" /> the error sais: "an error occured: openid-setup-failed" ### How can we reproduce the issue? 1. Setup the OpenID option 2. wait some days / weeks ? ^^ 3. try to login ### Where are you hosting Actual? Docker ### What browsers are you seeing the problem on? Other ### Operating System Linux
GiteaMirror added the bug label 2026-02-28 20:12:54 -06:00
GiteaMirror commented 2026-02-28 20:12:55 -06:00
Author
Owner
Copy Link

@youngcw commented on GitHub (Aug 18, 2025):

Please reach out on discord for tech support.

@youngcw commented on GitHub (Aug 18, 2025): Please reach out on discord for tech support.
GiteaMirror commented 2026-02-28 20:12:55 -06:00
Author
Owner
Copy Link

@AlexT59 commented on GitHub (Aug 18, 2025):

For those who have the same problem, here is the link to the Discord post: https://discord.com/channels/937901803608096828/1407022418534338641

@AlexT59 commented on GitHub (Aug 18, 2025): For those who have the same problem, here is the link to the Discord post: https://discord.com/channels/937901803608096828/1407022418534338641
GiteaMirror commented 2026-02-28 20:12:55 -06:00
Author
Owner
Copy Link

@dylarm commented on GitHub (Nov 28, 2025):

For anyone else who runs into this and can't consult Discord for the solution:

After investigation it occurs just after the container reboot
Ok, when configuring it with the environnement variables it works good, even after the restart

@dylarm commented on GitHub (Nov 28, 2025): For anyone else who runs into this and can't consult Discord for the solution: > After investigation it occurs just after the container reboot > Ok, when configuring it with the environnement variables it works good, even after the restart
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#2401
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?