Printer failing to connect to the server. Unable to use cloud services

U1 Toolchanger
1

Hey,

I’ve been using my U1 for about 14 days without larger issues. Suddenly I am not able to use the internet connectivity / “cloud mode” at all, the printer simply isn’t able to connect to Snapmaker’s servers. LAN mode works fine. I tried to log out of the account on the printer, and now I am not even able to get the login PIN / QR code to generate (on Global region, it works with China region for some reason, but I am based in EU), as it is stuck on “verifying device” in the GUI.

I first noticed it because my mobile app wouldn’t load the printer’s status, but later I wasn’t even able to send a print from Snapmaker Orca and had to switch to LAN mode to keep printing.

I tried restarting the printer as well as connecting it to a mobile hotspot from my mobile data to make sure my WiFi isn’t causing the issue.

I did some digging in fluidd and found a mqtt log which seems to capture the issue. Here is a snippet (this goes on and on):

[2026-05-09 02:34:31.410] [lava] [info] [AGENT]:425 Fetched access code
[2026-05-09 02:34:31.410] [lava] [info] [AGENT]:783 State transition: GET_ACCESS_TOKEN -> FETCHING_AUTH_INFO
[2026-05-09 02:34:31.413] [lava] [info] [AUTH]:235 Won't refresh CA!
[2026-05-09 02:34:31.575] [lava] [warning] [AGENT]:199 drop local response, not connected
[2026-05-09 02:34:31.860] [lava] [error] [AUTH]:793 GetMqttCerts: unexpected code: 602011
[2026-05-09 02:34:31.860] [lava] [error] [AUTH]:627 Failed to get MQTT certs
[2026-05-09 02:34:31.860] [lava] [warning] [AGENT]:462 Failed to obtain authentication info, retrying...
[2026-05-09 02:34:32.212] [lava] [info] [ISVC]:423 ReqUpdateDeviceStatus: device name U1, status: 1
[2026-05-09 02:34:32.212] [lava] [debug] [AUTH]:1137 ApiDeviceUpdate param: {"name":"U1","online":1}
[2026-05-09 02:34:32.990] [lava] [info] [ISVC]:423 ReqUpdateDeviceStatus: device name U1, status: 1
[2026-05-09 02:34:32.990] [lava] [debug] [AUTH]:1137 ApiDeviceUpdate param: {"name":"U1","online":1}
[2026-05-09 02:34:34.861] [lava] [info] [AUTH]:235 Won't refresh CA!
[2026-05-09 02:34:36.423] [lava] [error] [AUTH]:793 GetMqttCerts: unexpected code: 602011
[2026-05-09 02:34:36.423] [lava] [error] [AUTH]:627 Failed to get MQTT certs
[2026-05-09 02:34:36.423] [lava] [warning] [AGENT]:462 Failed to obtain authentication info, retrying...
[2026-05-09 02:34:39.423] [lava] [info] [AUTH]:235 Won't refresh CA!
[2026-05-09 02:34:39.665] [lava] [error] [AUTH]:793 GetMqttCerts: unexpected code: 602011
[2026-05-09 02:34:39.665] [lava] [error] [AUTH]:627 Failed to get MQTT certs
[2026-05-09 02:34:39.665] [lava] [warning] [AGENT]:462 Failed to obtain authentication info, retrying...
[2026-05-09 02:34:42.666] [lava] [info] [AUTH]:235 Won't refresh CA!
[2026-05-09 02:34:42.904] [lava] [error] [AUTH]:793 GetMqttCerts: unexpected code: 602011
[2026-05-09 02:34:42.904] [lava] [error] [AUTH]:627 Failed to get MQTT certs
[2026-05-09 02:34:42.904] [lava] [warning] [AGENT]:462 Failed to obtain authentication info, retrying...
[2026-05-09 02:38:12.822] [lava] [info] [AUTH]:235 Won't refresh CA!
[2026-05-09 02:38:13.056] [lava] [error] [AUTH]:793 GetMqttCerts: unexpected code: 602011
[2026-05-09 02:38:13.056] [lava] [error] [AUTH]:627 Failed to get MQTT certs
[2026-05-09 02:38:13.056] [lava] [warning] [AGENT]:462 Failed to obtain authentication info, retrying...
[2026-05-09 02:38:13.056] [lava] [error] [AGENT]:481 Exceeded maximum retries for fetching auth info, returning to IDLE state
[2026-05-09 02:38:13.056] [lava] [info] [AGENT]:783 State transition: FETCHING_AUTH_INFO -> IDLE
[2026-05-09 02:38:13.060] [lava] [info] [AGENT]:783 State transition: IDLE -> NETWORK_DETECTION
[2026-05-09 02:38:13.085] [lava] [debug] [AGENT]:389 Pinged host at int successfully
[2026-05-09 02:38:13.085] [lava] [info] [AGENT]:783 State transition: NETWORK_DETECTION -> GET_ACCESS_TOKEN
[2026-05-09 02:38:13.086] [lava] [info] [AUTH]:1788 SetRegion: region is valid: int
[2026-05-09 02:38:13.525] [lava] [info] [AGENT]:425 Fetched access code
[2026-05-09 02:38:13.525] [lava] [info] [AGENT]:783 State transition: GET_ACCESS_TOKEN -> FETCHING_AUTH_INFO
[2026-05-09 02:38:13.529] [lava] [info] [AUTH]:235 Won't refresh CA!
[2026-05-09 02:38:13.763] [lava] [error] [AUTH]:793 GetMqttCerts: unexpected code: 602011
[2026-05-09 02:38:13.763] [lava] [error] [AUTH]:627 Failed to get MQTT certs
[2026-05-09 02:38:13.763] [lava] [warning] [AGENT]:462 Failed to obtain authentication info, retrying...
[2026-05-09 02:38:16.764] [lava] [info] [AUTH]:235 Won't refresh CA!
[2026-05-09 02:38:17.004] [lava] [error] [AUTH]:793 GetMqttCerts: unexpected code: 602011
[2026-05-09 02:38:17.004] [lava] [error] [AUTH]:627 Failed to get MQTT certs
[2026-05-09 02:38:17.004] [lava] [warning] [AGENT]:462 Failed to obtain authentication info, retrying...
[2026-05-09 02:38:20.004] [lava] [info] [AUTH]:235 Won't refresh CA!
[2026-05-09 02:38:20.241] [lava] [error] [AUTH]:793 GetMqttCerts: unexpected code: 602011
[2026-05-09 02:38:20.241] [lava] [error] [AUTH]:627 Failed to get MQTT certs
[2026-05-09 02:38:20.241] [lava] [warning] [AGENT]:462 Failed to obtain authentication info, retrying...
[2026-05-09 02:38:23.242] [lava] [info] [AUTH]:235 Won't refresh CA!
[2026-05-09 02:38:23.473] [lava] [error] [AUTH]:793 GetMqttCerts: unexpected code: 602011
[2026-05-09 02:38:23.473] [lava] [error] [AUTH]:627 Failed to get MQTT certs
[2026-05-09 02:38:23.473] [lava] [warning] [AGENT]:462 Failed to obtain authentication info, retrying...
[2026-05-09 02:38:26.473] [lava] [info] [AUTH]:235 Won't refresh CA!

Any idea what is happening?

2

First off, have you updated to the latest firmware? And is the IP address changed by the router when it does a regular lease refresh…I actually had to lock in the IP in my router to make it static and not drop but I also just replaced the old one and didn’t have to do that anymore. BUT, you may want to look at Paxx12-16 firmware upgrade…not only is the video better but I wasn’t losing connections like I was having with stock. If you do the upgrade I also suggest that you do a calibrate and bed level. And switching back to a stock firmware is as easy as putting a USB stick in the back and selecting a stock firmware to switch back and reboot…all done. Regards.

3

Yes, I am running v1.3.0. I’ve contacted Snapmaker support and they confirmed it being a server-side issue. They have been able to fix it on their side and now it seems to be working correctly again.