Cannot finish "Setup Sentry" when `mail.use-ssl` was set in the config

[schettn]

Self-Hosted Version

24.6.0

CPU Architecture

x86_64

Docker Version

25.0.0

Docker Compose Version

2.25.0

Steps to Reproduce

1. Setup a fresh sentry
2. Configure mail inside sentry/config.yml (especially mail.use-ssl):
3. Visit "Welcome to Sentry"
4. Click Continue
5. See that nothing happens and look at the error

Expected Result

The Continue button should work.

Actual Result

URL: https://sentry.cronit.io/api/0/internal/options/?query=is:required Status: 400 Bad Request Source: Network Initiator: fetch.js:54

{
    "error": "immutable_option",
    "errorDetail": {
        "option": "mail.use-ssl",
        "message": "'mail.use-ssl' cannot be changed at runtime because it is configured on disk"
    }
}

Event ID

No response

[hubertdeng123]

Looks like a duplicate of https://github.com/getsentry/self-hosted/issues/3139. I'm going to backlog this for now until we have a chance to investigate

[schettn]

The workaround is to comment out mail.use-ssl in sentry/config.yml.

[zentavr]

@schettn Removed that mail.use-ssl from /etc/sentry/config.yml, restarted the pod and the issue is still there :(

[schettn]

mail.use-ssl' cannot be changed at runtime because it is configured on disk

Do you have the same error after removing it?

Maybe you have to reinstall

[zentavr]

@schettn I’d removed the whole setup seems like 4 times. So that did not help.

[schettn]

I am not familiar to your setup but is /etc/sentry/config.yml correct?

When /etc/sentry is the cloned https://github.com/getsentry/self-hosted.. shouldn't the config path be /etc/sentry/sentry/config.yml?

[IanWoodard]

Thanks @vanya2143, going to backlog this again, but feel free to use this as a short-term solution!

[tiwj]

Can confirm your solution @vanya2143 . Simply did it directly from the browser (Edge).

1. Open Developer Console F12
2. Open Network tab
3. Repeat failing request
4. Select request from the list
5. Right Click "Edit and send..."
6. Remove "mail.use-ssl":false from body
7. Resend > 200
8. Reload page

[cconrad]

I can confirm that this still exists in 24.10.0. After commenting the "mail.use-ssl" line and rerunning install.sh I was able to continue.

[aldy505]

Documented this here: https://github.com/getsentry/self-hosted/pull/3368

Going to close this issue.