ShipStation Connect service not detected — Windows service & port repair

Joe B.

Expert ★★★★★ 27,853 satisfied customers

Specialities: Windows 11/10, Printers, Networking, Print Services, Shipping/label apps

Fix “ShipStation Connect service not detected” — Windows service won’t start, ports blocked, firewall/proxy issues

Technician

Hi! We’ll get ShipStation Connect back online so labels and packing slips print again.
Quick triage: Do you see “service not detected” or “Connect is offline” in your browser? Is the tray/icon grey? Are you on Windows 10/11, and do you use an antivirus, firewall, or proxy/VPN? We’ll check the Windows service, ports 80/443, and the localhost WebSocket used by Connect.

Customer

Windows 11. The Connect tray icon is grey and the site says “ShipStation Connect service not detected.” I reinstalled but still can’t print labels to my Zebra.

Technician

Got it. This error usually means the ShipStation Connect Windows service didn’t start or the browser can’t reach it over https://127.0.0.1 (loopback). Common causes: service set to Disabled, blocked port 443/80, corrupted certificate, proxy/SSL inspection, or a stuck Node.js/Electron process. We’ll restart and repair the service + ports + cert.

Customer

Where do I check the service? Also I’m on a company network with CrowdStrike and Zscaler.

Technician

Step 1 — Start the Windows service
1) Press Win+R, type services.msc. Find ShipStation Connect (sometimes listed as SSConnect).
2) Set Startup type to Automatic (Delayed Start) → click Start. If it fails with a port or permission error, make note.
3) End orphaned processes: open Task Manager → kill ShipStation Connect.exe, node.exe, then try starting again.
This fixes most “service not detected” states.

Customer

The service starts then stops. Browser still says not detected. Could a blocked port cause that?

Technician

Step 2 — Repair ports & loopback
• Connect listens on localhost 127.0.0.1 over HTTPS (443) and sometimes HTTP (80) for the browser handshake/WebSocket.
• In an elevated PowerShell, run:
netsh http show urlacl | findstr /i 127.0.0.1
netsh http show sslcert ipport=0.0.0.0:443
If bindings are missing or owned by another app (IIS, VPN client):
netsh http delete urlacl url=https://127.0.0.1:443/ then let Connect recreate them.
• Add Windows Defender Firewall rules to allow ShipStation Connect for Private and Domain profiles. With Zscaler, exclude 127.0.0.1 from SSL inspection.

Customer

After exclusions, the icon turned blue but the site still can’t detect printers. ZPL labels won’t send to my Zebra.

Technician

Step 3 — Reset the local certificate & browser trust
• Open Connect → Settings → Reset Certificate (regenerates the localhost cert).
• Test detection at app.shipstation.com using Chrome/Edge. Clear cache + enable third-party cookies for ShipStation.
• Ensure the WebSocket wss://127.0.0.1 isn’t blocked by extensions (uBlock, privacy tools). Try an Incognito window with extensions off.

Customer

Detection works now, but the printer list is empty. My Zebra ZD420 is connected by USB.

Technician

Step 4 — Map Windows printer drivers
• In Control Panel → Devices and Printers, make sure the Zebra shows with a working Raw/9100 or USB port and the correct ZDesigner or Seagull driver (not “Generic”).
• In Connect, click Printers → Refresh. Toggle Share next to the Zebra so ShipStation can send ZPL labels.
• For 4×6 labels, set driver defaults to 203/300 dpi, stock size 4×6 in, and turn off “Fit to page”.

Customer

Printing works now, but sometimes after reboot I get “service not detected” again. Any long-term fix?

Technician

Yes — for stability:
• Keep ShipStation Connect service at Automatic (Delayed Start) and ensure the Log On account has local admin rights.
• Whitelist the app in AV (CrowdStrike) and exclude 127.0.0.1 from SSL inspection in Zscaler/Proxy.
• If port conflicts recur, reserve the URL ACL: netsh http add urlacl url=https://127.0.0.1:443/ user=Everyone.
• Optional: reinstall Connect (latest build) and repair WebView2/Edge runtime if the UI won’t load.

Customer

Great — service stays online and labels print instantly. Any final checks so scales and printers always show up?

Technician

Final checks:
• In Connect → Printers, ensure your Zebra/thermal printer is Shared and set as the default in ShipStation.
• For USB scales (Stamps/USB HID), allow Connect device access; avoid hubs that power-save.
• Keep Windows Power Management from turning off USB to save power (Device Manager → USB Root Hub → Power).
Need hands-on help applying the commands? Open the chat.

Customer

Perfect — “ShipStation Connect service not detected” is gone and labels print to the Zebra. Thanks!

Technician

Summary: To fix “ShipStation Connect service not detected”, start the Windows service, clear stuck processes, repair localhost (127.0.0.1) port 443/80 bindings and firewall rules, reset the certificate, and re-share printers in Connect. This restores detection, WebSocket handshake, and reliable ZPL label printing.

Quick answer: the accepted fix

Accepted fix when ShipStation Connect service is not detected: set the Windows service to Automatic (Delayed Start), kill orphaned Node/Electron tasks, open ports 80/443 on localhost, reset the Connect certificate, exclude 127.0.0.1 from proxy/SSL inspection, then refresh and Share the printer in Connect.

FAQ

Step-by-step (Windows 10/11)

1. Start ShipStation Connect service → set to Automatic (Delayed Start).
2. Kill orphaned ShipStation Connect.exe/node.exe → restart service.
3. Repair localhost ports 80/443 (URL ACL/SSL bindings) and allow through firewall/proxy.
4. Reset Connect certificate; test in Chrome/Edge; disable blocking extensions.
5. Refresh printers in Connect → Share Zebra/thermal → set correct driver defaults.

Note for mixed environments (macOS)

1. ShipStation Connect for macOS also uses localhost; ensure no proxy app intercepts it.
2. Grant Accessibility/USB permissions so printers and scales appear in Connect.

Sources

• ShipStation — Connect troubleshooting
• Microsoft — HTTP.SYS URL ACL & SSL bindings
• Google — Allow sites to connect to insecure/localhost resources

Matt ● replies in < 1 min

Technician Expert

⭐⭐⭐⭐⭐ Trusted by 27,000+ customers

Alex · Expert's Assistant

Start Chat

5 Tech Support Specialists are online right now.