After succesfully installing the Plugin CR0.16BL2.80 I cant login to the Cloud Rendering. At the Cloud Rendering Control Panel I provide my username and password and click the login button. But nothing happens. The button flashes blue and that´s it. It also does not matter what I type as username or pw. My Account is validatet and charged. In Blender 2.79 everything is working.
Hi. I uploaded the zip logs to the support ticket. Hope you can find out what is the issue...Thanks again for the great support.
Thanks for the help. I've read what you wrote earlier, and when I opened the task manager, I didn't see the two background processes, that were meant to start, when I start blender. Maybe I have some problems with the software, or maybe I am missing something. Anyway, I'll try to use the advice, that you gave . Thanks for the response :)
Hello, I'm running Blender 2.91, and I had the same issue, where I can't login to my cloud account from blender. I tried restarting Blender, and also my computer, but it didn't solve the issue. Maybe I am doing somethin wrong? This is the first time, that I am using the addon, so I might have messed up something.
Hi @jllibera are you still having issues with logging in? Sorry, I just found I hadn't replied to your earlier post :(
I knew about 2.8 issue, I tried it just because I was desperate. However it brings me interesting conclusion. It seams that there is a correlation between crowd-render for 2.79b and 2.8. After I tried with 2.8 with successful login, now I can't do the same via 2.79b. Even I deleted from 2.8.
2.79b, I tried 2.8 with the same symptoms. It consumes me 40 cents, so it's not much but It stops me from trying.
You're welcome! But oh no! thats not good about the credit. Can you tell me, what build of blender are you using to connect to the cloud? Are you still using 2.79b?
Thanks for fast reply. Finally after I've reinstall blender I menage to login to my cloud rendering panel. Unfortunately now I'm struggling with another issue. I can't connect to any server. Each time I try to connect I receive message: Connection failed, moreover it consumes my credits.
Hi Jan, though I can't read the whole of each line (the image is chopped to the right) what I can see is that our background sync process died. It died because a port it needs is already assigned to something.
This can be due to two reasons:
1. The port is in use by another application, in which case you can try searching for which process has that port open
2. Sometimes CR can load more than one instance of this background process, causing issues. To check, look at all the processes running on your computer. From a fresh start of blender/crowdrender (after a system restart is a good idea) you should see three blender processes. One will be your foreground blender session with the blender GUI. The other two are helper processes we start to manage the render nodes. If you don't have three, then there is something wrong. Usually a restart of Blender will fix it, otherwise, you can kill all the background processes manually (if they don't close with blender), or a system restart will definitely put the system back in a good state.
If you still can't get it to work, please write back so we can investigate further :)
Hi there :)
There's been a little bit of a saga with 2.80. Thankfully today we may have just resolved it. I won't repeat all the detail here as really there's too much. Basically until only a few hours ago, blender 2.80 beta (latest daily versions, post 2.80.41) had a breaking change which rendered our add-on quite explosive. That has now, hopefully, been fixed by a commit earlier today, I am going to find out if this is true and if so, we'll let you know.
We've also been holding off on another fix we needed to make to our build which could very well be what is stopping you from logging in. That fix is for the 2.80 compatible build of our addon.
So, apologies that you can't login, yet, stay tuned as we test the latest daily build of the 2.80 beta. I'll post back when we've confirmed its working, we'll also update our addon with the other fix I've mentioned and test, then we'll be sending out announcements via e-mail to let all know its fixed.
If there's anything else you need, feel free to let us know :)