SSL link check fails, while curl succeeds #376

ilg-ul · 2017-02-04T15:39:08Z

I'm getting the following error when running html-proofer in a Travis job:

- /home/travis/out/gnuarmeclipse/gnuarmeclipse.github.io/qemu/build-procedure/index.html
  *  External link https://developer.apple.com/xcode/downloads/ failed: 302 SSL connect error
- /home/travis/out/gnuarmeclipse/gnuarmeclipse.github.io/windows-build-tools/build-procedure/index.html
  *  External link http://developer.apple.com/xcode/downloads/ failed: 302 SSL connect error
htmlproofer 3.4.0 | Error:  HTML-Proofer found 2 failures!

However, in exactly the same environment, a curl to that address was ok:

$  curl -L --url http://developer.apple.com/xcode/downloads/ --verbose
* Hostname was NOT found in DNS cache
*   Trying 17.146.1.14...
* Connected to developer.apple.com (17.146.1.14) port 80 (#0)
> GET /xcode/downloads/ HTTP/1.1
> User-Agent: curl/7.35.0
> Host: developer.apple.com
> Accept: */*
> 
< HTTP/1.1 301 Moved Permanently
< Date: Sat, 04 Feb 2017 14:43:25 GMT
< Content-Type: text/html
< Content-Length: 179
< Connection: keep-alive
< Location: https://developer.apple.com/xcode/downloads/
* Server Shield is not blacklisted
...
< 
* Ignoring the response-body
* Connection #1 to host developer.apple.com left intact
* Issue another request to this URL: 'https://idmsa.apple.com/IDMSWebAuth/login?appIdKey=891bd3417a7776362562d2197f89480a8547b108fd934911bcbea0110d07f757&path=%2Fdownload%2F&rv=1'
* Hostname was NOT found in DNS cache
*   Trying 17.171.11.86...
* Connected to idmsa.apple.com (17.171.11.86) port 443 (#2)
* successfully set certificate verify locations:
*   CAfile: none
  CApath: /etc/ssl/certs
* SSLv3, TLS handshake, Client hello (1):
* SSLv3, TLS handshake, Server hello (2):
* SSLv3, TLS handshake, CERT (11):
* SSLv3, TLS handshake, Server finished (14):
* SSLv3, TLS handshake, Client key exchange (16):
* SSLv3, TLS change cipher, Client hello (1):
* SSLv3, TLS handshake, Finished (20):
* SSLv3, TLS change cipher, Client hello (1):
* SSLv3, TLS handshake, Finished (20):
* SSL connection using AES128-GCM-SHA256
* Server certificate:
* 	 subject: 1.3.6.1.4.1.311.60.2.1.3=US; 1.3.6.1.4.1.311.60.2.1.2=California; businessCategory=Private Organization; serialNumber=C0806592; C=US; postalCode=95014; ST=California; L=Cupertino; street=1 Infinite Loop; O=Apple Inc.; OU=GNCS Traffic Management; CN=idmsa.apple.com
* 	 start date: 2017-01-20 00:00:00 GMT
* 	 expire date: 2019-01-20 23:59:59 GMT
* 	 subjectAltName: idmsa.apple.com matched
* 	 issuer: C=US; O=Symantec Corporation; OU=Symantec Trust Network; CN=Symantec Class 3 EV SSL CA - G3
* 	 SSL certificate verify ok.
> GET /IDMSWebAuth/login?appIdKey=891bd3417a7776362562d2197f89480a8547b108fd934911bcbea0110d07f757&path=%2Fdownload%2F&rv=1 HTTP/1.1
> User-Agent: curl/7.35.0
> Host: idmsa.apple.com
> Accept: */*
> 
< HTTP/1.1 200 OK
< Set-Cookie: JSESSIONID=E374FE13E2A29D92D8B47263B64ACFD7; Path=/; Secure; HttpOnly
< Set-Cookie: dslang=US-EN; Domain=.apple.com; Expires=Thu, 03-Aug-2017 14:43:26 GMT; Path=/; Secure; HttpOnly
< Set-Cookie: dslang=US-EN; Domain=.apple.com; Expires=Thu, 03-Aug-2017 14:43:26 GMT; Path=/; Secure; HttpOnly
< TOTAL_TIME: 105
< DS_TIME: default
< X-FRAME-OPTIONS: DENY
< X-Content-Type-Options: nosniff
< X-XSS-Protection: 1; mode=block
< Strict-Transport-Security: max-age=31536000; includeSubDomains
< Cache-Control: private, no-cache, no-store, must-revalidate, max-age=0, post-check=0, pre-check=0
< Pragma: no-cache
< Expires: Thu, 01 Jan 1970 00:00:00 GMT
< Content-Type: text/html;charset=UTF-8
< Content-Language: en-US
< Transfer-Encoding: chunked
< Vary: Accept-Encoding
< Date: Sat, 04 Feb 2017 14:43:26 GMT
* Server APPSRV is not blacklisted
< Server: APPSRV
< Set-Cookie: X-SESS=28d4a3da9fb70633345a49ca2d42db4197df95593ba62c62d7c0d5cc6198624c97df0a3f;Version=1;Max-Age=1800;path=/;secure;httponly
< 
<!DOCTYPE html>
...

The entire log is available at:
https://travis-ci.org/gnuarmeclipse/gnuarmeclipse.github.io-source/builds/198333357

For the moment I added the offending URLs to the --url-ignore list, but perhaps there is something you can do to accept these URLs too.

Any thoughts?

The text was updated successfully, but these errors were encountered:

ilg-ul · 2017-02-05T18:49:35Z

I have three new more URLs that fail the test, but return 200 with curl:

  *  External link https://www.element14.com/community/groups/gnu-arm-eclipse failed: 503 No error
  *  External link https://www.element14.com/community/welcome failed: 503 No error
  *  External link https://www.element14.com/community/discussion/create.jspa?containerID=2436&containerType=700 failed: 503 No error

ilg-ul · 2017-02-06T11:42:20Z

Some more, reported by Travis:

  *  External link https://jekyllrb.com/ failed: response code 0 means something's wrong.
             It's possible libcurl couldn't connect to the server or perhaps the request timed out.
             Sometimes, making too many requests at once also breaks things.
             Either way, the return message (if any) from the server is: SSL connect error
...
  *  External link http://kramdown.gettalong.org/syntax.html failed: 503 No error

The workaround was to add https://jekyllrb.com,http://kramdown.gettalong.org/syntax.html to the list of exclusions.

ilg-ul · 2017-02-15T06:33:35Z

anybody home?

gjtorikian · 2017-02-15T22:58:13Z

However, in exactly the same environment, a curl to that address was ok

Well, that's part of the rub: was that curl command run on the Travis box itself?

This issue has come up before: #141

And it seems like passing { :ssl_verifyhost => 0} to the :typhoeus options works. Could you try that?

ilg-ul · 2017-02-15T23:03:34Z

was that curl command run on the Travis box itself?

yes, I provided the link to the Travis log

{ :ssl_verifyhost => 0} Could you try that?

sorry, my knowledge of :typhoeus is limited, can you provide more details on how to do this from a script shell?

gjtorikian · 2017-02-15T23:26:11Z

can you provide more details on how to do this from a script shell?

Sure! Generally it looks like this in Ruby:

HTMLProofer.check_directory("out/", {
  :typhoeus => {
    :ssl_verifypeer => false,
    :ssl_verifyhost => 0}
}).run

I'm embarrassed to say that there doesn't seem to be a way to set Typheous options through the command-line. 😞 I'll open an issue for that.

ilg-ul · 2017-02-15T23:33:05Z

I'm currently taking a look at Ruby syntax, but I'm not sure I'll be able to update my travis scripts to replace bash commands with Ruby scripts, so I might wait for the new version that uses command line options.

mattclegg · 2017-03-06T17:50:36Z

Try adding to your travis.yml;

sudo: required
before_install:
  - sudo update-ca-certificates

The default CAs shipped with Ubuntu 12.04 are somewhat out of date now. Running update-ca-certificates will get the latest certs (but you need sudo to run it).

ilg-ul · 2017-03-06T18:11:05Z

as the title states, in exactly the same environment, curl was able to access the links; do you think that curl uses a newer list of certificates than the list updated by update-ca-certificates?

mattclegg · 2017-03-06T18:39:10Z

This should fix the problem where you get "response code 0" ie on; https://jekyllrb.com/.

Regarding the issue you opened the ticket with; The request to http://developer.apple.com/xcode/downloads/ is being redirected and html-proofer is returning an error because it looks like it doesn't seem to handle 302 requests. All the linkWithRedirect tests are either 301 or 200.

fulldecent · 2017-05-18T14:14:30Z

I see several actionable items in this issue:

The error message for "External link xxx failed: 302 SSL connect error" should be improved to include detail on the SSL error or simply state "... consider updating your CA certificates"
Allow Typheous options from the command line Allow Typheous options to be set from bin/command line #379 (checked off because we have another issue open)
Make dead-simple Ruby and Travis examples of how to customize Typheous behavior, see https://github.com/gjtorikian/html-proofer/wiki/How-to-configure-Typhoeus
Reduce complexity of README.md and link to that Typhoeus wiki page for people that want to customize
Report upstream to Typhoeus that they are failing to make a SSL connection where curl succeeds Typhoeus fails to make SSL connection on host where curl success typhoeus/typhoeus#568

Installing libcurl3-dev seems to fix SSL error HTML Proofer gets when trying to get https://mochajs.org/ . See gjtorikian/html-proofer#141 gjtorikian/html-proofer#194 gjtorikian/html-proofer#376

Give the entire rug test doc the once-over, integrating the content on handler testing and adding as much missing stuff as I could think of. Install libcurl3-dev to fix HTML Proofer SSL error when it tests https://mochajs.org/ see gjtorikian/html-proofer#141 gjtorikian/html-proofer#194 gjtorikian/html-proofer#376 Add retry to HTML Proofer. Address review comments.

see if this fixes response code 0 errors gjtorikian/html-proofer#376

mvasin · 2017-08-27T14:25:08Z

Here's the error I get:

  *  External link https://talk.jekyllrb.com failed: response code 0 means something's wrong.
             It's possible libcurl couldn't connect to the server or perhaps the request timed out.
             Sometimes, making too many requests at once also breaks things.
             Either way, the return message (if any) from the server is: SSL connect error

I've tried sudo update-ca-certificates, but it didn't work: https://travis-ci.org/cloud-tv/cloud-tv.github.io/builds/268911228

There is no error on CircleCI and on my local machine. Maybe the solution is just to abandon Travis in favour of CircleCI.

Floppy · 2017-08-28T21:34:49Z

On the issue of getting SSL failures on travis specifically, I'm working on https://github.com/Floppy/jekyll-test which plans to automate all the required setup to make it work reliably, once I've found out how :)

gjtorikian · 2017-08-29T23:54:59Z

That's a really great idea @Floppy. Wonder if I can convince @parkr to pull it in as an optional gem once it's completed. 🙂

mizzao · 2017-09-11T17:01:19Z

Also getting this error on Travis:

  *  External link https://summit.scienceathome.org failed: response code 0 means something's wrong.
             It's possible libcurl couldn't connect to the server or perhaps the request timed out.
             Sometimes, making too many requests at once also breaks things.
             Either way, the return message (if any) from the server is: SSL connect error

Re-running the build on Travis CI consistently generates this error. It doesn't occur locally (e.g. bundle exec rake test). Any tips for how I can track down the cause? I'm using the following options at the moment (which have cleared up many other connect errors) so it's not due to certificate issues. I've also tried the sudo update-ca-certificates which doesn't do anything on Trusty.

  options = {
    :allow_hash_href => true,       # don't break on <a href="#">
    :assume_extension => false,     # (true) for extensionless paths
    :http_status_ignore => [ 999 ], # LinkedIn throttling errors
    :typhoeus => {
      # avoid strange SSL errors: https://github.com/gjtorikian/html-proofer/issues/376
      :ssl_verifypeer => false,
      :ssl_verifyhost => 0
    }
  }
  HTMLProofer.check_directory("./_site", options).run

JasonYao · 2017-09-24T08:50:25Z

Running into the same issue here with the error-code 0:

I can pass my tests fine on my local machine
Running curl inside the travis environment prints a correct response code (200) to the same external site
Running the exact same tests inside the travis environment returns a response code of 0
Updating the certs via sudo update-ca-certificates completes successfully and does nothing (and really should do nothing since we're talking about the same environment here)
Not sure why the guys upstream at typhoeus are saying that we need libcurl with openssl compiled in, since we've already shown that curl (which depends on libcurl) can perfectly hit the exact same external sites (HTTP and HTTPS) just fine.

Travis information

Running Ubuntu 14.04 'Trusty'
Link to error log here

Any other information I can provide to help make this easier to debug? Or would this be more of an issue for typhoeus to deal with?

gjtorikian · 2017-09-27T20:51:28Z

I wonder if anyone would try Travis' instructions for Troubleshooting Locally in a Docker Image?

ilg-ul · 2017-09-27T21:01:17Z

Personally I gave up, I added --only-4xx to my Travis scripts.

From time to time I run a manual build on my machine with the full check.

Floppy · 2017-09-27T21:41:56Z

@gjtorikian that's a brilliant idea, I forgot you could do that. I'm downloading the docker images now and will give it a go with https://github.com/SomethingNewUK/redirector which fails on a very regular basis :)

EDIT: yes, I've now got it replicated locally. html-proofer fails, but curl succeeds. I can investigate more but it's bedtime now. 😴

Floppy · 2017-09-28T07:54:24Z

OK, in my travis trusty environment, I'm running:

HTMLProofer.check_directory("./_site",
    typhoeus: {ssl_verifyhost: 0, ssl_verifypeer: false, timeout: 30},
    check_html: true,
    assume_extension: ".html").run

I've also run sudo update-ca-certificates.

Currently I'm still failing with response code 0 in a number of cases, so those aren't the fix. Still looking... :)

Floppy · 2017-09-28T08:02:13Z

Sorry if I'm a bit noisy while I debug.

I decided to drop down to typheous and try directly. So, with a simple GET:

require 'typhoeus'

request = Typhoeus::Request.new(
  ARGV[0],
  method: :get,
  headers: { Accept: "text/html" }
)

request.run

puts request.response.code

...my test link (https://somethingnew.org.uk/news/2017/05/15/ge2017-brexit.html) returns 0. So that's good.

Note that a simple CURL on that url returns a 200 successfully.

Floppy · 2017-09-28T08:34:31Z

AHA! Got it!

Changing the libcurl to use openssl instead of gnutls fixes it. On the travis environment, if I do sudo apt-get install libcurl4-openssl-dev, it removes the gnutls version, then all the links work with 200 responses.

I've reported this upstream to typhoeus in the linked issue, but we can resolve it here with some instructions and suggested travis config. I'll work out how to get travis to do that itself and report back.

ilg-ul · 2017-09-29T11:57:03Z

ok, thank you.

gjtorikian · 2017-09-29T15:24:43Z

Keeping this open just so I remember to find a way to convey this fix as in my comment above.

ilg-ul · 2017-09-29T15:55:55Z

Yes @gjtorikian, you could also add a section explaining how to run the proofer via a Rakefile. Assume no Ruby knowledge.

mizzao · 2017-10-02T15:47:45Z

libcurl4-openssl-dev fixed it for me too. For reference, here's my Rakefile for a Jekyll site, including the Typhoeus stuff:

https://github.com/mizzao/andrewmao.net/blob/master/Rakefile

ilg-ul · 2017-10-02T16:18:44Z

great! something like this, together with examples how to invoke it, would be useful in the README.

errors like #539 (comment) possible fix found at gjtorikian/html-proofer#376 (comment)

gjtorikian · 2017-10-07T21:26:33Z

@Floppy did an amazing job documenting the fix in the wiki, so I just provided links in the README to that document.

closes #376

After updating all the spaconference.org links to use https, we're still getting errors in the build, for example: * External link https://[secure]rence.org/spa2017 failed: response code 0 * means something's wrong. It's possible libcurl couldn't connect to the server or perhaps the request timed out. Sometimes, making too many requests at once also breaks things. Either way, the return message (if any) from the server is: SSL connect error This fix is recommended on the [htmlproofer wiki][wiki], following on from gjtorikian/html-proofer#376. [wiki]: https://github.com/gjtorikian/html-proofer/wiki/Using-HTMLProofer-From-Ruby-and-Travis

We've moved the site to HTTPS today and now the build is failing, for example: * External link http://[secure]rence.org/spa2016 failed: 301 SSL connect error This fix is recommended on the htmlproofer wiki [1], following on from gjtorikian/html-proofer#376. [1]: https://github.com/gjtorikian/html-proofer/wiki/Using-HTMLProofer-From-Ruby-and-Travis

gjtorikian/html-proofer#376

* Use more modern APT installation on Travis not requiring `sudo` * Install `libcurl4-openssl-dev` to prevent HTMLProofer OpenSSL issues (gjtorikian/html-proofer#376) * Use custom HTMLProofer to allow specifying a sensible `timeout` option (the `htmlproofer` command-line does not support options)

Trying solution: gjtorikian/html-proofer#376 (comment)

Solution: gjtorikian/html-proofer#376 (comment) Tried: gjtorikian/html-proofer#376 (comment)

Solution: gjtorikian/html-proofer#376 (comment)

* Fix SSL issues in TravisCI: gjtorikian/html-proofer#376 (comment) * Update html-proofer version * Update Rakefile options used for html-proofer * Fix pagination linking failure

See gjtorikian/html-proofer#376.

Fix from gjtorikian/html-proofer#376

m-reuter · 2020-04-21T20:43:25Z

I still struggle with this. I don't want to include a rake file, it should work directly from travis with --typhoeus_config string but I can not figure out how. Here is my line:
script: bundle exec jekyll build && bundle exec htmlproofer ./_site --check_html --typhoeus_config ''{ "timeout": 30 , "verbose": "true" }''
also tried with three single-quotes and with escaping the curly brackets etc, nothing works and travis won't even start building. Can someone post an example how to pass this in a .travis.yml file? Thanks.

gjtorikian · 2020-04-22T16:53:36Z

Are you able to provide the Travis log? I just tried locally and --typhoeus_config '{ "timeout": 30 , "verbose": "true" }' definitely works.

It may be a Travis CI problem.

m-reuter · 2020-04-22T18:02:03Z

Thanks, yes, it is a parsing problem of the travis file, which is why travis does not even start (so there is no log). I found out that removing the space after the ":" works:

script: bundle exec jekyll build && bundle exec htmlproofer ./_site --check_html --typhoeus_config '{ "timeout":30 }'

Then travis runs and calls the htmlproofer. I still get several:

External link <!deleted!> failed: response code 0 means something's wrong.
It's possible libcurl couldn't connect to the server or perhaps the request timed out.
Sometimes, making too many requests at once also breaks things.
Either way, the return message (if any) from the server is: Server returned nothing (no headers, no data)

And it definitely does not wait 30 sec (command finishes in 5 sec). So either it does not take the timeout , or does not wait for some other reason. Passing additionally the verbose: true did have an effect.

leelee35 · 2020-06-07T08:43:11Z

I have three new more URLs that fail the test, but return 200 with curl:

  *  External link https://www.element14.com/community/groups/gnu-arm-eclipse failed: 503 No error
  *  External link https://www.element14.com/community/welcome failed: 503 No error
  *  External link https://www.element14.com/community/discussion/create.jspa?containerID=2436&containerType=700 failed: 503 No error

fulldecent · 2021-04-27T16:31:02Z

I have carried this habit from using Travis.

Not sure if this is still necessary with GitHub Actions on ubuntu-latest.

fulldecent mentioned this issue May 18, 2017

Typhoeus fails to make SSL connection on host where curl success typhoeus/typhoeus#568

Open

lwasser pushed a commit to earthlab/earthlab.github.io that referenced this issue Aug 17, 2017

ssl issues

8e9d019

see if this fixes response code 0 errors gjtorikian/html-proofer#376

willdurand mentioned this issue Sep 1, 2017

To fix HTMLProofer galaxyproject/training-material#493

Merged

secondsun mentioned this issue Sep 7, 2017

Update raincatcher documentation feedhenry/feedhenry.github.io#18

Merged

aelred mentioned this issue Sep 21, 2017

Add rake test command to check links in docs typedb/typedb#2106

Merged

jasonrudolph mentioned this issue Sep 21, 2017

Fix Travis CI failures related to SSL certificate issues atom/flight-manual.atom.io#376

Merged

gjtorikian reopened this Sep 29, 2017

mlinksva added a commit to github/choosealicense.com that referenced this issue Oct 4, 2017

libcurl4-openssl-dev to maybe avoid SSL errors in tests?

b1baa06

errors like #539 (comment) possible fix found at gjtorikian/html-proofer#376 (comment)

mlinksva mentioned this issue Oct 4, 2017

libcurl4-openssl-dev to maybe avoid SSL errors in tests? github/choosealicense.com#540

Merged

gjtorikian closed this as completed in 705f367 Oct 7, 2017

gjtorikian added a commit that referenced this issue Oct 7, 2017

Add wiki links to the readme

371560b

closes #376

Tiryoh added a commit to tofuconf/tofuconf.club that referenced this issue Feb 1, 2018

Fix SSL connect error on travis

97dd059

gjtorikian/html-proofer#376

hiimbex mentioned this issue Apr 14, 2018

Several fixes to make the tests pass probot/probot.github.io#152

Merged

urda added a commit to urda/website that referenced this issue May 21, 2018

Bump travis version and bundle upate. (...)

1513576

Trying solution: gjtorikian/html-proofer#376 (comment)

urda added a commit to urda/website that referenced this issue May 21, 2018

Bump travis version and bundle upate. (...)

c3a2d92

Solution: gjtorikian/html-proofer#376 (comment) Tried: gjtorikian/html-proofer#376 (comment)

urda added a commit to urda/website that referenced this issue May 21, 2018

Install libcurl4-openssl-dev solution via gjtorikian/html-proofer#376

d5a4a0a

Solution: gjtorikian/html-proofer#376 (comment)

fabiendv mentioned this issue Feb 13, 2019

Show return message for status code 0 #322

Merged

yous added a commit to yous/yous.be that referenced this issue May 3, 2019

Add libcurl4-openssl-dev for html-proofer

288dc5d

See gjtorikian/html-proofer#376.

ppannuto added a commit to tock/tock-www that referenced this issue Jul 12, 2019

update travis ssl libraries

80755e8

Fix from gjtorikian/html-proofer#376

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

SSL link check fails, while curl succeeds #376

SSL link check fails, while curl succeeds #376

ilg-ul commented Feb 4, 2017

ilg-ul commented Feb 5, 2017

ilg-ul commented Feb 6, 2017

ilg-ul commented Feb 15, 2017

gjtorikian commented Feb 15, 2017

ilg-ul commented Feb 15, 2017

gjtorikian commented Feb 15, 2017

ilg-ul commented Feb 15, 2017

mattclegg commented Mar 6, 2017

ilg-ul commented Mar 6, 2017

mattclegg commented Mar 6, 2017

fulldecent commented May 18, 2017 •

edited

Loading

mvasin commented Aug 27, 2017 •

edited

Loading

Floppy commented Aug 28, 2017

gjtorikian commented Aug 29, 2017

mizzao commented Sep 11, 2017 •

edited

Loading

JasonYao commented Sep 24, 2017

gjtorikian commented Sep 27, 2017

ilg-ul commented Sep 27, 2017

Floppy commented Sep 27, 2017 •

edited

Loading

Floppy commented Sep 28, 2017

Floppy commented Sep 28, 2017 •

edited

Loading

Floppy commented Sep 28, 2017 •

edited

Loading

ilg-ul commented Sep 29, 2017

gjtorikian commented Sep 29, 2017

ilg-ul commented Sep 29, 2017

mizzao commented Oct 2, 2017 •

edited

Loading

ilg-ul commented Oct 2, 2017

gjtorikian commented Oct 7, 2017

m-reuter commented Apr 21, 2020

gjtorikian commented Apr 22, 2020 •

edited

Loading

m-reuter commented Apr 22, 2020

leelee35 commented Jun 7, 2020

fulldecent commented Apr 27, 2021

SSL link check fails, while curl succeeds #376

SSL link check fails, while curl succeeds #376

Comments

ilg-ul commented Feb 4, 2017

ilg-ul commented Feb 5, 2017

ilg-ul commented Feb 6, 2017

ilg-ul commented Feb 15, 2017

gjtorikian commented Feb 15, 2017

ilg-ul commented Feb 15, 2017

gjtorikian commented Feb 15, 2017

ilg-ul commented Feb 15, 2017

mattclegg commented Mar 6, 2017

ilg-ul commented Mar 6, 2017

mattclegg commented Mar 6, 2017

fulldecent commented May 18, 2017 • edited Loading

mvasin commented Aug 27, 2017 • edited Loading

Floppy commented Aug 28, 2017

gjtorikian commented Aug 29, 2017

mizzao commented Sep 11, 2017 • edited Loading

JasonYao commented Sep 24, 2017

Travis information

gjtorikian commented Sep 27, 2017

ilg-ul commented Sep 27, 2017

Floppy commented Sep 27, 2017 • edited Loading

Floppy commented Sep 28, 2017

Floppy commented Sep 28, 2017 • edited Loading

Floppy commented Sep 28, 2017 • edited Loading

ilg-ul commented Sep 29, 2017

gjtorikian commented Sep 29, 2017

ilg-ul commented Sep 29, 2017

mizzao commented Oct 2, 2017 • edited Loading

ilg-ul commented Oct 2, 2017

gjtorikian commented Oct 7, 2017

m-reuter commented Apr 21, 2020

gjtorikian commented Apr 22, 2020 • edited Loading

m-reuter commented Apr 22, 2020

leelee35 commented Jun 7, 2020

fulldecent commented Apr 27, 2021

fulldecent commented May 18, 2017 •

edited

Loading

mvasin commented Aug 27, 2017 •

edited

Loading

mizzao commented Sep 11, 2017 •

edited

Loading

Floppy commented Sep 27, 2017 •

edited

Loading

Floppy commented Sep 28, 2017 •

edited

Loading

Floppy commented Sep 28, 2017 •

edited

Loading

mizzao commented Oct 2, 2017 •

edited

Loading

gjtorikian commented Apr 22, 2020 •

edited

Loading