Can't login to console after changing HOST URL

[silentmado]

I edited the console docker yml file to correspond to my host URL (./docker/console/env/config.yaml) :
host_url: https://whateveraddress.com

The console opens with no problem bbut when clicking on Login button nothing happens

I can see this log in the browser :

Logger.js:37 login: Logging in as admin
Logger.js:37 LoginApi: login admin: Logging in
Logger.js:37 RestApi: POST /api/v3/auth/login sending request
Logger.js:37 RestApi: POST /api/v3/auth/login succeeded with 200: OK
Logger.js:37 LoginApi: login admin: Success
Logger.js:37 RestApi: GET /api/v3/users/info?preventCache=1741915936073 sending request
Logger.js:37 RestApi: GET /api/v3/users/info?preventCache=1741915936073 succeeded with 202: Accepted
Logger.js:37 RestApi: GET /api/v3/authscheme sending request
Logger.js:37 RestApi: GET /api/v3/authscheme succeeded with 200: OK
Logger.js:37 RestApi: GET /api/v3/settings sending request
Logger.js:37 RestApi: GET /api/v3/settings succeeded with 200: OK
Logger.js:37 App: Current debug level: 2
Logger.js:37 RestApi: GET /deployer/api/v3/instance/$iid sending request
RestApi.js:95
GET https://whateveraddress.com/deployer/api/v3/instance/$iid 503 (Service Unavailable)
Logger.js:37 RestApi: GET /deployer/api/v3/instance/$iid failed with 503: Service Unavailable
Logger.js:37 RestApi: GET /deployer/api/v3/instance/$iid response: {
"statusCode": 503,
"error": "api is not available",
"msg": "this api is not available to Console's without the "deployer" counterpart"
}
Logger.js:37 RestApi: GET /deployer/api/v3/instance/$iid Formatted RestApi error into: REQUEST_ERROR_IN_RESPONSE: GET /deployer/api/v3/instance/$iid failed with 503: Service Unavailable
Logger.js:37 RestApi: GET /deployer/api/v3/instance/$iid old-style Translating error back to old-style throws: REQUEST_ERROR_IN_RESPONSE: GET /deployer/api/v3/instance/$iid failed with 503: Service Unavailable

PS: I used an nginx reverse proxy with SSL and redirected it to http://localhost:3000

[TsvetanG]

@silentmado
The deployer is a separate container that integrates with K8S fabric operator controller. You get that deployer error because it is not available for docker-based deployments as it is specifically designed to work only in k8s environment.

The error should not prevent you from logging in. There should be some other reason.

By looking at the log I can say the login was successful. It might be because of the SSL certificate you are using. You may check if the cert has the proper host inside that matches the host name of the console. If you run it locally just use HTTP instead of https. Of course, if you run it on the cloud you need to properly set up your hostname and issue a tls cert from one of the trusted CAs like letsencrypt (or your own if you already operate one in your private network).