KC 17 installation help needed

Hello,

I’ve installed KC 17 on a fresh ubuntu 20.04 (bare metal) on a remote server with LetsEncrypt certs.
I can connect to the server on http://mydomain.org:8443
However, I can’t open the administration console. I Have enabled https, but now when I click on “Administration Console”, it will report after some time:

ERR_CONNECTION_REFUSED

My keycloak.conf looks like this:

# Basic settings for running in production. Change accordingly before deploying the server.

# Database

# The database vendor.
db=postgres

# The username of the database user.
db-username=...

# The password of the database user.
db-password=...

# The full database JDBC URL. If not provided, a default URL is set based on the selected database vendor.
db-url=jdbc:postgresql://localhost/keycloak

# Observability

# If the server should expose metrics and healthcheck endpoints.
#metrics-enabled=true

# HTTP
KC_HTTP_ENABLED=true

# The file path to a server certificate or certificate chain in PEM format.
#https-certificate-file=${kc.home.dir}conf/server.crt.pem
https-certificate-file=/etc/letsencrypt/live/keycloak.zeisberg.org/fullchain.pem

# The file path to a private key in PEM format.
#https-certificate-key-file=${kc.home.dir}conf/server.key.pem
https-certificate-key-file=/etc/letsencrypt/live/<domain>/privkey.pem

# The proxy address forwarding mode if the server is behind a reverse proxy.
#proxy=reencrypt

# Do not attach route to cookies and rely on the session affinity capabilities from reverse proxy
#spi-sticky-session-encoder-infinispan-should-attach-route=false

# Hostname for the Keycloak server.
hostname=<domain>

What does it take to get into the admin console?
Thank you for your help!
BR
Sven

Hi,
Do you have any logging set up?
I had a problem w/Camunda on AKS where Camunda was listening on port 8080 but the cluster was HTTPS only. In the Tomcat log I could see that the connection was refused because the endpoint (at 8443) did not exist.