Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: Servers - Cloudflared Tunnel #2194

Open
luckycreationsindia opened this issue May 13, 2024 · 3 comments
Open

[Bug]: Servers - Cloudflared Tunnel #2194

luckycreationsindia opened this issue May 13, 2024 · 3 comments
Assignees

Comments

@luckycreationsindia
Copy link

Description

Hi,

I'm trying to implement cloudflared tunnel ssh. I did followed the steps provided in documentation but failed.

Anyone got success in this?

My server details:
Ubuntu 23
UFW Firewall used (Able to access if I use host.docker.internal but not via cloudflared tunnel)

Just in case, i've also added cloudflare ip addresses to whitelist.
IP Subnet 172.x.x.x, 127.x.x.x are all whitelisted.

Minimal Reproduction (if possible, example repository)

  1. Create new tunnel in cloudflare
  2. Host added - localhost:22 with SSH selected
  3. Point that host to subdomain (tunnel.example.com)
  4. Create new server in coolify
  5. Give IP address as localhost
  6. Set cloudflare Tunnel token and ssh host (localhost:22)
  7. Click on Automated Configuration

Exception or Error

ssh: connect to host localhost port 22: Connection refused

Version

v4.0.0-beta.277

@luckycreationsindia
Copy link
Author

Update:

I tried to install cloudflared tunnel within server. It was suucessful and the service is running but when I select "I have already set up the tunnel manually on the server." the following error shows when validating server.

Error: kex_exchange_identification: Connection closed by remote host

@andrasbacsai
Copy link
Member

localhost refers to the server where Coolify is running and should not be accessible through CF. This doesn't seem logical. Why would you want to use it in that way?

If you use host.docker.internal, it will stay within your server as it is an internal IP/network.

@luckycreationsindia
Copy link
Author

I'm trying to add 2nd server which should be accessible from tunnel instead of direct access. I don't want to expose 2nd server's SSH port.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants