🐛 [Tailscale] "This site can’t be reached" when installing Tailscale after installing Cloudflare tunnel

[jasonpearce]

Store Application

Tailscale

App version

v1.61.11

Description

If Tailscale is installed after Cloudflared, user is unable to access http://192.168.xxx.xxx:8093/ or https://192.168.xxx.xxx:8093/. Browser reports:

This site can’t be reached
192.168.xxx.xxx refused to connect
ERR_CONNECTION_REFUSED

Steps to reproduce

1. Install Ubuntu
2. Install Tipi v3.1.0
3. Install Cloudflared v2024.2.1
4. Install Hello World
5. Validate Hello World works via http://192.168.xxx.xxx:8000/ (it does)
6. Validate Hello World works via https://helloworld.example.com (it does)
7. Install Tailscale
8. Validate Tailscale works via http://192.168.xxx.xxx:8093/ or https://192.168.xxx.xxx:8093/ (it does not)

App logs

Provide instructions on how to provide logs and I'll try.

Browser

Firefox and Brave

Browser logs

No response

User-Config changes

No response

Other

I have other apps that don't work if I install them after Cloudflared is installed. Some other apps, however, do work after Cloudflared is installed. I'll create separate tickets for each.

Please confirm the following

• I believe this issue is a bug that affects all users of RunTipi, not something specific to my installation.
• I have already searched for relevant existing issues and discussions before opening this report.
• I have updated the title field above with a concise description.

[jasonpearce]

Problem remains with Tailscale v1.62.0.

[steveiliop56]

Hello @jasonpearce

Sorry for late reply. I can reproduce the issue, will fix asap since this is a major app. Probably an update in >1 hour.

[steveiliop56]

Alright after testing again seems that the app works on my seconds tipi testing machine. Are you using wsl? Because there seems to be an issue with that.

[jasonpearce]

On both my physical production and my test VM, I am using Ubuntu 22.04.4 LTS. I'm sorry that I don't know what the WSL acronym represents. On both machines, their only purpose is to run Tipi.

[steveiliop56]

No worries wsl is windows subsystem for Linux I couldn't access the tailscale ui from it but I think that was my issue. Can you share the output of docker logs tailscale

[JigSawFr]

Don't use cloudflare tunnels on my side, @jasonpearce why not using Funnels ? As it's the tunneling function of Tailscale :)

[steveiliop56]

Oh wait sorry I didn't see the cloudflare part. Are you sure you configured it correctly?

[jasonpearce]

I configured it the same way that I reported with a lot of screen shots within this ticket:

• 🐛 [Kasm] 400 Bad Request when exposing via RunTipi.io using Cloudflare tunnel #2394

I did it twice, once on my production physical server. And again on a virtual server.

In both cases, I first installed Hello World and configured it to work via a Cloudflare tunnel before attempting to recreate the problem with Tailscale.

I'm not certain I did it correctly, but I think it is likely. Would you like detailed screen shots similar to what I provide in issue 2394?

[jasonpearce]

Don't use cloudflare tunnels on my side, @jasonpearce why not using Funnels ? As it's the tunneling function of Tailscale :)

I haven't looked at Funnels yet. But thank you. I will. (Edit: I assume you are referring to https://tailscale.com/kb/1223/funnel).

I'd prefer to use Tailscale since I already have 10 to 15 other devices within that network.

[jasonpearce]

After upgrading to...

• RunTipi v3.1.3
• Cloudflared v2024.3.0
• Tailscale v1.62.1

My results are unchanged:

• Hello World still works by local IP address and Cloudflare Tunnel
• http://local-ip:8093 is Unable to Connect
• https://local-ip:8093 is Unable to Connect

The Firefox error is a little different, but that could be a result of an upgrade version of Firefox.

Unable to connect
An error occurred during a connection to 192.168.xxx.xxx:8093.

The site could be temporarily unavailable or too busy. Try again in a few moments.
If you are unable to load any pages, check your computer’s network connection.
If your computer or network is protected by a firewall or proxy, make sure that Firefox is permitted to access the web

[steveiliop56]

A small question here. Do you want to use cloudflare just to point your domain to the tailscale ui local only so you can access it from tailscale.mydomain.com? Or do you want to expose the ui to the internet? These two are completely different from each other and the second I highly advise not to do.

[jasonpearce]

I want to have Tailscale on my phone and on my RunTipi server so that I may remotely access the server's RunTipi dashboard through a VPN tunnel.

First, I'd like to just have a local IP-based interface to Tailscale, which does not appear to work if RunTipi also has Cloudflared installed on it.

In summary, I'm using Cloudflared to remotely access other apps installed on the RunTipi server. I don't intend to use Cloudflared to remotely access Tailscale with my own internet-facing subdomain (e.g. tailscale.example.com). I simply want to be able to install and use Tailscale locally on the same RunTipi server that also has Cloudflared installed and working for other apps.

I hope that helps clarify my use case. Thank you for your assistance.

[steveiliop56]

Cloudflare tunnel is the wrong approach here. If you just want to access tailscale inside your home network then cloudflare tunnel is not the solution. The solution would be to use tipi's reverse proxy or simply dns. Now as far as your ui issue it seems a bit weird as I cannot reproduce. Can you share the output of docker logs tailscale please?