Sven Tennie

@ramesh8830 The `Access-Control-Allow-Origin` header is set by `nginz` (and `cannon`'s `nginx` in some special cases.) Could you please check these Values: - `nginz.nginx_conf.allowlisted_origins` - `nginz.nginx_conf.nginx_conf.external_env_domain`

@ramesh8830 You should have some yaml file or files where you put all config values. The dots (`.`) refer to nodes in this yaml file. E.g. [Link to `nginz.nginx_conf.nginx_conf.external_env_domain`](https://github.com/wireapp/wire-server-deploy/blob/master/values/wire-server/demo-values.example.yaml#L156) if...

Ah, sorry, it's a list in yaml. E.g. ```yaml nginz: replicaCount: 3 config: ws: useProxyProtocol: false # images: # nginz: # tag: some-tag (only override if you want a newer/different...

@ramesh8830 Welcome :smile: BTW, there are more web application you may want to use (e.g. `account-pages`.) If you run into the same issue with one of them, you'll have to...

According to @julialongtin this is only a change in the label.

> Request URL: https://nginz-https.example.com/v3/properties/webapp Request Method: GET Status Code: 404 > > Websocket connections are failing. Hey @mfarhanmail :wave: `*.example.com` looks like a default value that surely does not fit...

Ah, I see. You may get away with fake domains as long as you stay consistent. However, this is not officially supported. And, you may need to solve HTTPS/SSL certificate...

Hey @bentby , Have you tried to add the `--debug` option to your Helm commands to spot where in the Helm charts this happens?

Hey @cydparser , Could you please explain a bit which issue you're solving (error messages, etc.)?

IMHO linting and consistent formatting are always good! :+1: