Troubleshooting job submission issues, or ‘pressing print!’
“My Jobs aren’t showing up for release”
Make sure that your nodes can speak to the cloud. Try a telnet-test out to mqtt.googleapis.com (see below for examples).
telnet mqtt.googleapis.com 443
If the test is successful you should see:
If the test is unsuccessful you’ll see an error:
Verify that the different nodes on your network can communicate with each other. Try to see if you can access the status page for a few of the Edge Nodes in your network. Prioritize this check against any Super Nodes that you may have in the environment.
To access the status page, open a web browser on a computer on the network, and open:
https://[other-node-ip]:9264/status - where
[other-node-ip] is the IP address of another node that should be online and accessible from the computer that you’re testing on.
If this succeeds, you should see a JSON-formatted page with some information about your Edge Mesh - including some version numbers and Organization ID. To be extra confident in this test, repeat it with a few different pairs of Edge Nodes on your network.
If that doesn’t work, check the Firewall ports and networking section to make sure that all the required ports are open to let the different nodes communicate with each other.
If a job is having problems getting submitted into the Edge Mesh, we’ll want to take a look at the print client service on the machine that’s having issues. Verify that the pc-print-client-service shows up in your Task Manager or Command Center. If this part is not running, you can try to run it manually to see if it was a one-off issue. If you still experience issues, read through our Test Page Failed to Print article. If that doesn’t help, you may need to reach out to your reseller or PaperCut Partner for some additional input.