“[Errno 10013] error while attempting to bind on address ('127.0.0.1', 443):..." message when activating DeviceHub in PitneyShip, PitneyShip Pro, or PitneyShip Enterprise
Products affected: PitneyShip®, PitneyShip® Pro, PitneyShip® Enterprise
Issue
When activating DeviceHub, the logs show the message “[Errno 10013] error while attempting to bind on address ('127.0.0.1', 443): an attempt was made to access a socket in a way forbidden by its access permissions”
Cause
Port 443 is not available. Another program may be running that is using the port.
Resolution
If you need assistance performing these steps, contact your IT department.
- Right-click on the DeviceHub DH icon in the system tray (small icons near the clock) and choose Exit to close DeviceHub.
- In the Windows search box, type cmd and press Enter to open a DOS command window.
- In the command window, type netstat -ano -p tcp and press Enter. A long list of numbers will be produced.
- Scroll up to the top of the list and look for 127.0.0.1:443 or 0.0.0.0:443. Note number next to it in the PID column.
- Right-click on the Windows taskbar and select Task Manager
- In the Task Manager, select the Details tab.
- Click on the PID column heading to sort the list by PID number.
- Scroll through the list to find the PID number you identified earlier.
- Right-click on that program and select End task to stop the program.
- Start DeviceHub from the desktop shortcut or the start menu.
- Go back to PitneyShip, PitneyShip Pro, or PitneyShip Enterprise.
- Click on Settings in the upper right.
- If you see My Devices, select it, then click Activate DeviceHub.
- If you see Printers & Scales, select it, go to the Settings & Downloads tab, and click Activate DeviceHub.
- Once the activation is complete, refresh the devices list.
If you are still receiving the error after performing these steps, follow these steps for additional troubleshooting:
- Find the application that is using port 443.
- Shut down the application using port 443.
- Start DeviceHub.
- Activate DeviceHub.
- Shut down DeviceHub.
- Restart the original conflicting application.
- Restart DeviceHub.
The features and options you see may vary depending upon your role and subscription. If you have any questions regarding your permissions, please contact your administrator.
UPDATED: November 12, 2026