If you are using Cloud Print on a Mobility Print server version earlier than v1.0.3770, you will need to upgrade, in order to keep users printing via Cloud Print.
Check that auto-updates are enabled on your server. Refer to the Mobility Print advanced configuration page and ensure your server can reach the following endpoints: [Windows] https://mobility-print.papercut.com/client-version/v1/check-update/pc/win [Mac] https://mobility-print.papercut.com/client-version/v1/check-update/pc/macos [Linux] https://mobility-print.papercut.com/client-version/v1/check-update/pc/linux If your organization does not allow auto-updates, you’ll need to manually update your server before Tuesday 7 October. Download the latest Mobility Print server installer here . On versions v1.0.3770 or later of Mobility Print Server, if you are using Cloud Print, an update to the firewall outbound rules may be required if you see the following message in the Mobility Print Admin UI:
"To ensure users can keep printing via Cloud Print, follow the details on the Cloud Print update page"
You will need to update firewall outbound rules by replacing mqtt.notifications.cloud.papercut.com with notif.mp.cloud.papercut.com (IP(s): 3.13.10.206, 3.147.218.242). See the Mobility Print system requirements page for more information.
There are no Mobility Print client updates required for this change to take effect.
Articles in this section
- PaperCut MF - New SSL certificate (macOS)
- New KB article template
- Xerox embedded devices - Incorrect login screen issues
- Handling hidden characters in card numbers
- Scan to multiple email destinations
- PaperCut NG/MF Security Bulletin (March 2026)
- PaperCut Hive and Pocket Compatibility Tool
- Enabling ARM64 support in PaperCut NG/MF Print Deploy
- Incorrect stapling when printing multiple copies via a Find-Me queue using HP PCL drivers
- Resetting the PaperCut Hive or Pocket app (Android & iOS)
Comments
0 comments
Please sign in to leave a comment.