"Failed to connect, invalid authentication" after Luban 4.3.0 upgrade

Snapmaker 2.0
1

I’ve been printing without issue on my A350 for months but just upgraded to 4.3.0 and now Luban can’t connect. The Snapmaker is definitely on the wifi and I’ve tried to reconnect manually with it’s IP but I keep getting the same thing:

“Failed to connect, invalid authentication”

It doesn’t even think about it, just fails. have no idea where to start with this and I didn’t find any support for this particular problem.

Any thoughts? Can I roll back to a older version?

1 Like
2

Yes, just roll back to an older version.
I’m on mac, so don’t know if it’s different on a pc, but I always keep the older version and just add the version to the name. You’ll find that SM more often than not releases versions of Luban that have just as many bugs as the older ones. Just different ones for you to discover. Think of it like an adventure…

I actually still just use 3.14.0 since I don’t have any upgrades or rotary module.

-S

3

Ha! I just rolled back versions and came back here to update the post. Uninstalled 4.3.0 and reinstalled 4.2.3 and we’re back in business. Cheers!

2 Likes
4

I ran into the same problem and then realized there was also a firmware update available for my SnapMaker. After installing the firmware the Luban software had no problems connecting. Beware though, it did reset my calibration, so I had to rerun that.

1 Like
5

I have same problem, how do I roll back to earlier version ??

6

In this post, you can download the older firmware versions:

In this post, you can download the older Luban versions:

7

I found a way to fix this problem, without having to update the device’s firmware: You just have to go into your modem/router settings, and change the ip-address that is assigned to the SnapMaker device.

My guess is that the authentication-data format or procedure changed, so Luban is trying to connect with that stored auth-data, but failing because that data is now invalid. And the user-interface provides no way, as far as I can see, to clear this data. So we have to change the SnapMaker device’s ip-address, which makes Luban think it’s a new device, and so make a fresh attempt at connecting.

Unfortunately, I cannot give details instructions on how to change SnapMaker’s ip-address in your router, as it is different for every router/company.

However:

  1. You can search youtube for “how to open router settings <your router type/company here>”, to open the router settings. (it’s generally at “http://192.168.0.1” or “http://192.168.1.1”)
  2. Once in the router settings webpage, you can go to the “DHCP Reservations” (or some page similarly titled), find your SnapMaker’s entry (match the ip-address in the list with the ip-address shown on SnapMaker’s “Settings → About device”), then change it’s reserved ip-address to something else.
  3. Once the router change is saved, open the “Settings → Wifi” on your Snapmaker, turn off Wifi, wait 5-10 seconds, turn Wifi back on, and then check your new ip-address in the “Settings → About device”. It should match the new ip-address assigned in step 2.

Anyway, it worked for me! (I tried to do the firmware updating, but it kept getting stuck on the final “Updating…” step all 3 times I tried it – though interestingly, the “About device” panel showed a new version number for the firmware after the first attempt, and a new version for the controller on the second attempt, so maybe it partially succeeded in updating; anyway, the connection issue persisted until I did the ip-address reassignment above)

2 Likes
8

Just wanted to report that Wicklund’s fix worked for me as well.

1 Like
9

I’ll just put this here for anyone looking to install older versions, having previously rolled back from 4.4.0 to 4.3.2, now continuing down to 4.2.3 Tags · Snapmaker/Luban · GitHub I’m 0/2, hoping I don’t strike out.

1 Like
10

A more convenient alternative can be seen here: Luban 4.4.0 not connecting - #25 by Wicklunds

(config file edit rather than having to mess with router settings)