Yesterday, 08:07 PM
(This post was last modified: Yesterday, 08:10 PM by TheDreadPirate. Edited 1 time in total.)
A thought occurred. Since you mentioned that your IP did NOT change, I remembered that some ISPs block port 80 and 443 on residental Internet plans. Their justification being that "only businesses need to run a web server".
Try using a non-standard port for the "external" port.
Something like this for the port forwarding rule
external port = 50080 -> internal port = 80
external port = 50443 -> internal port = 443
When you're remote you'd have to add the port to the end of the address. https://jellyfin.domain.tld:50443. NAT Loopback should handle this gracefully as well.
Your ISP blocking port 80 and 443 makes more sense than CGNAT. From other users here that did have CGNAT, they just straight up did not have the ability to setup port forwarding on their ISP provided router.
Regarding setting a cutom DNS entry, IP Alias doesn't look like what we need. And the manual I could find for a router in the same family wasn't much help. If it was accurate, you cannot set a custom DNS entry.
Try using a non-standard port for the "external" port.
Something like this for the port forwarding rule
external port = 50080 -> internal port = 80
external port = 50443 -> internal port = 443
When you're remote you'd have to add the port to the end of the address. https://jellyfin.domain.tld:50443. NAT Loopback should handle this gracefully as well.
Your ISP blocking port 80 and 443 makes more sense than CGNAT. From other users here that did have CGNAT, they just straight up did not have the ability to setup port forwarding on their ISP provided router.
Regarding setting a cutom DNS entry, IP Alias doesn't look like what we need. And the manual I could find for a router in the same family wasn't much help. If it was accurate, you cannot set a custom DNS entry.