Is your browser blocking your printer? Test it for free
This test takes a few seconds, requires no installation and sends no data. It checks one thing, but the right one: does your browser still allow a web page to reach a program installed on your own computer? That mechanism is what your receipt printing depends on.
Connection test
Run the test from the till station and the browser where printing stopped working.
How to read the result
A perfectly healthy computer gives a paradoxical result: the page effortlessly reaches servers thousands of kilometres away, yet can no longer reach a program running a few centimetres away, on your own machine. That is not a fault: it is a browser security measure, active since Chrome 142 (October 2025). It protects your network — and breaks receipt printing for POS software running in the browser along the way.
What this test cannot do — and why that matters. It cannot tell you whether your printing utility is running. The browser cuts the connection before it reaches it: a stopped utility and a running but unreachable one return exactly the same result. We measured it on 2 September 2026 on Chromium 148: open port → failure in 2 ms, closed port → failure in 1 ms. No usable difference. That is precisely what makes this failure so baffling: it is silent, and nothing points to where it happens.
The test is negative: the connection still gets through
If the third line is green, your browser does not (yet) apply this blocking, and your printing problem most likely comes from somewhere else. Check, in this order: the paper roll and the lid, the USB cable, your vendor's printing utility (is it actually running?), then the printer driver. Our FAQ covers these cases.
The test is positive: the connection is cut
This is the case we fix. The blocking happens inside the browser, so that is where the path must be restored. Browser extensions are not subject to this restriction: that is the route our solution takes. We verified it in real conditions: where the page fails, the extension relays the receipt in 12 milliseconds, content intact.
See how we restore printing → The illustrated install guide
Frequently asked questions about this test
Does the test send information about my sales?
No. Everything happens in your browser: the test only measures whether a connection to the local address 127.0.0.1 succeeds. No receipt content, no sales data and no result is transmitted or kept.
Why test several ports?
Every POS vendor has its printing utility listen on a different port. We test a few of the most common ones. On a browser that applies the blocking, the result is identical on every port anyway: it is the route itself that is cut, not one particular door.
Can I just switch browsers?
Moving to a browser that does not yet apply this blocking helps for the moment, but it is a sticking plaster: the restriction is a web standard set to become general, and you impose a daily change of tool on your staff. See the FAQ.
Can the result be misleading?
Yes, in two cases: if you run the test from a station other than the till, or from a browser other than the one used for sales. The blocking applies browser by browser and station by station: test where the failure actually happens.