# An attempt was made to access a socket in a way forbidden by its access permissions

- Link: https://www.agilicus.com/faq/an-attempt-was-made-to-access-a-socket-in-a-way-forbidden-by-its-access-permissions/
- Published: 2024-10-24T01:38:23+00:00
- Author: Don Bowman

The connector and the launcher both might observe this error on a Microsoft Windows
platform when trying to refresh credentials.

The normal operation of the Launcher is to be automatically refreshed via Profile
when the desktop integration is installed. However, if the user does not have the
desktop integration, or, the credentials have timed out, they will see the Launcher
open a browser to facilitate a refresh.

As part of this flow, the Launcher will open a local TCP port (e.g. port 53210) 
on localhost.

Normally the Windows firewall will allow this since the port is localhost only. 
However, some environments require the Agilicus Connector & Launcher to be explicitly
allowed in the Microsoft Windows firewall. In this case, you might see a message“
bind: an attempt was made to access a socket in a way forbidden by its access permissions.”

![Agilicus AuthMatrix error: 'An attempt was made to access a socket in a way forbidden
by its access permissions.' This indicates a firewall or network security setting
is blocking the AuthMatrix client from connecting to the AuthMatrix server. Check
firewall rules and network configurations to allow communication on the necessary
ports.](https://www.agilicus.com/www/2f773248-image-1024x643.png)