Verify the message through the established support channel, then follow the player’s supported method for updating the endpoint. Keep the old private record and any settings backup until the new configuration works. Do not replace an address based solely on an unsolicited message.
Confirm the scope of the change
Ask whether only the server address changes or whether the username, password and account method also change. A partial update can produce a misleading authentication failure. Copy the full endpoint including protocol, port and path exactly as supplied.
Use an editable profile where supported
Some players allow account details to be changed without deleting local organisation. Others require a fresh profile. Check the app’s documented behaviour and avoid removing the working entry before preserving favourites or other settings that may be tied to it.
Test and tidy afterwards
Open the intended profile and try a small relevant selection. If a new profile was necessary, label it clearly during testing and remove the stale entry once the replacement is established. Keep account-bearing URLs out of public screenshots when reporting any remaining error.
