Port 80 & 443 cause Wifi Issues and Are Not Detected

[Jack Aubrey]

Hi guys I've been having a really weird issue regarding port forwarding and wifi connectivity.

I had my Linux Mint based Jellyfin server port forwarded through 80 and 443 and used caddy and duckdns to reverse proxy and all of that. This was working perfectly for accessing it from outside the house for months. One day recently maybe because of flickering power, the wifi stopped working so I unplugged the router and plugged it back in. Ever since then, having ports 80 and 443 port forwarded causes my wifi (not ethernet) to not work properly (minute long page loading if loading at all) and the ports (80 & 443) are only detected by canyouseeme dot org (or any other port checking website) ~30% of the time. 

If I port forward port 4123 and host a simple ping service so that canyouseeme dot org can detect it, it detects it as open 100% of the time and my wifi runs fine. I have tried factory resetting my router. People online say Xfinity blocks ports 80 and 443 sometimes but their official website says they don't.

Router is a Netgear Nighthawk C7000v2 on Firmware Version V1.03.08

I have lost my mind trying to fix this, going so far as to switch my server OS to Ubuntu and wiping my jellyfin, caddy, and duckdns from the machine. 
Is there something simple I am missing? I am going to call Xfinity to ask if they are blocking ports 80 and 443. Is there a different discord server or forum better suited for this issue?

Thanks in advance

[Jack Aubrey]

Comcast says ports 80 and 443 are not blocked.

[34626]

Check for updates for Caddy.
Can you access Jellyfin using the public IP? DuckDNS i suppose is just a DNS service, so if you can access the jellyfin login page by entering your publc IP, then the issue is somewhere else. You may need to accept a invalid ssl certificate since you access it via IP and not a domain

[Jack Aubrey]

I did try updating caddy and restarting it.
I was able to access the jellyfin server if connected localhost:8096 and I believe my duckdns.org url but only when on ethernet.

Importantly though, I also got issues when port forwarding 80 and 443 on a machine that was not using caddy or duckdns.
I used powershell to run a simple service via 80 and 443 and it crashed my wifi and didn't show as open on canyouseeme dot org.
When I used powershell to run a simple service on port 4123, my wifi worked fine and canyouseeme detected it as open.

[34626]

The IP is your public, so the IP you have used for duckdns is the IP you should try in a browser...