github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-05-06 07:01:45 -05:00
Code Issues 1.5k Packages Projects Releases 54 Wiki Activity

[Bug]: Docker Health Check fails in combination with Tailscale #2379

New Issue
Closed
opened 2026-02-28 20:12:19 -06:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-02-28 20:12:19 -06:00
Owner
Copy Link

Originally created by @diktomat on GitHub (Aug 11, 2025).

Verified issue does not already exist?

  • I have searched and found no existing issue

What happened?

When using Actual inside Docker, and using Tailscale to get access, either the Docker healthcheck or the listening will fail.

How can we reproduce the issue?

docker-compose.yml:

services:
  actual_server:
    image: docker.io/actualbudget/actual-server:latest-alpine
    ports:
      - '5006:5006'
    extra_hosts:
      - 'pi.tailXXXX.ts.net=::1'
    environment:
      - ACTUAL_HTTPS_KEY=/certs/pi.tailXXXX.ts.net.key
      - ACTUAL_HTTPS_CERT=/certs/pi.tailXXXX.ts.net.crt
      - ACTUAL_HOSTNAME=pi.tailXXXX.ts.net
      - ACTUAL_PORT=5006
    volumes:
      - ./actual:/data
      - ./certs:/certs
    healthcheck:
      test: ['CMD-SHELL', 'node src/scripts/health-check.js']
      interval: 60s
      timeout: 10s
      retries: 3
      start_period: 20s
    restart: unless-stopped

Like this the health check passes, but it will refuse all connections. If one removes the ACTUAL_HOSTNAME variable, it will serve flawlessly, but the healthcheck fails, as the certificate is not for localhost:

Health check failed: FetchError: request to https://localhost:5006/health failed, reason: Hostname/IP does not match certificate's altnames: Host: localhost. is not in the cert's altnames: DNS:pi.tailXXXX.ts.net at ClientRequest.<anonymous> (/app/node_modules/node-fetch/lib/index.js:1501:11) at ClientRequest.emit (node:events:517:28) at TLSSocket.socketErrorListener (node:_http_client:501:9) at TLSSocket.emit (node:events:517:28) at emitErrorNT (node:internal/streams/destroy:151:8) at emitErrorCloseNT (node:internal/streams/destroy:116:3) at process.processTicksAndRejections (node:internal/process/task_queues:82:21) { type: 'system', errno: 'ERR_TLS_CERT_ALTNAME_INVALID', code: 'ERR_TLS_CERT_ALTNAME_INVALID' }

Where are you hosting Actual?

NAS

What browsers are you seeing the problem on?

Other

Operating System

Linux

Originally created by @diktomat on GitHub (Aug 11, 2025). ### Verified issue does not already exist? - [x] I have searched and found no existing issue ### What happened? When using Actual inside Docker, and using Tailscale to get access, either the Docker healthcheck or the listening will fail. ### How can we reproduce the issue? docker-compose.yml: ```yaml services: actual_server: image: docker.io/actualbudget/actual-server:latest-alpine ports: - '5006:5006' extra_hosts: - 'pi.tailXXXX.ts.net=::1' environment: - ACTUAL_HTTPS_KEY=/certs/pi.tailXXXX.ts.net.key - ACTUAL_HTTPS_CERT=/certs/pi.tailXXXX.ts.net.crt - ACTUAL_HOSTNAME=pi.tailXXXX.ts.net - ACTUAL_PORT=5006 volumes: - ./actual:/data - ./certs:/certs healthcheck: test: ['CMD-SHELL', 'node src/scripts/health-check.js'] interval: 60s timeout: 10s retries: 3 start_period: 20s restart: unless-stopped ``` Like this the health check passes, but it will refuse all connections. If one removes the `ACTUAL_HOSTNAME` variable, it will serve flawlessly, but the healthcheck fails, as the certificate is not for localhost: ``` Health check failed: FetchError: request to https://localhost:5006/health failed, reason: Hostname/IP does not match certificate's altnames: Host: localhost. is not in the cert's altnames: DNS:pi.tailXXXX.ts.net at ClientRequest.<anonymous> (/app/node_modules/node-fetch/lib/index.js:1501:11) at ClientRequest.emit (node:events:517:28) at TLSSocket.socketErrorListener (node:_http_client:501:9) at TLSSocket.emit (node:events:517:28) at emitErrorNT (node:internal/streams/destroy:151:8) at emitErrorCloseNT (node:internal/streams/destroy:116:3) at process.processTicksAndRejections (node:internal/process/task_queues:82:21) { type: 'system', errno: 'ERR_TLS_CERT_ALTNAME_INVALID', code: 'ERR_TLS_CERT_ALTNAME_INVALID' } ``` ### Where are you hosting Actual? NAS ### What browsers are you seeing the problem on? Other ### Operating System Linux
GiteaMirror commented 2026-02-28 20:12:20 -06:00
Author
Owner
Copy Link

@MatissJanis commented on GitHub (Aug 11, 2025):

👋 Hi!
Please use the community discord for tech support. Tailscale is not an officially supported solution for Actual, but I'm sure someone on the community Discord is using it too and will be able to assist.

We use github issues only for feature requests and bug reports. Since this is neither - closing.

@MatissJanis commented on GitHub (Aug 11, 2025): 👋 Hi! Please use the community discord for tech support. Tailscale is not an officially supported solution for Actual, but I'm sure someone on the community Discord is using it too and will be able to assist. We use github issues only for feature requests and bug reports. Since this is neither - closing.
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
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#2379
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?