Use Enable Local Server

What It Is

File > Enable Local Server starts a WebSocket relay inside the Social Stream Ninja desktop app. Pages join the same session room and use matching channels to exchange messages. New installations use 127.0.0.1:3003; an upgraded installation that already used port 3000 may keep it.

This is a relay, not a website host. It does not serve the SSN interface, capture platform chat by itself, or expose the Local Control API.

What It Can Do

Relay supported Social Stream chat traffic between pages using the same session.
Carry supported Dock or remote commands when the matching command route is enabled.
Replace the hosted WebSocket endpoint for pages that support localserver.
Keep selected relay traffic on the SSApp computer.
Accept direct clients from a trusted LAN after LAN access is explicitly enabled.

Support is page-specific. Some pages use localserver directly; others also need the matching server, server2, or server3 route.

Typical Dock Read-and-Reply Setup

Open the Social Stream Ninja desktop app.
Choose File > Enable Local Server. The menu shows the active port.
In Global settings and tools > Mechanics - Connections & Integrations, enable Send chat messages to API server (for external listeners).
Enable Dock sends its commands to Extension via server if replies or Dock commands must return through the relay.
Copy fresh Dock and overlay links from SSApp. The app adds localserver and the active localserverport where needed.
Replace old saved URLs in OBS and reopen any browser pages that were already running.
Send one fake test message and confirm it reaches the Dock before testing replies or overlays.

If the Dock offers Enable Server Fallback, that shortcut enables the normal read and reply routes together. The local-server flag changes those supported routes to use SSApp's relay.

Generated Link Example

A new-install link using the relay may contain:

https://socialstream.ninja/dock.html?session=YOUR_SESSION_ID&server2&server3&localserver&localserverport=3003

Do not add these flags to every page by hand. The exact server flags and channel routing differ between the Dock, overlays, alerts, games, and utility pages. Copy the generated URL for the exact page.

Using Another Port

Choose File > Set Local Server Port.
Select an unused port from 1024 through 65535.
Copy fresh generated links so they contain the new localserverport.
Replace saved OBS URLs and reopen active pages.

Changing this port does not change the Local Control API on 17777 or the local media server on 3001.

Optional Trusted-LAN Access

File > Allow Local Server Connections from the LAN changes the relay from loopback-only to listening on the computer's network interfaces. A client on another device must connect to the SSApp computer's LAN address, not 127.0.0.1. The exact custom WebSocket URL and routing flag remain page-specific.

LAN mode has no authentication or encryption. Use it only on a trusted private network. Do not port-forward it or expose it to the internet. For normal cross-machine internet control, use Social Stream's existing WebRTC or hosted WebSocket transport.

Common Problems

Problem	What To Check
Dock or overlay stays blank	Confirm the source and page use the same session and password, then copy a fresh generated URL with the current routing flags.
The link uses port 3000 but SSApp shows 3003	Replace the old link. New installs add `localserverport=3003`; older installs may intentionally remain on `3000`.
Server will not start	Another program may own the port. Choose another unused port, restart the relay, and recopy links.
Chat arrives but replies fail	The incoming and command routes are separate. Confirm Dock sends its commands to Extension via server is also enabled.
LAN device cannot connect	Confirm LAN access is enabled, the client uses the SSApp computer's LAN IP, and the firewall permits the selected port.