Helium-7

yeah so i just had this too, been unsuccessfully trying to fix it for days now got it running on a barebones arch install ~~because i like to torture myself~~...

> yeah so i just had this too, been unsuccessfully trying to fix it for days now got it running on a barebones arch install ~because i like to torture...

> You need to wrap the hosts into an array. E.g. > > ``` > GOTIFY_SERVER_SSL_LETSENCRYPT_HOSTS: '[gotify.url.xyz]' > ``` ok, that fixed that, but now if i try to open...

> Hi, can you share some more details about your setup? (Where does the port 32768 and 42768 wire to?) > > My intuitive understanding of what went wrong is...

it works fine without SSL, even if i turn SSL on and explicitly open it via http://, just not https

from the server it gives me: `curl: (35) OpenSSL/3.0.17: error:0A000438:SSL routines::tlsv1 alert internal error` from a different computer it shows `curl: (52) Empty reply from server`

I'm considering it.. but here's the output of that: ``` [ { "Id": "7a8aa7ff25462f015494ac1cea9d5d7c4ea9d1fab14915d253b9f96e19d42036", "Created": "2025-09-15T11:19:20.51161539Z", "Path": "./gotify-app", "Args": [], "State": { "Status": "running", "Running": true, "Paused": false, "Restarting": false,...

1. the directory is in the container, invisible to me afaik 2. yeah, it always starts with ``` Started listening for plain connection on tcp [::]:80 Started listening for TLS...

> I tried the workflow on my end, it seems like if you visit the port 443 from the public URL, `docker logs gotify should tell you the error`? >...

> Okay I am pretty sure I know the this error, this is your SNI not matching. > > > If I send curl --insecure -H "Host: gotify.example.com" https://localhost from...