[GH-ISSUE #4687] [Bug]: ERR_CONNECTION_REFUSED / ERR_SSL_PROTOCOL_ERROR since #4049 #43644

Closed
opened 2026-04-26 04:16:09 -05:00 by GiteaMirror · 4 comments
Owner

Originally created by @mauroartizzu on GitHub (Mar 25, 2025).
Original GitHub issue: https://github.com/actualbudget/actual/issues/4687

Verified issue does not already exist?

  • I have searched and found no existing issue

What happened?

If i switch to edge tag in my docker-compose.yaml file I can not access the server

Image

Certificates are valid and work fine in latest

services:
  actual:
    image: docker.io/actualbudget/actual-server:latest
    # image: docker.io/actualbudget/actual-server:edge
    ports:
      - '5006:5006'
    environment:
      - ACTUAL_HTTPS_KEY=/certs/myhost.key
      - ACTUAL_HTTPS_CERT=/certs/myhost.crt
      - ACTUAL_PORT=5006
      - ACTUAL_UPLOAD_FILE_SYNC_SIZE_LIMIT_MB=20
      - ACTUAL_UPLOAD_SYNC_ENCRYPTED_FILE_SYNC_SIZE_LIMIT_MB=50
      - ACTUAL_UPLOAD_FILE_SIZE_LIMIT_MB=20

    volumes:
      - actual_data:/data
      - /var/run/docker.sock:/var/run/docker.sock
      - /share/CACHEDEV1_DATA/.qpkg/Tailscale:/certs
    restart: unless-stopped

volumes:
  actual_data:

How can we reproduce the issue?

switch from latest to edge in a dockerized environment

Where are you hosting Actual?

Docker

What browsers are you seeing the problem on?

Other

Operating System

Other

Originally created by @mauroartizzu on GitHub (Mar 25, 2025). Original GitHub issue: https://github.com/actualbudget/actual/issues/4687 ### Verified issue does not already exist? - [x] I have searched and found no existing issue ### What happened? If i switch to edge tag in my docker-compose.yaml file I can not access the server ![Image](https://github.com/user-attachments/assets/2c38d788-b8ce-4696-8b2f-e14491bf6b75) Certificates are valid and work fine in latest ``` services: actual: image: docker.io/actualbudget/actual-server:latest # image: docker.io/actualbudget/actual-server:edge ports: - '5006:5006' environment: - ACTUAL_HTTPS_KEY=/certs/myhost.key - ACTUAL_HTTPS_CERT=/certs/myhost.crt - ACTUAL_PORT=5006 - ACTUAL_UPLOAD_FILE_SYNC_SIZE_LIMIT_MB=20 - ACTUAL_UPLOAD_SYNC_ENCRYPTED_FILE_SYNC_SIZE_LIMIT_MB=50 - ACTUAL_UPLOAD_FILE_SIZE_LIMIT_MB=20 volumes: - actual_data:/data - /var/run/docker.sock:/var/run/docker.sock - /share/CACHEDEV1_DATA/.qpkg/Tailscale:/certs restart: unless-stopped volumes: actual_data: ``` ### How can we reproduce the issue? switch from latest to edge in a dockerized environment ### Where are you hosting Actual? Docker ### What browsers are you seeing the problem on? Other ### Operating System Other
GiteaMirror added the bug label 2026-04-26 04:16:09 -05:00
Author
Owner

@mauroartizzu commented on GitHub (Mar 25, 2025):

the last working tag is:
docker.io/actualbudget/actual-server:sha-c17cd28-alpine c17cd28

from this tag on it gives me ERR_CONNECTION_REFUSED
docker.io/actualbudget/actual-server:sha-d5e2030-alpine d5e2030

Image

The edge tag gives instead ERR_SSL_PROTOCOL_ERROR i don't know yet since what tag. Still investigating but this requires be to test all the tags up to the edge. The problem seems to start from d5e2030

<!-- gh-comment-id:2752123716 --> @mauroartizzu commented on GitHub (Mar 25, 2025): the last working tag is: `docker.io/actualbudget/actual-server:sha-c17cd28-alpine` **c17cd28** from this tag on it gives me **ERR_CONNECTION_REFUSED** `docker.io/actualbudget/actual-server:sha-d5e2030-alpine` **d5e2030** ![Image](https://github.com/user-attachments/assets/025eaad3-36f6-4b1b-ad97-0bb40365b155) The edge tag gives instead **ERR_SSL_PROTOCOL_ERROR** i don't know yet since what tag. Still investigating but this requires be to test all the tags up to the edge. The problem seems to start from **d5e2030**
Author
Owner

@mauroartizzu commented on GitHub (Mar 25, 2025):

It might be CORS related?

Image

<!-- gh-comment-id:2752174536 --> @mauroartizzu commented on GitHub (Mar 25, 2025): It might be CORS related? ![Image](https://github.com/user-attachments/assets/b556c1a0-ff88-449d-950d-89b910f52da3)
Author
Owner

@lelemm commented on GitHub (Mar 25, 2025):

Thank you for your report. I was able to pinpoint the issue and fixed. Tomorrow will be available on the edge image.
Would be nice if you could give us a feedback if the issue was solved on your side

<!-- gh-comment-id:2752569572 --> @lelemm commented on GitHub (Mar 25, 2025): Thank you for your report. I was able to pinpoint the issue and fixed. Tomorrow will be available on the edge image. Would be nice if you could give us a feedback if the issue was solved on your side
Author
Owner

@mauroartizzu commented on GitHub (Mar 26, 2025):

Thank you for your report. I was able to pinpoint the issue and fixed. Tomorrow will be available on the edge image. Would be nice if you could give us a feedback if the issue was solved on your side

It is solved, thanks!

<!-- gh-comment-id:2754197809 --> @mauroartizzu commented on GitHub (Mar 26, 2025): > Thank you for your report. I was able to pinpoint the issue and fixed. Tomorrow will be available on the edge image. Would be nice if you could give us a feedback if the issue was solved on your side It is solved, thanks!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/actual#43644