2024-09-29, 12:04 AM
(This post was last modified: 2024-09-29, 12:06 AM by TheDreadPirate. Edited 2 times in total.)
Negatory. Subdomain CNAMEs can point to domain names. They can also be a completely different IPs.
"jellyfin" is a cname that points to my domain. So jellyfin.domain.tld would resolve to my public IP. This allows you to have multiple services listening on the same port since the reverse proxy would direct traffic to the proper destination based on the subdomain used. This also allows you to change how Cloudflare handles each subdomain. Whether DNS only or proxying. If you used subPATHs you wouldn't be able to do this. Like domain.tld/jellyfin.
"jellyfin" is a cname that points to my domain. So jellyfin.domain.tld would resolve to my public IP. This allows you to have multiple services listening on the same port since the reverse proxy would direct traffic to the proper destination based on the subdomain used. This also allows you to change how Cloudflare handles each subdomain. Whether DNS only or proxying. If you used subPATHs you wouldn't be able to do this. Like domain.tld/jellyfin.
Jellyfin 10.10.1 (Docker)
Ubuntu 24.04 LTS
Intel i3 12100
Intel Arc A380
OS drive - SK Hynix P41 1TB
Storage
3x WD Red Pro 6TB CMR in RAIDZ1 (JF Library)
![[Image: GitHub%20Sponsors-grey?logo=github]](https://img.shields.io/badge/GitHub%20Sponsors-grey?logo=github)
Ubuntu 24.04 LTS
Intel i3 12100
Intel Arc A380
OS drive - SK Hynix P41 1TB
Storage
3x WD Red Pro 6TB CMR in RAIDZ1 (JF Library)