Page MenuHome

Cloud repository - SSL Error
Closed, ResolvedPublic


System Information
OS X 10.12.6, NVIDIA GeForce GTX 780M 4096 MB

Blender Version
Broken: 2.79.4
Worked: 2.79b

Short description of error
I can't login and open Blender Cloud Repository with daily builds.

Exact steps for others to reproduce the error
I can reproduce it with today build (31f2a6755db) too.
Factory setting.

Behaviour is like this:
2.79.4 (daily build 31f2a6755db) I can't login.
2.79b (official) I can and I can also access repository

than if I'm logged in with official 2.79b
2.79.4 I see I'm logged
2.79.4 I can't still access cloud repository

Thank you for help

I had already discussion with Sybren, he asked me to run this commands (see screen).
After that he direct me to post it here.
(Left side official 2.79b / Right side daily 2.79.3 in that time)



Event Timeline

On my macOS local build, this is working. Might be that buildbot isn't working as it should. svn problem or something like that. @Sergey Sharybin (sergey) ? Or anyone who has access to mac buildbot.

@Arto Kitula (akitula), can you reproduce the issue with buildbot builds on your machine?

@Sergey Sharybin (sergey) Actually just now realized that this happens because of the application translocator, the very reason we give releases on signed DMG.

@filip mond (vklidu) Could you try to start blender from Terminal ?

Buildbot should also be making signed dmg files I think, really the only difference with release builds should be the revision it's built from.

@Arto Kitula (akitula), do you think it will be smart idea and possible to sign buildbot binaries? Last time i've tried to sign in a headless mode, codesign gave me error code 0xffffffff...

@Sergey Sharybin (sergey) It is possible. I've got script that works, just needs some caring to do neat dmg. I'll push it when ready (next week latest).

Philipp Oeser (lichtwerk) lowered the priority of this task from Needs Triage by Developer to Confirmed, Medium.

@Arto Kitula (akitula) , assigning to you then?

filip mond (vklidu) added a comment.EditedApr 4 2018, 2:33 PM

@Arto Kitula (akitula) If you mentioned "translocation" issue - Do you mean "double docking" issue? Because I already moved blender out and in a directory, to "fix" that with mentioned build. But SSL error appeared before and after (double docking) anyway.

Running from Terminal - here is the output

if it helps in some way.
I also moved out all user files to run clear Blender and downloaded Blender Cloud addon to get all fresh :)

@Philipp Oeser (lichtwerk) yeah, that's ok.

@filip mond (vklidu) Yeah so this is not because of application translocation. Wondering why ssl module is not found. When I downloaded latest build from buildbot, it works.

What does following code give you?

import site

That's just as it should. If you go that folder, does it have ?

filip mond (vklidu) added a comment.EditedApr 5 2018, 10:12 AM

In folder "site-packages" is only ""
Filtering with blender's file browser displayed only this file containing SSL.


Here is what inside "site-packages" folder

But "" is in level up in "python3.6" folder as you can see on screen too.
That's probably you asked for, right?

Arto Kitula (akitula) lowered the priority of this task from Confirmed, Medium to Needs Information from User.Apr 5 2018, 10:39 AM

Oops, that one level up is correct. Could you start the build with all debugging options on. And then just hit import ssl to python console and post the whole debug output.
Marking this as incomplete for now.

Thanks for reliance :) but what the hell is "start the build with all debugging options on"? :) Sorry, simple designer on this side of cable.
I would like to help you, but be a bit more descriptive for me, thank you. I will try my best.

No pressure =)
Let's do also factory startup so your preferences and some addons aren't affecting this:

./ --factory-startup --debug-python

That is just for debugging python, --debug-all includes all debug messages. Let's start with --debug-python for now.

Here it is, just a note when I started now from terminal I was still logged in (by official 2.79b version) and I tried to open cloud from image editor, or should I log out first?

What if you move directory /Users/filip/Library/Application Support/Blender/2.79/ away and start blender again, and install the latest cloud addon?

filip mond (vklidu) added a comment.EditedApr 5 2018, 6:01 PM

That's exactly what I did yesterday.

  • downloaded daily build
  • moved whole folder 2.79 from Application Support
  • downloaded addon available from cloud, installed

Same error.

Should I do it again for you to get generated console output?

Philipp Oeser (lichtwerk) raised the priority of this task from Needs Information from User to Needs Triage by Developer.Jun 20 2018, 4:13 PM

We have a report (T56329) with the same issue in the Benchmark Client, so it's not just buildbot-builds.

This will be fixed now in the latest daily builds after rBcd5db907261e: Build Environment: updates for macOS..