PaperCut Hive - MQTT

[Edu-IT]

Can somebody ping and traceroute these addresses for me and see if it's working?

 

• mqtt.notifications.cloud.papercut.com

• mqtt2.notifications.cloud.papercut.com

• mqtt3.notifications.cloud.papercut.com

[djm968]

8 minutes ago, Edu-IT said:

• mqtt.notifications.cloud.papercut.com

Not resolving, the other 2 addresses are pinging.

[Edu-IT]

Thank you.

[Edu-IT]

Anyone else experiencing issues with Hive not releasing jobs?

[Netwacky87]

No one is complaining here...yet...😆

[Edu-IT]

9 minutes ago, Netwacky87 said:

No one is complaining here...yet...😆

Do those above links work for you, if you do a ping / tracert?

[Netwacky87]

15 minutes ago, Edu-IT said:

Do those above links work for you, if you do a ping / tracert?

 

Same as @djm968

 

First one doesn't resolve but other 2 do.

[aydee]

20 hours ago, Edu-IT said:

Anyone else experiencing issues with Hive not releasing jobs?

We have this on a few random MPF's.

Like the jobs appear on the device screen, press release but nothing comes out. But we have only just moved to Hive this summer so we were thinking its a config thing or somthing we havent gotten around to investigating yet.

 

Same as the other guys though, mqqt2 & 3 ping and trace fine; but mtqqt does not.

 

Edited Friday at 09:54 by aydee

[Anthony-SpectrumIT]

On 10/09/2026 at 13:59, Edu-IT said:

Anyone else experiencing issues with Hive not releasing jobs?

 

Hello there 👋🏻

 

A few of the schools that we migrated to PaperCut Hive over the summer also experienced intermittent issues with releasing jobs from printers. It was related to communicating with MQTT API endpoints in PaperCut Hive. We migrated 6 schools over the summer and half of them were experiencing issues. It turns out after reviewing the Edge node client logs on the node that attempts to print the job, that it was unable to communicate with mqtt3.notifications.cloud.papercut.com. It turns out that they have an agent based web content filter as well as a network filter that was inspecting SSL/TLS which breaks the release job tasks.

 

There is an information banner on the Hive System Requirements KB (source: https://www.papercut.com/help/manuals/pocket-hive/plan-and-get-started/system-requirements/#firewall-and-networking) that states that any SSL/TLS inspection (decryption) can interfere with the commands sent and received by MQTT.

Quote

ℹ️ TLS packet inspection
Please make sure to place exception rules for TLS inspection & monitoring for the PaperCut Hive & Pocket MQTT URLs .

This can interfere with the MQTT-client (IoT) service. This stops the client software from submitting print jobs, and receiving commands from our service.

We have seen this with Secure Access Service Edge (SASE) solutions (Zscaler/Netskope etc), as well as network firewalls with TLS packet inspection.

 

The three schools are using Lightspeed Filter. Once I had added the MQTT URls to the exceptions for both TLS inspection + to the web content filter, we were golden.

 

On 10/09/2026 at 14:11, Edu-IT said:

Do those above links work for you, if you do a ping / tracert?

mqtt.notifications.cloud.papercut.com doesn't resolve so I think that's a dead endpoint, but 2 and 3 do resolve.

 

I hope the above helps! I'm now dealing with another problem where two photocopiers of the same model are in a Follow Me print queue and only one of them is working 😄

But a direct queue works on both... and no helpful logs unlike the MQTT issue.