Adam Driscoll
Hello Adam,
first of all, thanks for the quick response and the great explanation. I took your solution approach and changed my appsettings.json for both instances accordingly. My port-conflict on server startup ist now resolved. One thing i noticed is though that the callback-ports for the Devolutions login are not running on the loopback address 127.0.0.1 or its IPv6-equivalent ::1. Is this behavior intended? I checked that with the following command (you may need to change the filter in the "where"-clause).
Get-NetTCPConnection -State Listen | Select-Object @{name = 'Server'; expression = { $env:ComputerName } }, LocalAddress, LocalPort, OwningProcess, @{name = 'Commandline'; expression = { (Get-Process -Id $_.OwningProcess).Commandline } } | Where-Object {$_.CommandLine -like "D:\*"} | Format-Table
Thats the output from my server. Port 60370 and 60371 are the configured "PSULoginPort"-ports.
Server LocalAddress LocalPort OwningProcess Commandline
------ ------------ --------- ------------- -----------
S107123 :: 60371 4028 D:\psu_test\app\Universal.Server.exe
S107123 :: 60370 4016 D:\psu_prod\app\Universal.Server.exe
S107123 ::1 49882 4028 D:\psu_test\app\Universal.Server.exe
S107123 ::1 49812 4028 D:\psu_test\app\Universal.Server.exe
S107123 ::1 49810 4016 D:\psu_prod\app\Universal.Server.exe
S107123 :: 8443 4028 D:\psu_test\app\Universal.Server.exe
S107123 :: 443 4016 D:\psu_prod\app\Universal.Server.exe
S107123 127.0.0.1 49882 4028 D:\psu_test\app\Universal.Server.exe
S107123 127.0.0.1 49812 4028 D:\psu_test\app\Universal.Server.exe
S107123 127.0.0.1 49810 4016 D:\psu_prod\app\Universal.Server.exe
Since the callback-ports are not whitelisted in the Windows Firewall, they are not reachable from the clientside, and PSU works totally fine. Is it probably no issue in my use case, because we dont use the devolutions login?
Thanks in advance for the help.
Best regards,
Markus
Special Q&A