Skip to content

Connecting to OpsLink

The run log names it on every start:

remote: LISTENING on http://0.0.0.0:7833 (open http://192.168.4.58:7833)

Or press M in the wheel, which shows the address and password on screen.

The password is in the remote-password file next to your config:

Platform
macOS / Linux~/.vpinops/remote-password
Windows%USERPROFILE%\.vpinops\remote-password

Change it in Settings. It is generated to be typeable on a phone, not to be strong.

  1. Windows firewall. Port 7833, inbound, TCP, private profile. Windows prompts on first run; if that prompt was dismissed, the address simply never answers. This is the single most common cause.

  2. Same network. OpsLink is local by design. A phone on guest Wi-Fi, or on cellular, cannot reach it.

  3. Is it still running? vPinOps deliberately outlives its own windows. If a second copy will not start, the first one is still holding port 7833 — quit it from the tray.

  1. Open OpsLink → LibraryImport

  2. Send a table from this device → pick a .vpx, .vpxz, .directb2s or an archive

  3. It lands in the cab’s .inbox folder. Sending is not importing.

  4. Waiting in your inbox lists what is there. Press Look at these files and you get the usual preview, names and copy or move choices.

Importing copies by default, so the inbox fills up on purpose — your original is never deleted on the strength of an assumption that the import worked.

When you want the space back, the inbox offers to remove files whose table is already in your library, and nothing else. Everything it is keeping is listed with the reason, you see the list before pressing anything, and the button asks a second time before it deletes.