Nearly exact same scenario with me happened as of last night, but with server version 1.16.5.1592 (Very latest I can tell as of this writing). Perhaps 1592 was supposed to fix that symptom for those of you already having it, but now it’s caused others to have it as well? Either way, this is a huge bummer not having it work outside my network anymore, and yes I’ve power cycled all the devices in order etc. still no change…
Main Device: Windows 10 1903 (18362.295)
Server version#: 1.16.5.1592
Player version#: 1.2.0.875-b7362913 (Windows)
