Same server name prevents library access after Windows -> Arch migration

Server Version#: 1.43.0.10492

Only after switching from Windows 10 to Arch, and reinstalling PMS with the same server name (M******), did I read on the forums that Plex DOES NOT like multiple same-name servers on one account. Now, the Plex Android and Chromecast apps, and app.plex.tv, that worked yesterday show the server as offline, and media can only be watched on localhost.

Some users in years-old posts have gotten a Plex associate to make edits/deletions to fix this. Is this still the case? Is there another workaround?

I’ve tried removing all Authorized Devices under Settings > Authorized Devices. The new server (M******) shows up with the correct OS information, but it seems that all the apps are still trying to connect to the old server’s ID.

The “friendly name” is irrelevant. It is solely for the server admin, to disambiguate servers from each other on https://app.plex.tv/desktop/#!/settings/devices/pms

What should not be re-used between server instances is the external/WAN port of your router in
Settings - ‘Show Advanced’ - [server name] - Remote Access - “ Manually specify public port”

So, you need to edit the port forwarding in your router and change the external/WAN port number. Then put this same number in the above mentioned input field of the Plex configuration.

[The above is true, unless you are also copying the old server’s “identity” (Windows Registry, or Preferences.xml) over to the new machine. But that is usually only practical if the new server will be running under the samee operating system.]

Thanks for responding so fast! I appreciate the explanations. Unfortunately, the issue was my own configuration of firewalld. For anyone else running Linux and having issues, don’t forget the basics! I’ll mark your response as the solution, since it helped me get in the right mindset.