Skip to content

Without opening ports

Your domain without touching the router, with a Cloudflare tunnel, or your devices inside your Tailscale network. How it's done and what each one costs you.

If your ISP uses CG-NAT (no public IP of your own), its router won't let you open ports, or you'd rather not open them, there are two ways. Both work with a connector that reaches out from your machine, so you open nothing:

  • Cloudflare tunnel: your domain, over HTTPS, for anyone.
  • Tailscale: your devices get in as if they were at home. With Funnel, anyone can too, on a .ts.net name.

What you gain and what you lose

Cloudflare tunnelTailscaleTailscale Funnel
Who gets inAnyoneOnly your devices with TailscaleAnyone
Your domainYesNo: the machine's name or .ts.netNo: name.your-tailnet.ts.net
HTTPSYes, Cloudflare'sWith tailscale serve; otherwise HTTP inside an encrypted tunnelYes
Who sees the trafficCloudflare decrypts and re-encrypts itNobody: end-to-end encryptedNobody: HTTPS ends on your machine
Limits100 MB per request on the free plan; its terms limit serving lots of videoNone of its ownOnly ports 443, 8443 and 10000; limited bandwidth

For lots of video away from home, opening 443 with a reverse proxy (Synology or Docker and Linux) is still best, if your connection allows it.

Cloudflare tunnel

A small connector, cloudflared, opens an outgoing connection to Cloudflare, and Cloudflare serves your two addresses over HTTPS through it. You need a Cloudflare account (the free plan is fine) and your domain managed by Cloudflare (its nameservers at your registrar).

Create the tunnel

In Cloudflare, Zero Trust → Networks → Tunnels → Create a tunnel, of type Cloudflared. Give it a name, such as kumoyami, and install the connector with the command it gives you (on Docker, Linux, Windows or macOS).

Both addresses, to 4890

Under Public hostnames (in the newer dashboard, Published application routes), add two, both with the HTTP service to 4890:

HostnameService
app.example.comhttp://localhost:4890
drive.example.comhttp://localhost:4890

localhost works if cloudflared is installed on the same machine. If it runs in a container in the same docker-compose.yml as KumoYami, use http://web:4890. Cloudflare creates the DNS records itself.

Save the addresses

In the panel, System → Modules: https://app.example.com for the Library and https://drive.example.com for Files.

If you manage the tunnel with a configuration file instead of the dashboard, it's the same under ingress, with a final rule for everything else:

~/.cloudflared/config.yml
tunnel: TUNNEL-ID
credentials-file: /home/your-user/.cloudflared/TUNNEL-ID.json

ingress:
  - hostname: app.example.com
    service: http://localhost:4890
  - hostname: drive.example.com
    service: http://localhost:4890
  - service: http_status:404

And the DNS records, with cloudflared tunnel route dns kumoyami app.example.com (and the same for drive).

The installer sets it all up with --access cloudflare; with Docker by hand, the cloudflared service and the CF_CONNECTING_IP_FROM variable are in Cloudflare tunnel.

What you need to know

  • Big uploads. Uploads from the site go in 8 MB pieces and pass through fine. The network drive (WebDAV) uploads each file in one go, and Cloudflare cuts requests over 100 MB on the Free and Pro plans.
  • Video. Cloudflare's terms don't allow using its free network mainly to serve video: with heavy use they may limit you. Also, every video takes the long way round through Cloudflare, with a little more waiting when it starts and when you skip. To watch films away from home often, open 443 if you can.
  • Cloudflare sees the traffic. It decrypts HTTPS on its network to hand it to you through the tunnel. That's how its proxy works.
  • From home through the tunnel, your devices arrive with your home's public IP, so the Library sees them as "away". At home, use http://MACHINE-IP:4891 and :4892.
  • WebSockets go through the tunnel without doing anything (under your domain's Network → WebSockets, leave them on).

Tailscale

Tailscale joins your devices into a private, encrypted network that works from anywhere. Install it on KumoYami's machine and on your devices, with the same account. On a Synology it's in Package Center; on Linux:

curl -fsSL https://tailscale.com/install.sh | sh
sudo tailscale up

Like at home: ports 4891 and 4892

With nothing else to set up, from any device on your Tailscale network:

  • http://machine-name:4891: the Library.
  • http://machine-name:4892: Files.
  • http://machine-name:4890/admin: the panel.

The machine's name works with MagicDNS on (under DNS in the Tailscale console); otherwise, use its 100.x.y.z IP. In Docker, the ports have to be published on every interface ("4890-4892:4890-4892"): with 127.0.0.1: in front they can't be reached over Tailscale.

It's the simplest way, and Tailscale encrypts the traffic, but the browser sees http://: without HTTPS there are no passkeys, no installing as an app and no push notifications. Tailscale addresses count as home for the Library.

With HTTPS, inside your network: tailscale serve

In the Tailscale console, under DNS, turn on MagicDNS and HTTPS Certificates. Then, on the machine, send each Tailscale HTTPS port to a module's port: 443 to Files (4892) and 8443 to the Library (4891):

sudo tailscale serve --bg --https=443 http://localhost:4892
sudo tailscale serve --bg --https=8443 http://localhost:4891

One name, both modules, for your devices only:

  • https://machine-name.your-tailnet.ts.net: Files.
  • https://machine-name.your-tailnet.ts.net:8443: the Library.

There's nothing to save: KumoYami knows the module by the port each request arrives on. Save these two addresses in System → Modules (the Library's with its :8443) only if you want the launcher's cards and the emails to link to the .ts.net names. sudo tailscale serve status shows what's published, and sudo tailscale serve reset removes it all.

It also works if KumoYami runs in Docker with its ports published on 127.0.0.1 only, as in its docker-compose.yml: tailscale serve reaches them from the machine itself. The panel stays at http://machine-name:4890/admin (or on the machine itself); to have the panel over HTTPS too, use the third port, --https=10000 http://localhost:4890.

The installer does it another way, with two nodes in containers, kumoyami (Files) and kumoyami-app (the Library): see Tailscale.

For anyone: Funnel

Funnel publishes the same as serve to the internet, on the same ports:

sudo tailscale funnel --bg --https=443 http://localhost:4892
sudo tailscale funnel --bg --https=8443 http://localhost:4891

In Tailscale's access policy, allow Funnel for that machine (nodeAttrs with funnel). Before choosing it:

  • Only on the .ts.net name, never on your domain.
  • Only on ports 443, 8443 and 10000.
  • With limited bandwidth, which Tailscale doesn't publish: fine for sharing something, not for watching films often.

If something goes wrong

502 Bad Gateway or Cloudflare error 1033

  • Error 1033: the tunnel isn't connected. Check that cloudflared is running (in Cloudflare, the tunnel shows as Healthy).
  • 502: the tunnel gets through, but cloudflared can't find KumoYami. localhost:4890 only works if cloudflared is on the same machine; from a container, web:4890. Check KumoYami is running too.

WebSocket errors or "connection lost"

In Cloudflare, check that Network → WebSockets is on for your domain. With Tailscale, nothing is needed.

Certificate error

  • Cloudflare: Cloudflare provides the certificate. If the browser warns, the name isn't in the tunnel or its DNS record isn't Proxied (the orange cloud).
  • Tailscale: turn on HTTPS Certificates under DNS. The first visit to a .ts.net name can take a few seconds while the certificate is issued.

"413" when uploading through the network drive

It's Cloudflare's 100 MB per-request limit. Upload those files from the site, which goes in pieces, or at home.

The launcher, the other module or "nothing published" shows up

  • With a Cloudflare tunnel, Files shows on the Library's address: an unsaved domain shows Files. Save the Library's in System → Modules, exactly as in the browser.
  • With tailscale serve, the launcher shows: that Tailscale port goes to 4890. Send it to 4891 or 4892, as in With HTTPS, inside your network, or save the address with its port (https://machine-name.your-tailnet.ts.net:8443).
  • "Nothing published": that module is turned off in System → Modules.

Every case, in How KumoYami picks the module.

:4891 won't load over Tailscale

In Docker, the ports are published on 127.0.0.1 only: publish them as "4890-4892:4890-4892". Also check that both devices show as connected in the Tailscale console.

All trademarks and logos belong to their respective owners. Their use only indicates compatibility, not sponsorship or affiliation. The Synology logo is a trademark of Synology Inc.; Google Drive, Google Cast and Android are trademarks of Google LLC, and the Android robot is reproduced from work created and shared by Google, used under the Creative Commons Attribution 3.0 license. Microsoft, Windows and OneDrive are trademarks of the Microsoft group of companies; Amazon S3 is a trademark of Amazon.com, Inc. or its affiliates; Apple, AirPlay, macOS and iPhone are trademarks of Apple Inc.; Raspberry Pi is a trademark of Raspberry Pi Ltd; Ubuntu is a trademark of Canonical Ltd.; Debian is a trademark of Software in the Public Interest, Inc.; Linux is a trademark of Linus Torvalds. This product uses the TMDB API but is not endorsed or certified by TMDB.