Self-Hosting: CHARM_HOST Env uses port 35353 instead of 443?

[azoller1]

Hello, I have charm running in a docker container with charm.mydomain.net reverse proxied to the http port 35353 from the container with caddy.

Everything looks good with the container/host. Also have CHARM_SERVER_PUBLIC_URL=charm.mydomain.net set.

So, when using skate on a different host with CHARM_HOST=https://charm.mydomain.net, it seems to be using 35353 instead of 443, which I would assume it would use by default?

$ skate list
Error: authentication failed: dial tcp: address https://charm.mydomain.net:35353: too many colons in address

Is there possibly a PORT env I am missing? Also, I am assuming skate uses http and not ssh correct?

[bashbunni]

Hey @azoller1 I think you're looking for the CHARM_SERVER_SSH_PORT. You can see all the env variables for Charm in this section of the readme. Skate uses SSH by default, not HTTP. The auth is done with SSH keys, so we generally use SSH > HTTP.

Hope that helps!!

[richard-kramer]

I don't think, that answers the question, does it?

The CHARM_SERVER_SSH_PORT variable ist a server setting, but the problem ist pointing the client to another port than 35353. For example, when running skate behind a reverse proxy, which accepts https connections on 443.

The mentioned setting simply tells the server (potentially inside the docker container) to listen on another port for ssh connections, which doesn't affect the client at all.

Can we please reopen this? Or are there some hidden settings, that already exist?

[richard-kramer]

It seems like additionally setting CHARM_HTTP_PORT to 443 does the trick.

It now works for me behind a http reverse proxy which handles TLS and this in my .zshrcfile:

export CHARM_HOST="charm.my_domain.tld"
export CHARM_HTTP_PORT="443"

Unfortunately, this is not explained in the docs. I only found it by looking at the client sourcecode.

[bashbunni]

Ah @richard-kramer gotcha, thank you for clarifying the issue! I assumed it was asking something different. I'll add a section to our docs to reflect the changes you can make on the client side to help in cases like this.