Ben Lambert
Ben Lambert
I think that there's a little issue that we don't have the migration code for future releases, so we can't rollback on older versions in step 5. I think that...
@mtlewis to confirm that things still work 🤞
I'm thinking that this error message might be helpful: ``` "code":"ERR_TLS_CERT_ALTNAME_INVALID","host":"localhost","reason":"Host: localhost. is not in the cert's altnames: DNS:acibackstage.westeurope.azurecontainer.io"}, ``` Looks like you're trying to hit it through localhost? Or...
You shouldn't have to change the `/etc/hosts` file. If you're running locally, then the `app-config.yaml` `backend.baseUrl` and `app.baseUrl` should be set to `localhost`, you can take advantage of doing this...
Do you have to do SSL termination in the node process, you're going to need to add localhost to the alt names for local development in that case as internal...
Ah right OK, yeah it's a little tricky to do if you're not going to add the alt names to the certificate for communication with localhost, and the way that...
@drodil we normally stop supporting it when there's another version promoted to LTS in it's place. > Node.js 22 will enter long-term support (LTS) in October So when 22 goes...
@freben thoughts on pausing this for a few months until we drop 18:?
Fixed by #26245