Since our Direct Print subscriptions (https://print.ventor.tech/plans) use PrintNode’s infrastructure, standard troubleshooting steps often apply, regardless of whether you use our client or theirs. Note that a portion of your fee helps support their service.
Direct Print / PrintNode Client needs to be able to resolve the following domain names:api.printnode.comapp.printnode.comhost2b.printnode.comclient.printnode.comlon1.printnode.comcentral.printnode.comrdga3b.printnode.combyfa3b.printnode.com
Each of the above domain names can resolve to an IP address in any of the following ranges. Please note that although the ranges are static, the mapping of domain names to IP addresses is not.5.10.27.32/28 (that is, 5.10.27.33 – 5.10.27.46)5.10.23.32/27 (that is, 5.10.23.33 – 5.10.23.62)94.228.44.128/28 (that is, 94.228.44.129 – 94.228.44.142)
Direct Print / PrintNode Client makes outbound connections on ports 443 and 6123.
A good way to test if you can reach our servers is to open a browser and go to https://api.printnode.com/ping. If this doesn’t work, there’s a problem somewhere between your computer and our servers. Try running:tracert api.printnode.com
from the command prompt (Windows), ortraceroute api.printnode.com
from the terminal (macOS / OS X, Linux). This will give you technical information about the way the connection is routed.
If you can reach https://api.printnode.com/ping in your browser, but the Direct Print / PrintNode Client cannot connect, please send us logs and contact us.