Having a lot of trouble accessing ports 80 and 443 on my home network

[telepathicChimp]

Hi everyone.

I have been able to successfully set up a reverse proxy on a remote server to allow access to my Raspberry Pi from the general internet. That hasn't been a problem. What has been excruciating is finding out that apparently, I am not able to access ports 80 and 443, even with port forwarding established. Just take a look at my router's port-forwarding configuration:

---

Service Name: Jellyfin Server
Service Type: TCP
Internal Port(s): 8096~8096
External Port(s): 8096~8096
Server IPv4: 49.57.50.46 

Service Name: HTTP
Service Type: TCP/UDP
Internal Port(s): 80~80
External Port(s): 80~80
Server IPv4: 192.168.0.45
Server IPv6: 2601:47:4980:15b0:0:0:0:b7ca 

Service Name: HTTPS
Service Type: TCP/UDP
Internal Port(s): 443~443
External Port(s): 443~443
Server IPv4: 192.168.0.45
Server IPv6: 2601:47:4980:15b0:0:0:0:b7ca 

Service Name: RPI SSH
Service Type: TCP/UDP
Internal Port(s): 8022~8022
External Port(s): 8022~8022
Server IPv4: 192.168.0.45
Server IPv6: 2601:47:4980:15b0:0:0:0:b7ca 

Service Name: Jellyfin Server
Service Type: TCP
Internal Port(s): 8920~8920
External Port(s): 8920~8920
Server IPv4: 49.57.50.46

---

The Jellyfin Server configurations (automatically generated) work just fine, but for some reason use an IP address that's totally unfamiliar to me (49.57.50.46 - is that just how uPnP works?) whereas the actual static IP address for the ethernet connection, the one that I use to SSH into my RPI, doesn't work. I can't even use certbot without doing a DNS-01 challenge, which, to my understanding, doesn't require port 80 to be open. Also this was going on with ufw disabled, but even when I enable it and allow those ports, I still get this issue.

What is going on here? I am away from my home computer so I can provide more details later, but I spent hours the past couple of days trying to figure out why this was happening. 

Thank you.