[GH-ISSUE #235] Upload failed

kerem commented

2026-03-15 10:23:52 +03:00

Owner

Originally created by @stayingcool on GitHub (Sep 20, 2017).
Original GitHub issue: https://github.com/asciinema/asciinema/issues/235

Upload fails with the following error:

bash-3.2$ exit
exit
~ Asciicast recording finished.
~ Press <Enter> to upload, <Ctrl-C> to cancel.

~ Upload failed: <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:749)>
~ Retry later by running: asciinema upload /var/folders/9g/60yjppb57779f3nrvxzvb_wn5wr3t6/T/tmp3zaagfuf-asciinema.json

My Env:
MacOS Sierra - 10.12.4 (16E195)

I'm able to play the recording, just that the upload fails. Any feedback or clues to fix this issue?

Originally created by @stayingcool on GitHub (Sep 20, 2017). Original GitHub issue: https://github.com/asciinema/asciinema/issues/235 Upload fails with the following error: ``` bash-3.2$ exit exit ~ Asciicast recording finished. ~ Press <Enter> to upload, <Ctrl-C> to cancel. ~ Upload failed: <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:749)> ~ Retry later by running: asciinema upload /var/folders/9g/60yjppb57779f3nrvxzvb_wn5wr3t6/T/tmp3zaagfuf-asciinema.json ``` **My Env:** MacOS Sierra - 10.12.4 (16E195) I'm able to play the recording, just that the upload fails. Any feedback or clues to fix this issue?

kerem closed this issue

2026-03-15 10:23:57 +03:00

kerem commented

2026-03-15 10:24:03 +03:00

Author

Owner

@boris commented on GitHub (Oct 6, 2017):

@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

@boris commented on GitHub (Oct 6, 2017): @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 ```

kerem commented

2026-03-15 10:24:08 +03:00

Author

Owner

@ku1ik commented on GitHub (Oct 8, 2017):

@stayingcool which asciinema version and OS are you running?

@ku1ik commented on GitHub (Oct 8, 2017): @stayingcool which asciinema version and OS are you running?

kerem commented

2026-03-15 10:24:13 +03:00

Author

Owner

@hickeng commented on GitHub (Oct 18, 2017):

I'm seeing the same issue on current HEAD (8cdd2579ff).
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).

@hickeng commented on GitHub (Oct 18, 2017): 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).

kerem commented

2026-03-15 10:24:18 +03:00

Author

Owner

@ku1ik commented on GitHub (Oct 24, 2017):

@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.

@ku1ik commented on GitHub (Oct 24, 2017): @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.

kerem commented

2026-03-15 10:24:23 +03:00

Author

Owner

@ku1ik commented on GitHub (Oct 24, 2017):

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

@ku1ik commented on GitHub (Oct 24, 2017): @hickeng was the recording which fails produced by yet unreleased asciinema version? (`develop` branch)?

kerem commented

2026-03-15 10:24:28 +03:00

Author

Owner

@hickeng commented on GitHub (Oct 24, 2017):

@sickill yes, it was recorded with develop.

@hickeng commented on GitHub (Oct 24, 2017): @sickill yes, it was recorded with `develop`.

kerem commented

2026-03-15 10:24:33 +03:00

Author

Owner

@ku1ik commented on GitHub (Oct 25, 2017):

@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.

@ku1ik commented on GitHub (Oct 25, 2017): @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.

kerem commented

2026-03-15 10:24:38 +03:00

Author

Owner

@StephaneBenfredj commented on GitHub (Oct 27, 2017):

@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)

@StephaneBenfredj commented on GitHub (Oct 27, 2017): @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)

kerem commented

2026-03-15 10:24:43 +03:00

Author

Owner

@boris commented on GitHub (Oct 30, 2017):

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 :)

@boris commented on GitHub (Oct 30, 2017): 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 :)

kerem commented

2026-03-15 10:24:48 +03:00

Author

Owner

@ku1ik commented on GitHub (Nov 28, 2017):

@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)

@ku1ik commented on GitHub (Nov 28, 2017): @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)

kerem commented

2026-03-15 10:24:54 +03:00

Author

Owner

@StephaneBenfredj commented on GitHub (Nov 29, 2017):

thanks for the information @sickill !

@StephaneBenfredj commented on GitHub (Nov 29, 2017): thanks for the information @sickill !

kerem commented

2026-03-15 10:24:59 +03:00

Author

Owner

@ku1ik commented on GitHub (Dec 4, 2017):

@stayingcool has the above hint helped?

@ku1ik commented on GitHub (Dec 4, 2017): @stayingcool has the above hint helped?

kerem commented

2026-03-15 10:25:04 +03:00

Author

Owner

@Mariatta commented on GitHub (Feb 8, 2018):

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.

@Mariatta commented on GitHub (Feb 8, 2018): 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.

kerem commented

2026-03-15 10:25:09 +03:00

Author

Owner

@Mariatta commented on GitHub (Feb 8, 2018):

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!!

@Mariatta commented on GitHub (Feb 8, 2018): 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!!

kerem commented

2026-03-15 10:25:14 +03:00

Author

Owner

@vxsilis commented on GitHub (Oct 19, 2019):

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

@vxsilis commented on GitHub (Oct 19, 2019): can someone tell me what exactly the ~/.config/asciinema/config file has inside ?

kerem commented

2026-03-15 10:25:19 +03:00

Author

Owner

@PlutoniumProphet commented on GitHub (Jan 21, 2020):

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

I'm still broken on the pipe though

@PlutoniumProphet commented on GitHub (Jan 21, 2020): @bllyz in the docs: https://asciinema.org/docs/config I'm still broken on the pipe though

Rows
Columns

[GH-ISSUE #235] Upload failed #781