[GH-ISSUE #94] Uploading fails on IPv6 hosts #72

New issue

Closed

opened 2026-02-25 20:32:29 +03:00 by kerem · 4 comments

kerem commented

2026-02-25 20:32:29 +03:00

Owner

Originally created by @WhyNotHugo on GitHub (May 1, 2015).
Original GitHub issue: https://github.com/asciinema/asciinema/issues/94

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

~ Upload failed, asciicast saved at /tmp/asciicast-447814332
~ Retry later by executing: asciinema upload /tmp/asciicast-447814332
Error: Connection failed (Post https://asciinema.org/api/asciicasts: dial tcp 109.107.38.78:443: network is unreachable)

The error message makes me assume that you're assuming that there's native IPv4 connectivity. This assumption is mistaken.

Note: The is a client assumption error, not a network error.

Originally created by @WhyNotHugo on GitHub (May 1, 2015). Original GitHub issue: https://github.com/asciinema/asciinema/issues/94 ``` ~ Asciicast recording finished. ~ Press <Enter> to upload, <Ctrl-C> to cancel. ~ Upload failed, asciicast saved at /tmp/asciicast-447814332 ~ Retry later by executing: asciinema upload /tmp/asciicast-447814332 Error: Connection failed (Post https://asciinema.org/api/asciicasts: dial tcp 109.107.38.78:443: network is unreachable) ``` The error message makes me assume that you're assuming that there's native IPv4 connectivity. This assumption is mistaken. Note: The is a client assumption error, not a network error.

kerem

2026-02-25 20:32:29 +03:00

closed this issue
added the
bug
label

kerem commented

2026-02-25 20:32:29 +03:00

Author

Owner

@ku1ik commented on GitHub (May 3, 2015):

This is interesting. Do you still get this error?

There's no explicit use of IPv4 in the code anywhere. I'll check if there is a default in Go's stdlib somewhere for it, maybe that's Go's DNS resolver.

@ku1ik commented on GitHub (May 3, 2015): This is interesting. Do you still get this error? There's no explicit use of IPv4 in the code anywhere. I'll check if there is a default in Go's stdlib somewhere for it, maybe that's Go's DNS resolver.

kerem commented

2026-02-25 20:32:29 +03:00

Author

Owner

@WhyNotHugo commented on GitHub (Jun 27, 2015):

I could have sworn I'd replied to this pretty fast. My bad.

Any how, I had not noticed this used go at the time of my report. Indeed, go's stdlib isn't really IPv6-ready (hence why I've always said it's not really production-ready for networking apps).

So yeah, asciinema won't work reliably until golang fixes those issues, regrettably.

@WhyNotHugo commented on GitHub (Jun 27, 2015): I could have sworn I'd replied to this pretty fast. My bad. Any how, I had not noticed this used go at the time of my report. Indeed, go's stdlib isn't really IPv6-ready (hence why I've always said it's not really production-ready for networking apps). So yeah, asciinema won't work reliably until golang fixes those issues, regrettably.

kerem commented

2026-02-25 20:32:29 +03:00

Author

Owner

@ku1ik commented on GitHub (Jun 27, 2015):

Ok then, I'm leaving it open for now. Thx for the report.

@ku1ik commented on GitHub (Jun 27, 2015): Ok then, I'm leaving it open for now. Thx for the report.

kerem commented

2026-02-25 20:32:29 +03:00

Author

Owner

@ku1ik commented on GitHub (Jul 13, 2016):

@hobarrera I just released v1.3.0 which should solve this issue (as it's implemented in Python). Can you check it out? sudo pip3 install asciinema.

@ku1ik commented on GitHub (Jul 13, 2016): @hobarrera I just released v1.3.0 which should solve this issue (as it's implemented in Python). Can you check it out? `sudo pip3 install asciinema`.

kerem referenced this issue

2026-03-15 08:47:37 +03:00

[GH-ISSUE #72] asciinema enables XON/XOFF flow control and does not reset it #671