Unable to connect to server behind ssh tunnel via public hostname

[user16986]

What is the issue you’re encountering

ssh tunnel public hostname does not resolve to internal IP

What are the steps to reproduce the issue?

I am able to connect to the server behind cloudflared tunnel via its assigned private IP with warp or using the public hostname if using cloudflared as a client and the legacy method by using ProxyCommand in ssh config. However with warp enabled, I am not able to ssh to the server using the public hostname. Do I need to add a local DNS entry to have the public hostname resolve to the internal IP of the ssh tunnel?

[fritex]

@user16986

However with warp enabled, I am not able to ssh to the server using the public hostname.

Do you get some default WAF block page error, or rather it doesn’t load, is it white page, or even your Access Policy not allowing you to access it?

Have you considered using Browser-rendering for SSH or a different method (4 in total):

Connect to SSH in the browser · Cloudflare Zero Trust docs

SSH · Cloudflare Zero Trust docs

Or even the newest one here:

SSH with Access for Infrastructure (recommended) · Cloudflare Zero Trust docs

[fritex]

@user16986

ProxyCommand

Below might help to cross-check with your configuration as well:

Clouflare does not forward ssh to locally managed cloudflare tunnel

Let’s say you want to use the tunnel for ssh.example.com: Create a proxied CNAME record with name ssh and the tunnel as the value (xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx.cfargotunnel.com). Then, your ssh config as follows: Host ssh.example.com User myuser IdentityFile /path/to/key ProxyCommand /usr/local/bin/cloudflared access ssh --hostname %h