MakerWorld will not load in the browser, Bambu Studio cannot see the printer, and with a VPN on the phone both work. Or you updated Studio and the install ended with Failed to install the plugin. Please check whether it was blocked.... The two symptoms look nothing alike, but they share something: the problem is neither the printer nor the account. It is the path between your computer and Bambu's servers.

What the network plugin does

Bambu Studio is not finished when the installer is. The slicer downloads the part that talks to the printer and to the Bambu cloud as a separate component: the network plugin. The Bambu wiki page devoted to troubleshooting this plugin gives the location for Windows: the plugins folder inside AppData\Roaming\BambuStudio in your user directory.

The practical consequence: if the plugin never downloaded or cannot load, slicing and saving G-code keep working, but the printer side does not. The Bambu wiki's remote control page states it plainly: without the plugin installed you cannot send a print job over the network and the Device tab is unavailable. So part of what gets described as "it will not find the printer" is really a plugin problem.

The test that separates them: MakerWorld in a browser

You can narrow down which side to look at in one move: open makerworld.com in a browser.

If it loads, your computer is reaching Bambu's servers, so look at Studio, at the account or at the local network. If it does not load, the slicer is not the problem: your computer cannot reach those servers at all, and Studio not seeing the printer is a consequence of that.

The Russian thread on the forum is exactly this second case. What the original poster describes, in translation:

One day I sat down at my desk, opened makerworld.com and the site would not load; in the same way Bambu Studio stopped seeing the printer.

Do not miss the distinction here: the printer also goes missing from the list when you are signed into the wrong account, but in that case the site loads and the error comes from the account side. The account's region and two accounts getting crossed are covered separately in sign-in problems.

The forum observation: it only works through a different route

The poster writes that they waited all day thinking the servers were under maintenance, and that the next day, after many attempts, they could reach the sites with a VPN on. The accepted answer is the fix they found themselves:

I turned the VPN on on my phone, then shared wifi from the phone to the computer and the printer. Everything works. Bambu Studio found the printer.

I am passing that on as the solution one forum user found, not as advice. The part that is useful for diagnosis is this: if the connection only comes up through a different route, the problem is not the printer and not the account. The forum does not spell this out, but sharing the connection with the printer as well makes sense: the printer reaches the cloud over its own connection, so changing only the computer's route does not cover it.

The thread is dated April 2025 and it is long. Under the same title there is a second wave in October 2025: the job uploads to the cloud and the printer sees it, but cannot download the file. There another user suggests the route that takes the cloud out of the picture entirely: putting the printer in LAN Only Mode. The steps and the cost are in connection errors.

When the plugin will not install

The second forum thread is a completely different symptom: macOS Sequoia 15.3.2, VPN off and off from the start. Studio had installed without trouble the day before, and the error appeared after the next morning's bug fix was installed. The error text, verbatim:

Failed to install the plugin. Please check whether it was blocked...

The user writes that nothing appeared blocked in the system security settings, and that reinstalling the previous build did not help either. The accepted answer is a single line: restart the application after the install, the plugin should be installed and running. It costs nothing to try, which is why it sits at the top of the list.

In the replies one user writes that a single restart was not enough and the plugin came up on the third; another says that restarting the Mac and the app did not help at all. One user says the problem appeared after build v02.00.01.50, while the reply from Bambu states that it had been fixed in an internal build and that the fix would arrive with the next update. The thread is dated March 2025. Do not assume that answer maps one to one onto the current build; the same error text can appear on later versions for other reasons. Even so, "restart it first" remains the first thing to try. Running an old and a new build at the same time can put the plugin in conflict too; how to keep the two apart is in the beta and stable article.

The checklist, in order

These are not claims, they are an order of attempts:

  1. Close the application and open it again. For a plugin error right after an install, this is the accepted answer on the forum.
  2. Try MakerWorld in a browser. If it does not load you are on the cloud side; if it does, you are on the printer or account side.
  3. Check your security software. The Bambu wiki says antivirus software can block or delete the plugin, in which case it has to be whitelisted. On corporate and school networks the block can be on the network side. The Bambu wiki notes the reverse direction too: on macOS some VPN and security software blocks the plugin download, and on Windows leftover proxy or VPN settings from software installed earlier can produce the same failure.
  4. Make sure the plugin file is not held open by another application. The route the wiki suggests is to delete the plugins directory in the data folder with Studio fully closed, and let the plugin download again.
  5. Test the download path. The wiki gives the direct address of the plugin package; if pasting it into a browser starts a zip download, you can reach the plugin server and the problem is elsewhere.
  6. If you cannot reach the cloud at all, you can print without it using LAN Only Mode. The setup is in the connection errors article.

What you lose while the cloud is off

The short answer: with the cloud off you lose remote monitoring, the phone app and the MakerWorld side, including picking up a ready-made print profile. Slicing, saving G-code and sending prints from the same local network stay. The detail of that trade-off is in the connection errors article.

In short, the order is this: first, is the plugin installed; then, is the cloud reachable; last, the account and the local network. Skipping that order and going straight to the account settings usually means spending hours in the wrong place.