[Bug]: Stuck on &#34;Initializing the connection to the local database...&#34; Fresh Docker install #1155

@newtonfav commented on GitHub (Jun 27, 2024):

I'm having same issue, stuck at "Initializing the connection to the local database..." I'm running the repo on my PC locally. should i open a new issue for this @youngcw

@newtonfav commented on GitHub (Jun 27, 2024): I'm having same issue, stuck at "Initializing the connection to the local database..." I'm running the repo on my PC locally. should i open a new issue for this @youngcw

GiteaMirror commented

@youngcw commented on GitHub (Jun 27, 2024):

@newtonfav Only if your issue is different than this.

@youngcw commented on GitHub (Jun 27, 2024): @newtonfav Only if your issue is different than this.

GiteaMirror commented

@newtonfav commented on GitHub (Jun 27, 2024):

@newtonfav Only if your issue is different than this.

same, just that I'm not running on docker

@newtonfav commented on GitHub (Jun 27, 2024): > @newtonfav Only if your issue is different than this. same, just that I'm not running on docker

GiteaMirror commented

@youngcw commented on GitHub (Jun 27, 2024):

@davemcmath If you are on anything apple make sure you are using https, and probably a non self-signed cert. Apple browsers are really picky about certs, and Actual doesn't work properly without https.

@youngcw commented on GitHub (Jun 27, 2024): @davemcmath If you are on anything apple make sure you are using https, and probably a non self-signed cert. Apple browsers are really picky about certs, and Actual doesn't work properly without https.

GiteaMirror commented

@newtonfav commented on GitHub (Jun 28, 2024):

Is there a guide on how i can run using https instead of http on local server?

@newtonfav commented on GitHub (Jun 28, 2024): Is there a guide on how i can run using https instead of http on local server?

GiteaMirror commented

@nyakojiru commented on GitHub (Oct 7, 2024):

I'm on the same train. Can't use it on iOS with http. There should be optional parameters to be able to use Actual with http in development mode. I don't want to expose the service to the internet .

@nyakojiru commented on GitHub (Oct 7, 2024): I'm on the same train. Can't use it on iOS with http. There should be optional parameters to be able to use Actual with http in development mode. I don't want to expose the service to the internet .

GiteaMirror commented

@hrv231 commented on GitHub (Oct 15, 2024):

I'm having the same problem, running on docker, behind traefik proxy, with HTTPS.
I'm using it with a purchased domain and let's encrypt certificate.

I generally use Firefox, so when I open the link that takes me to Actual, at first shows the Initializing the connection to the local database... , then I refresh the page and quickly it takes me to the enter your password.

I believe there is a bug for sure.

Edit: added more details

@hrv231 commented on GitHub (Oct 15, 2024): I'm having the same problem, running on docker, behind traefik proxy, with HTTPS. I'm using it with a purchased domain and let's encrypt certificate. I generally use Firefox, so when I open the link that takes me to Actual, at first shows the _Initializing the connection to the local database..._ , then I refresh the page and quickly it takes me to the enter your password. I believe there is a bug for sure. Edit: added more details

GiteaMirror commented

2026-02-28 19:34:01 -06:00

@tibuski commented on GitHub (Feb 12, 2025):

I wanted to give actual budget a try but I am facing the same issue on a fresh docker start ...

@tibuski commented on GitHub (Feb 12, 2025): I wanted to give actual budget a try but I am facing the same issue on a fresh docker start ...

GiteaMirror commented

@Ralle001 commented on GitHub (Feb 12, 2025):

As I can see there is no changes.

Logs:
Checking if there are any migrations to run for direction "up"...
Migrations: DONE
Listening on :::5006...

Tried: Opera, Chrome, Edge

config.json:
{}

Still stuck on: "Initializing the connection to the local database…"

@Ralle001 commented on GitHub (Feb 12, 2025): As I can see there is no changes. Logs: `Checking if there are any migrations to run for direction "up"...` `Migrations: DONE` `Listening on :::5006...` Tried: Opera, Chrome, Edge config.json: `{}` Still stuck on: "Initializing the connection to the local database…"

GiteaMirror commented

2026-02-28 19:34:01 -06:00

@tibuski commented on GitHub (Feb 12, 2025):

FYI, I made it work by using https. It seems it's required.

@tibuski commented on GitHub (Feb 12, 2025): FYI, I made it work by using https. It seems it's required.

GiteaMirror commented

2026-02-28 19:34:01 -06:00

@bo0tzz commented on GitHub (Feb 12, 2025):

I suspect this issue is caused by the uBlock extension: https://github.com/uBlockOrigin/uBlock-issues/issues/3527

@bo0tzz commented on GitHub (Feb 12, 2025): I suspect this issue is caused by the uBlock extension: https://github.com/uBlockOrigin/uBlock-issues/issues/3527

GiteaMirror commented

@tibuski commented on GitHub (Feb 12, 2025):

Just did a test disabling ublock and in private mode but got the same issue.

@tibuski commented on GitHub (Feb 12, 2025): Just did a test disabling ublock and in private mode but got the same issue.

GiteaMirror commented

@bo0tzz commented on GitHub (Feb 12, 2025):

In my case it happens if uBlock is installed at all, the disable button in the extension seems to make no difference.

@bo0tzz commented on GitHub (Feb 12, 2025): In my case it happens if uBlock is installed at all, the disable button in the extension seems to make no difference.

GiteaMirror commented

@MikesGlitch commented on GitHub (Feb 13, 2025):

This should fix it: https://github.com/actualbudget/actual/pull/4375

@MikesGlitch commented on GitHub (Feb 13, 2025): This should fix it: https://github.com/actualbudget/actual/pull/4375

GiteaMirror commented

2026-02-28 19:34:03 -06:00

@fdfytr commented on GitHub (Feb 15, 2025):

This should fix it: #4375

It does not
Same error on Firefox linux
Tried to clean cache, redownloading latest image without resolving

@fdfytr commented on GitHub (Feb 15, 2025): > This should fix it: [#4375](https://github.com/actualbudget/actual/pull/4375) It does not Same error on Firefox linux Tried to clean cache, redownloading latest image without resolving

GiteaMirror commented

@youngcw commented on GitHub (Feb 15, 2025):

This should fix it: #4375

It does not Same error on Firefox linux Tried to clean cache, redownloading latest image without resolving

@fdfytr you have to test out the PR or edge build. Latest won't have the fix until the next release.

@youngcw commented on GitHub (Feb 15, 2025): > > This should fix it: [#4375](https://github.com/actualbudget/actual/pull/4375) > > It does not Same error on Firefox linux Tried to clean cache, redownloading latest image without resolving @fdfytr you have to test out the PR or edge build. Latest won't have the fix until the next release.

GiteaMirror commented

@bibberp commented on GitHub (Feb 26, 2025):

I'm still having the same problem even with the edge build

services:
  actual_server:
    image: docker.io/actualbudget/actual-server:edge
    ports:

      - '5006:5006'
    volumes:
      - /opt/actual/actual-data:/data
    healthcheck:
      # Enable health check for the instance
      test: ['CMD-SHELL', 'node src/scripts/health-check.js']
      interval: 60s
      timeout: 10s
      retries: 3
      start_period: 20s
    restart: unless-stopped

@bibberp commented on GitHub (Feb 26, 2025): I'm still having the same problem even with the edge build ``` services: actual_server: image: docker.io/actualbudget/actual-server:edge ports: - '5006:5006' volumes: - /opt/actual/actual-data:/data healthcheck: # Enable health check for the instance test: ['CMD-SHELL', 'node src/scripts/health-check.js'] interval: 60s timeout: 10s retries: 3 start_period: 20s restart: unless-stopped ```

GiteaMirror commented

@MikesGlitch commented on GitHub (Feb 26, 2025):

I'm still having the same problem even with the edge build

services:
  actual_server:
    image: docker.io/actualbudget/actual-server:edge
    ports:

      - '5006:5006'
    volumes:
      - /opt/actual/actual-data:/data
    healthcheck:
      # Enable health check for the instance
      test: ['CMD-SHELL', 'node src/scripts/health-check.js']
      interval: 60s
      timeout: 10s
      retries: 3
      start_period: 20s
    restart: unless-stopped

Can you open devtools with F12/CTRL Shift I, and copy/paste the contents in here.

There's a chance you're cached on the old code - can you also try in incognito?

@MikesGlitch commented on GitHub (Feb 26, 2025): > I'm still having the same problem even with the edge build > > ``` > services: > actual_server: > image: docker.io/actualbudget/actual-server:edge > ports: > > - '5006:5006' > volumes: > - /opt/actual/actual-data:/data > healthcheck: > # Enable health check for the instance > test: ['CMD-SHELL', 'node src/scripts/health-check.js'] > interval: 60s > timeout: 10s > retries: 3 > start_period: 20s > restart: unless-stopped > ``` Can you open devtools with F12/CTRL Shift I, and copy/paste the contents in here. There's a chance you're cached on the old code - can you also try in incognito?

GiteaMirror commented

@bibberp commented on GitHub (Feb 27, 2025):

192.168.1.220/:1 The Cross-Origin-Opener-Policy header has been ignored, because the URL's origin was untrustworthy. It was defined either in the final response or a redirect. Please deliver the response using the HTTPS protocol. You can also use the 'localhost' origin instead. See https://www.w3.org/TR/powerful-features/#potentially-trustworthy-origin and https://html.spec.whatwg.org/#the-cross-origin-opener-policy-header.Understand this errorAI i18n.ts:60 Unknown locale en-US, falling back to en

same for incognito -- seems like it really wants https? I thought that it supported local http connections?

tried on MacBook with safari and win10 with chrome

@bibberp commented on GitHub (Feb 27, 2025): `192.168.1.220/:1 The Cross-Origin-Opener-Policy header has been ignored, because the URL's origin was untrustworthy. It was defined either in the final response or a redirect. Please deliver the response using the HTTPS protocol. You can also use the 'localhost' origin instead. See https://www.w3.org/TR/powerful-features/#potentially-trustworthy-origin and https://html.spec.whatwg.org/#the-cross-origin-opener-policy-header.Understand this errorAI i18n.ts:60 Unknown locale en-US, falling back to en` same for incognito -- seems like it really wants https? I thought that it supported local http connections? tried on MacBook with safari and win10 with chrome

GiteaMirror commented

@MikesGlitch commented on GitHub (Feb 27, 2025):

same for incognito -- seems like it really wants https? I thought that it supported local http connections?

It does if it comes from localhost. localhost is treated as a secure context. There's some info here: https://developer.mozilla.org/en-US/docs/Web/Security/Secure_Contexts#when_is_a_context_considered_secure

You should have seen these two messages in your console:

Backend: Attempting to connect to client
Backend: Client connected

If you didn't it suggests you're not on the latest edge version - you may want to do another docker pull.

@MikesGlitch commented on GitHub (Feb 27, 2025): > same for incognito -- seems like it really wants https? I thought that it supported local http connections? It does if it comes from localhost. localhost is treated as a secure context. There's some info here: https://developer.mozilla.org/en-US/docs/Web/Security/Secure_Contexts#when_is_a_context_considered_secure You should have seen these two messages in your console: ``` Backend: Attempting to connect to client Backend: Client connected ``` If you didn't it suggests you're not on the latest edge version - you may want to do another docker pull.

GiteaMirror commented