[Bug]: ERR_CONNECTION_REFUSED / ERR_SSL_PROTOCOL_ERROR since #4049

[mauroartizzu]

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

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

[mauroartizzu]

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

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

[mauroartizzu]

It might be CORS related?

[lelemm]

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