My internal http 500 internal server error might have a different cause but what to do?

General
1

I’m getting the dreaded 500 internal error, which I’m told is a very generic response.

I’ll save you my venting like so many others who started experiencing this a few updates ago.

I’ve tried all the vague solutions that support links you to if you have this issue. But I think I know what’s causing mine. I’m using dynamic dns, duckdns specifically. I think I think the problem may be that plex gives out the IP address, not the dynamic IP. But there doesn’t seem to be a way to tell Infuse to connect to *.duckdns.org:32400

Am I onto something or is this just wrong?

2

No response from support on this?

Am I doomed to getting the same vague suggestions from support that everyone else got? Is that it?

3

It’s most likely that your issue is related to the DuckDNS dynamic URL configuration in Infuse. By configuring Infuse to connect to your DuckDNS domain name, you should be able to resolve the 500 error and allow Infuse to successfully connect to your remote Plex server, even with a dynamic IP.

4

Thank you but howwwww.

5

I repeat: howwwww do I do it