This page describes what to do if you start your StrongDM Desktop application and it’s stuck initializing, as seen here.
- Check your sdm.log for errors related to client.listen, which should be located at:C:\Users\<USERNAME>\.sdm\sdm.log
- Look for the following error, which indicates that either the port (65220) used by the StrongDM client is in use by another application or it could be reserved.
level=error msg="[client.Listen] failed to listen" addr=127.0.0.1:65220
error="listen tcp4 127.0.0.1:65220: bind: An attempt was made to access a
socket in a way forbidden by its access permissions."
- Check if another application is using port 65220 by running:
Get-Process -Id (Get-NetTCPConnection -LocalPort 65220).OwningProcess
- Then you can try one of two options, depending on whether or not the port is in use.
Option 1: If the port is in use by another application, close that application and start StrongDM Desktop. You may be able to restart the other app after StrongDM Desktop is running.
Option 2: If the port is not in use, check if the port is in the exclude range by running:
netsh interface ipv4 show excludedportrange protocol=tcp
- If your output shows 65220 in this list, as the example output above does, run the following commands to reserve 65220 and 65230 for StrongDM:
net stop winnat
netsh int ipv4 add excludedportrange protocol=tcp startport=65220 numberofports=1
netsh int ipv4 add excludedportrange protocol=tcp startport=65230 numberofports=1
net start winnat