2025-04-10, 05:41 PM
(This post was last modified: 2025-04-10, 05:41 PM by TheDreadPirate.)
Using CF tunnels to serve video and audio streams is against their TOS and is not recommended.
Additionally, with the new requirements to set a known proxy, this essentially makes CF tunnels non-viable.
The known proxies field can accept IPs, CIDRS, or host names of the host running your reverse. But not your domain name. Since the IP/host of your CF tunnel host is not constant, using them is not viable. And, again, against their TOS.
Additionally, with the new requirements to set a known proxy, this essentially makes CF tunnels non-viable.
The known proxies field can accept IPs, CIDRS, or host names of the host running your reverse. But not your domain name. Since the IP/host of your CF tunnel host is not constant, using them is not viable. And, again, against their TOS.
Jellyfin 10.10.7 (Docker)
Ubuntu 24.04.2 LTS w/HWE
Intel i3 12100
Intel Arc A380
OS drive - SK Hynix P41 1TB
Storage
4x WD Red Pro 6TB CMR in RAIDZ1
![[Image: GitHub%20Sponsors-grey?logo=github]](https://img.shields.io/badge/GitHub%20Sponsors-grey?logo=github)
Ubuntu 24.04.2 LTS w/HWE
Intel i3 12100
Intel Arc A380
OS drive - SK Hynix P41 1TB
Storage
4x WD Red Pro 6TB CMR in RAIDZ1