Nothing Appears

Your application wrote its bytes and the document list stays empty.

Start here: the IP whitelist rejected you

This is the most common cause, and it is silent from the outside - the connection is accepted and then reset, so a client that does not check for errors looks like it printed successfully.

Open Workspace Settings -> Access Log. It lists every connection the workspace received and whether each was allowed, so a rejected attempt from your address is visible immediately, with the address to add.

If your attempt is listed as rejected, add that address in Workspace Settings -> IP Whitelist - see Connection refused or reset for the details. New workspaces start with the whitelist enabled and only the IP they were created from on it, so any second machine - a CI runner, a POS terminal, your laptop on another network - is rejected until you add it.

If your attempt is not in the log at all, the bytes never reached the service: the problem is the address you are connecting to or the network path, not the workspace.

The connection is still open

A document is finalized when the connection closes, or after a short idle timeout once the bytes stop arriving. An application that opens a socket at startup and keeps it forever produces nothing you can look at until it closes.

Close the socket after each receipt - which is what a real printer expects too - or wait out the idle timeout.

The printer is stopped

A stopped printer is not listening at all, so this usually shows up as connection refused rather than silence. Check the state on the printer's card; start it, then print again.

The bytes went somewhere else

With several printers in a workspace it is easy to send to the port of one and watch the documents of another. Compare the port your application is configured with against the port on the card of the printer you are looking at.

The page is not refreshing

Documents arrive over a live stream, but a page left open through a lost connection can stop updating. Reload it. If the document is there after a reload, nothing was lost - it was only the view.

Still stuck?

Email support@virtual-printer.online with the printer's protocol and port, what your application sent, and what you expected to see.