sbigelow

I know, old thread and all of that, but there is an awkward workaround to this huge flaw in Cura. Update the profile with the setting tweaked. (Update profile with current settings / overrides). This is important for step 5. Go to Help --> Show Configuration Folder Close out of Cura. Open the "quality_changes" folder. Sort by date, and you'll see your latest changes in one of the files, if you open the last changed file. Open that file in notepad and search for the value that you changed. (i.e. 205 if you changed your standby temperature to 205). Highlight that entire line and delete it. Save the file Open Cura. Voila, that override setting is back to not being overridden. This would be such a simple flaw to fix. I see constant comments about it, and the devs never seem to think it's a flaw or bug. But, really, that's about the only way to undo an overridden setting.

No, I doubt IT would make an exception for Cura. We are a high tech firm with over 120,000 employees, and corporate security is a high priority. Even though this wouldn't compromise corporate security, it would take an act of Congress to convince the IT people of that, and another act to get them to open the firewall settings. 2 years from now it might actually work, but that's literally how long it would take. Oddly enough, I can SSH out of the firewall and then tunnel through ports over SSH, and that all works well. By the same token, I can log in from S3D and authenticate, going straight through the corporate proxy server. Fusion 360 also works well that way. I guess the way Cura was designed, a proxy wasn't fully comprehended and it was just assumed that a token or local server could be passed from the web browser to the app, instead of trying to talk through the proxy directly using the system settings. Seems like a backdoor method to bypass proxies that will eventually get closed, but appears to work for now in most cases.

Thanks for your response. No, I never saw an "allow" or "deny" prompt, other than the standard Windows Allow / Deny while installing. Two different computers, two different OS, same story. I think it must have something to do with the McAfee firewall, which I cannot change (corporate policy prevents modifying firewall). I see the website trying to make a request to "Localhost" and that eventually times out. At home, that request goes through. I've also tried setting my default browser to IE, and that doesn't work either. It's OK -- I see that Cura *still* doesn't support telling you the model names of parts on the build plate (even with multi build plate option enabled), so I'll just continue to use S3D for most of my work. This is a must-have feature for me. Cura tends to produce better quality slices in my experience, but I work with a lot of models that look very similar.

It seems that Cura 4.0 Cloud will not connect to a remote server behind a proxy. Is this the case? Or is it maybe a security or firewall setting? I click on the "Sign In" button, Chrome launches, I log into my Ultimaker account, wait some time, and then I get the message Not signed in Please allow the application to access the requested data. You can do this by signing in again and clicking Allow. I never see an allow button. Running Windows 7 and Windows 10, same issue. Running Windows 7 at home with no proxy works fine. Does anyone have any tips? I can still connect to the marketplace with no problems.