Getting cloudflared tunnel to work

I went through bigbear’s tutorial on this and it seems rather simple.

Create a tunnel
Enter access token in cloudflared.
Getting status as healthy
Setting path to local ip with the container running on port 3010

Getting this error. Does it have something to do with what network the containers are set to?

Initially i wanted to go with caddy on this, but i am not able to open port 443. Only downside to cloudflare it seems is not being able to stream media.

Anyone have some pointers for me here, what more details should i provide? :blush:


I reinstalled the container i wanted to point to and it worked flawlessly.

I had changed the ports of that container before reinstall and it would not connect through cloudflare, while it did work perfectly on that port locally.

Anyone know why this is?

Did you change the container ports or host ports? You can only change the host ports.

I changed both. Is there a reason why i can’t do that? :melting_face:

If it conflicts with another container host port, i have to do it right?

In my instructional videos, I emphasize the importance of not altering the designated container port as specified in the Dockerfile. This specific port is integral to the application’s configuration within the container; it’s the port that the application inside the container listens on for incoming connections. Altering this port without also updating the application’s settings to match can result in the application becoming inaccessible, because the Dockerfile configures the container environment based on the expectation that the application uses a specific port.

On the other hand, the host port, which is the port on your physical machine or server that routes traffic to the container port, offers flexibility and can be adjusted as needed. This adjustment is possible through port mapping when you run your container. The mapping enables external access to the application inside the container via a chosen host port, effectively acting as a bridge to the fixed container port. You can choose any available host port to route traffic to the container’s listening port, allowing you to work around port conflicts or adhere to external networking requirements without impacting the container’s internal configurations.


So installing both zipline and pingvin share which both use cointainer and web ui port 3000, it is enough just changing the host port and webui port?

Correct, just change the host port and web UI port.