Page MenuHome

Blender Cloud addon fails to authenticate via HTTPS
Closed, ArchivedPublic


System Information
Mac osx 10.11.6

Blender Version
Broken: 2.78 f74b4a0
Worked: (optional)

Blender ID does not connect to authenticate: Cannot connect to HTTPS URL because the SSL module is not available

Exact steps for others to reproduce the error
Installed Blender Cloud addon but could not access internet via Blender ID addon. I could use the addon window to open this page however.



Event Timeline

Aaron Carlisle (Blendify) lowered the priority of this task from Needs Triage by Developer to Normal.

Does 2.78c work?

Please provide more information. Where did you get this build of Blender? Can you start Blender from a terminal and tell us the output that's there?

Sorry I'm not near my MAC laptop now. I think that it was from Blender build bot. I will have to check back in a couple hours.

Just downloaded latest 64bit Mac OS 2.78 from build bot. Same fail. Hash: 20c9c1b44e
Is there a difference between libs from build bot and official release?

Also what terminal output do you need? I ran Blender from Mac Terminal but didn't see anything reported there.

I don't know anything about Apple, so I don't know what "Mac Terminal" is. Also, please answer @Aaron Carlisle (Blendify)'s question, as it'll help us find the issue.
The libraries can be different between buildbot and official release, because buildbot gets updates before releases get them.

Can confirm that it works in 2.78c

Fails in latest build bot.

Hey there @david mcsween (davidmcsween) could you share a screenshot or video of what happens with the add-on? You can attach it here in the thread.

Hey guys, having the same issue here in 2.78.5

@Colin Levy (effstops) which version 2.78.5 exactly? Do you have a build hash / place you downloaded it from?

I just tested on El Capitan (MacOS 10.11.6), and it works fine here. @david mcsween (davidmcsween) and @Colin Levy (effstops) can you give us the requested info, please?

Closing as Archived, since there was no response in a week and we haven't been able to reproduce the issue.

Same problem now with current Mac daily build found on at

This is a duplicate of T56275, so this task can remain archived. There is no need to start re-opening various tasks that all have the same root cause. As a matter of fact, it distracts and requires us to spend more time here typing responses and less time on actually fixing things.