Getting 500 Internal Error after 4.7.2.0 update

[gruppa 3]

I host an Emby server and up until it updated to 4.7.2.0 last night it worked just fine. No changes have been made to the server and it appears to work on computers on the internal LAN and on the localhost, but any attempts to access it from outside the network returns a 500 Internal Error. Any advice would be appreciated.

[Abobader 3470]

Hello gruppa,

** This is an auto reply **

Please wait for someone from staff support or our members to reply to you.

It's recommended to provide more info, as it explain in this thread:

Thank you.

Emby Team

[Luke 42083]

Hi there, please attach the emby server log from when this happened:

Thanks !

[gruppa 3]

Thanks for the reply. Here's the log from the restart after the update.

embyserver-63789897599.txt

[Luke 42083]

HI, where exactly did you see a 500 error? Can you please show a screenshot? thanks.

[gruppa 3]

It's coming up when you try to go to my Emby server in a browser. I have Emby configured on port 80 and the router port forwarding 80 to the Emby server and it has been working fine up until Friday. I know the port forwarding is working because 10.254.254.154 in the screenshot is the internal IP of the server and if I shut down Emby the 500 error does not come up, instead it just times out. The router itself does not have a web interface on port 80 and no other services on the server are running on that port either. I have attached a screenshot of the message but can't find anything in the Emby logs.

[gruppa 3]

So I found the problem after poking around some more. Apparently one of my firewall policies just happened to expire at the same time Emby updated. Removing the expired policy from the Emby rule in the firewall fixed the issue so it was not a problem with the Emby server at all.

[Luke 42083]

Thanks for the feedback !