SOLVED: JF randomly stopped working

[Toasted]

Hi all,
I've been thoroughly enjoying JF and all it has to offer. I went through the process of even setting up a reverse proxy via NoIP and Caddy. So far it has been flawless. Until the other evening I could no longer access my server non-locally.

I've verified that my reverse proxy is setup correctly, as well as my caddyfile, but alas, I can no longer access the server. Below is the pastebin (sorry, it's long) that shows the most recent Log for JF version 10.8.13. A note: This error also occurred on version 10.8.10 and I thought an update to JF would fix my issue. I'm at a loss, and I would appreciate some guidance

https://pastebin.com/iUkgvMKG

[tmsrxzar]

log does not contain any errors [ERR]
the schema warnings can be ignored https://github.com/jellyfin/jellyfin/issues/6989

not sure the log contains the clue to what the issue is, or i just dont see it

[Toasted]

huh, well now I'm at a complete loss lol. I legitimately didn't change a single thing. I guess it's going to be a looong night of troubleshooting, as I have no real place to start with possible issues. That log, I provided above was my only "new" occurrence since issues arose. As you stated, nothing is throwing an error in it tho. I appreciate your quickly reply !

[tmsrxzar]

i would check caddy, verify noip is going the right place, ping your domain name from an external network, do a quick tcp check to the ip:port from an external network (telnet); that should start you somewhere

[Toasted]

i would check caddy, verify noip is going the right place, ping your domain name from an external network, do a quick tcp check to the ip:port from an external network (telnet); that should start you somewhere

Roger that, nothing from pinging the name externally, although noip is all setup correctly...I may uninstall caddy entirely and set it back up tomorrow. I'll report back with my findings!

[Toasted]

i would check caddy, verify noip is going the right place, ping your domain name from an external network, do a quick tcp check to the ip:port from an external network (telnet); that should start you somewhere

Before I wipe everything and start over, this is what I get (https://pastebin.com/MgpTSH4p) trying to run the caddyfile. I'll note that it has always served the message about incorrect format, and never gave me issues. Running caddy fmt returns a "cannot format caddyfile" as well. I never paid close attention to the 'admin endpoint' portion, and I'm hoping there is some sort of clue as to what may be happening. I also replaced the 'domains' portion with a default named address to protect myself. Hopefully I didn't leave any revealing information either. Networking isn't my strong suit by any means

I've followed this guide (https://www.reddit.com/r/jellyfin/commen...dated_aug/) to a 'T' and it has worked for nearly a year with no issues up until now. There have been no recent hardware or software changes that could've changed networking settings either

[TheDreadPirate]

When you say "NoIP is setup correctly" what do you mean by that? Check your NoIP dashboard and https://whatismyipaddress.com/ match up. This 100% sounds like your NoIP update client isn't working and your WAN IP changed.

[Toasted]

When you say "NoIP is setup correctly" what do you mean by that?  Check your NoIP dashboard and https://whatismyipaddress.com/ match up.  This 100% sounds like your NoIP update client isn't working and your WAN IP changed.

Per this (https://imgur.com/a/gYlabsL) I'm good(?). I also used the website you provided and it matches. NoIP is paid for and working as intended, the necessary ports (80,443) are open/port forwarded on my router, as well as the correct inbound rules on my windows 10 firewall

[TheDreadPirate]

Is your ISP blocking port 80 and 443? I've seen this happen before with other people whose servers "suddenly stopped working" externally. What happens if you change your setup to use something like 50080 and 50443 for remote connections?

[Toasted]

Is your ISP blocking port 80 and 443?  I've seen this happen before with other people whose servers "suddenly stopped working" externally.  What happens if you change your setup to use something like 50080 and 50443 for remote connections?

...you're an actual godsend. YUP, they blocked both ports. It works immediately now. Any suggestions to not have this happen in the future? My qbitorrent client is bound to my vpn, so I knew that wasn't the cause of it.