ctbeke

Can you share logs with me? As far as I know the printer shouldn't call api.ultimaker.com unless specifically asked for.

Which printer are you using? Not all printer types support PETG and thus the material is hidden if such a printer is selected. The material is still installed, just not visible.

Hi, We have read through the logs, and it seems to be 'stuck' on the generic material profiles (it keeps thinking those have to be synced again). We'll investigate why those are not filtered out (because Cura ships with the same or a higher version of them). In the mean time, you can go to marketplace.ultimaker.com and unsubsribe from those, that will make the sync message for them go a way. Chris

Without logs is hard to say what is going on. The logs provided in the 3rd post indicate some kind of network restrictions are in place that prevent Cura from calling the Ultimaker cloud services. The following helpdesk article explains which connections are made and which domains should be whitelisted for all services to work properly: https://support.ultimaker.com/hc/en-us/articles/360012113719-I-am-having-networking-trouble-with-my-printer. If after configuring all of this it still doesn't work, something else is going on in Cura, but with the current logging I cannot find out what that would be.

@TerpsiKore please send your log file. The shorter after a wifi issue occurs the better.

You can dump all the printer logs to USB from the touch screen settings menu.

Great to hear you're back on track. We'd still very much like the logs if that's possible for you so we can examine what went wrong.

You can share cloud-connected Ultimaker printers in teams via https://mycloud.ultimaker.com. Settings can only be shared via the backups tool at this moment, but we have plans to make this easier. Don't know any timelines on that yet though.

Hi, Please export the printer logs to a USB drive an upload them here so we can help you figure out what is going on. After that, a Connect reset (from the printer's touch screen) can help to get the printer back into a working state (while we examine the logs).

Can you upload (or send in a PM) any logs from Cura and the printer? Then we can have a look into what's going on in your case (every case is different in networking related issues).

After a week of testing and fixing some bugs the 2.0.0 stable has now been published on the Marketplace!

Do you have both printers on the stable channel? Maybe re-installing the latest firmware from the stable channel (and then rebooting) helps?

Hi, I've received an update from one of the team members: Hopefully that'll help you out!

Thanks, I have forwarded this information to the team working on Connect.

Hi, Would you be able to extract the printer logs via the display to USB and upload them here or send them in a private message? That'll help us debugging what is going on.

Next to my day job at Ultimaker (working mainly on online services), I maintain the ThingiBrowser Cura plugin. The past couple of days I have worked with BohunkG4mer to completely refactor the plugin in order to support a much requested feature: adding MyMiniFactory. With the refactor, the plugin now supports multiple online repositories to be connected, Thingiverse and MyMiniFactory being currently implemented. I'm sure more will follow. You can download the first Beta build from GitHub and drag it in Cura. Please open an issue request on GitHub when you find any problems during testing! I intend to publish the stable v2.0.0 release in the coming weeks depending on test results. p.s. The Thingiverse API seems more stable now after several weeks of trouble. In the meantime I've submitted v1.5.1 to the Marketplace (pending review by Ultimaker) that prevents some crashes that were caused by Thingiverse API changes.

You can find Ultimaker cloud API documentation at https://api.ultimaker.com/docs/.

In general, for people reading these posts, exposing your printer's reverse proxy directly to the internet is not a good idea. Better to use Ultimaker Cloud for this so your connection is actually secure.

Please send me your email address and username in a private message. Then I can help you further.

Don't shoot the messenger... Anyways, there's a reason it is still in the experimental category. For one thing that usually means it's not clear how to use the settings.

It has since been renamed to "topography size". More details are available in this commit: https://github.com/Ultimaker/CuraEngine/commit/76e9e27b300eee37e6bf0f41af96450c6eed4779.

Feel free to check out the Ultimaker Cloud APIs, they might make your life easier with regards to sending jobs to connected printers.

Still got the same issue (also when clearing cache).

Building on top of what @nallath says, based on customer research we have found that authentication in the local network using a simple username/password simply doesn't cut it. Using Ultimaker Cloud (https://mycloud.ultimaker.com), any UM3 or newer benefits from (a currently basic) form of account-based authentication and team sharing. This is the place that we'll extend with more elaborate access control functionality that fits better with the growing B2B customer profile (but still keep it usable for individuals as well). I also strongly recommend against exposing the printer's local web server to the public internet in any form. If a 0-day exploit is discovered in any of the 3rd party software running on the printer your printer becomes an entrypoint into your entire network. Instead use Ultimaker Cloud and put the printer in a separate (virtual) subnet to block any local access. The connection between the printer and Ultimaker Cloud is securely initiated from the printer and encrypted as well as all G-codes being sent to it from Cura, giving you end-to-end security. In the near future we plan on expanding the Ultimaker Cloud feature set so that the local web interface of Connect can be entirely ignored or shielded off as explained above.

Any of the CAD programs that have plugins available for them in the Marketplace should be a good starting point. Currently all of these are maintained by @thopiekar, are in good condition, and regularly receive updates.