bbolli / tumblr-utils

Utilities for dealing with Tumblr blogs, Tumblr backup
GNU General Public License v3.0
668 stars 124 forks source link

SSL certificate verification fails (CERTIFICATE_VERIFY_FAILED) #225

Open overdue82 opened 3 years ago

overdue82 commented 3 years ago

I'm trying to do a backup of all files and media on my tumblr and my likes, but keep getting <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed <_ssl.c:590>>

I already allowed the program in API application settings and copied the API Key to the tumblr_backup.py but now the problem above persists. Unless I filled something out on the application wrong? I didn't know what to put for the urls so I used mine tumblr url. This is how I filled out the API application.

bbolli commented 3 years ago

Try with option -S, please.

bbolli commented 3 years ago

If you're on macOS, see #226.

cebtenzzre commented 3 years ago

This is a related but different issue: Some builds of Python 2 don't support SNI (Server Name Indication) and will sometimes complain about certificate verification errors. There are three ways to work around this:

overdue82 commented 3 years ago

Just a heads up. I'm on Windows and the problem resolved itself after I updated Python. I must've been using an old version and for whatever reason it was giving me verification errors. I don't know but it resolved after I updated.

Also using -S never worked with the tag "tumblr_backup.py username -S" or so I read on another similar thread. I tried that before updating and it give me an unknown error because it didn't recognize "-S". Unless I was doing that wrong. I don't know but like I said it resolved after the update. I'm only replying now because I kept getting email notifications.

bbolli commented 3 years ago

Also using -S never worked with the tag "tumblr_backup.py username -S"

Options generally go before the non-options, so the command should have been tumblr_backup.py -S username.

cebtenzzre commented 3 years ago

I'm reopening this issue so it can be tracked separately. Certificate verification errors are tracked here, TLS protocol version errors are tracked in #226.