Asciinema: Upload failed

@stayingcool I faced the same issue on El Capitan - 10.11.6 and fixed it by adding the url line to my ~/.config/asciinema/config:

[api]
token = 123123123
url = http://asciinema.org 

@stayingcool which asciinema version and OS are you running?

I'm seeing the same issue on current HEAD (8cdd2579ff2b192eca6df6b3164cabf03461aebe).
I'm getting Error: HTTP status: 500 Internal Server Error from asciinema 1.1.1-56ee754 - the version installed by the install script when I ran that.

I get a successful upload when using 0.9.8 which is what apt-get installed, but that doesn't allow me to upload already recorded files, or set the screen width to an appropriate size with tmux.

Distro:

vagrant@devbox:~$ cat /etc/*release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=16.04
DISTRIB_CODENAME=xenial
DISTRIB_DESCRIPTION="Ubuntu 16.04.2 LTS"
NAME="Ubuntu"
VERSION="16.04.2 LTS (Xenial Xerus)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 16.04.2 LTS"
VERSION_ID="16.04"
HOME_URL="http://www.ubuntu.com/"
SUPPORT_URL="http://help.ubuntu.com/"
BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/"
VERSION_CODENAME=xenial
UBUNTU_CODENAME=xenial

I've tried explicitly adding the url entry to the ~/.asciinema/config file as suggested by @boris but it had no observable effect (tried this with HEAD).

@boris @stayingcool that's a temporary workaround for client certificate issue, but we'll soon turn off http:// so we should look for the cause of CERTIFICATE_VERIFY_FAILED - I suspect some homebrew dependency issue wrt libopenssl or something similar.

@hickeng was the recording which fails produced by yet unreleased asciinema version? (develop branch)?

@sickill yes, it was recorded with develop.

@hickeng ok, that's because develop produces version 2 asciicasts, and the instance at asciinema.org hasn't yet been updated to handle that. I'm going to fix that in the coming days.

@stayingcool I had the same issue with OSX Sierra 10.12.6 (16G29)

~ Upload failed: <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:777)>

and fixed it by editing ~/.config/asciinema/config as advised by @boris (thanks !! :)
asciinema installed was performed directly using pip3:

$ pip3 install asciinema
Collecting asciinema
Downloading asciinema-1.4.0.tar.gz
... (snip'd)

I also installed 1.4.0 using pip3 on OS X I mentioned above. Sadly (to replicate this issue, but luckily to me) I'm not using OS X anymore and asciinema works pretty well in Linux :)

@stayingcool @stefb12 if you have installed Python via official dmg installer then you need to install root certificates by running this command:

/Applications/Python\ 3.*/Install\ Certificates.command

Paste this into your terminal or locate and open in Finder.

(found this info here: https://stackoverflow.com/questions/42098126/mac-osx-python-ssl-sslerror-ssl-certificate-verify-failed-certificate-verify)

thanks for the information @sickill !

@stayingcool has the above hint helped?

Hi, I'm having the same issue.
I'm on MacOS High Sierra 10.13.3 using asciinema 1.4.0.

The message I see is:

~ Upload failed: <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:864)>
~ Retry later by running: asciinema upload /var/folders/xg/b8lym1jx549c9q1qc8cf7b0c0000gn/T/tmp8yro_585-asciinema.json

I tried running the suggested command above:

$/Applications/Python\ 3.*/Install\ Certificates.command

 -- pip install --upgrade certifi
Collecting certifi
  Using cached certifi-2018.1.18-py2.py3-none-any.whl
Installing collected packages: certifi
Successfully installed certifi-2018.1.18
 -- removing any existing file or link
 -- creating symlink to certifi certificate bundle
 -- setting permissions
 -- update complete

Upload still failed.

Ah nevermind, I had to update the url in ~/.config/asciinema/config to http.
The upload works after I did that.
But feels like it should work over https?
Anyways, thanks!!

can someone tell me what exactly the ~/.config/asciinema/config file has inside ?

@bllyz in the docs: https://asciinema.org/docs/config

I'm still broken on the pipe though