# Julia doc: SSL error and Google still indexing 0.4.8 documentation better than 0.5 (or "latest")

**URL:** <https://discourse.julialang.org/t/julia-doc-ssl-error-and-google-still-indexing-0-4-8-documentation-better-than-0-5-or-latest/2812>\
**Category:** Community\
**Tags:** proposal\
**Created:** [March 22, 2017, 8:35am UTC](https://discourse.julialang.org/t/julia-doc-ssl-error-and-google-still-indexing-0-4-8-documentation-better-than-0-5-or-latest/2812 "2017-03-22T08:35:58Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![sylvaticus](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/sylvaticus/32/203883_2.png) [@sylvaticus](https://discourse.julialang.org/u/sylvaticus)\
**Post date:** [March 22, 2017, 8:35am UTC](https://discourse.julialang.org/t/julia-doc-ssl-error-and-google-still-indexing-0-4-8-documentation-better-than-0-5-or-latest/2812/1 "2017-03-22T08:35:58Z")

</div>

Just a feedback for the website managers: when looking for some Julia documentation in Google, Google still shows up the 0.4.8-pre documentation rather than the latest one, e.g.:

 ![](https://global.discourse-cdn.com/julialang/original/3X/7/1/7179b11301a4ee0f0e0e1de9400cc721e3a52a7c.png)

Is there way to “suggest” Google to point by default to the latest documentation ?

\*\* Got it \*\*… the reason is that 0.4.8 uses [http://docs.julialang.org](http://docs.julialang.org), while 0.5 uses [https://docs.julialang.org](https://docs.julialang.org), but the later one is configured with a certificate for for githug, not julialang:

> [docs.julialang.org](http://docs.julialang.org) uses an invalid security certificate.

> The certificate is only valid for the following names:  
> [www.github.com](http://www.github.com), \*.github.com, [github.com](http://github.com), \*.github.io, [github.io](http://github.io), \*.githubusercontent.com, [githubusercontent.com](http://githubusercontent.com)

> Error code: SSL\_ERROR\_BAD\_CERT\_DOMAIN

Nowadays you can get a free SSL certificate very easily using [Let’s Encrypt](https://letsencrypt.org/).

---

<div class="post-metadata">

**Author:** ![tkoolen](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/tkoolen/32/1603_2.png) [@tkoolen](https://discourse.julialang.org/u/tkoolen)\
**Post date:** [March 22, 2017, 4:28pm UTC](https://discourse.julialang.org/t/julia-doc-ssl-error-and-google-still-indexing-0-4-8-documentation-better-than-0-5-or-latest/2812/2 "2017-03-22T16:28:36Z")

</div>

Thanks for figuring that out; I was wondering why this was the case as well. Maybe open an issue at [Issues · JuliaLang/julia · GitHub](https://github.com/JuliaLang/julia/issues)?

---

<div class="post-metadata">

**Author:** ![yuyichao](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/yuyichao/32/20_2.png) [@yuyichao](https://discourse.julialang.org/u/yuyichao)\
**Post date:** [March 22, 2017, 4:56pm UTC](https://discourse.julialang.org/t/julia-doc-ssl-error-and-google-still-indexing-0-4-8-documentation-better-than-0-5-or-latest/2812/3 "2017-03-22T16:56:01Z")

</div>

This is a known issue and very non-trivial to fix. [https://github.com/JuliaLang/julia/issues/21078](https://github.com/JuliaLang/julia/issues/21078)