alexomc

sure: ``` captain-captain.1.sasqli1w0jip@ams-sm5038mr-h8trf-4-3 | Captain Starting ... captain-captain.1.sasqli1w0jip@ams-sm5038mr-h8trf-4-3 | Overriding skipVerifyingDomains from /captain/data/config-override.json captain-captain.1.sasqli1w0jip@ams-sm5038mr-h8trf-4-3 | September 21st 2023, 6:34:12.351 pm captain-captain.1.sasqli1w0jip@ams-sm5038mr-h8trf-4-3 | Error: Salt is not set! Cannot create authenticator...

I think the log are returning only the logs since the last restart... and since Caprover restarts each time a new app is created you won't see anything here.

got it, here's what happens when an app is created and Caprover restarts: ``` captain-captain.1.sasqli1w0jip@ams-sm5038mr-h8trf-4-3 | September 21st 2023, 7:03:05.026 pm Registering app started: jferacwunx captain-captain.1.sasqli1w0jip@ams-sm5038mr-h8trf-4-3 | September 21st 2023,...

note that the exact same API command works fine with older version of Caprover

Yes, that's weird, just creating a blank app (basically just entering the name of a new app inside the UI) triggers a restart: ``` captain-captain.1.tz8lukhrgdxv@ams-sm5038mr-h8trf-4-3 | September 21st 2023, 7:29:27.189...

doesn't seem to be a common issue or Github would be flooded, do you think reinstalling Caprover might fix it?

1.10.1 version works perfectly btw

I disabled the default push and that fixed the issue, thanks a lot! I'm available if you need to do more tests, install it to another server to see if...