Skip to content

Current SSL cert is not valid for "rtfd.org" domain #328

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
ncoghlan opened this issue Jan 17, 2013 · 20 comments
Closed

Current SSL cert is not valid for "rtfd.org" domain #328

ncoghlan opened this issue Jan 17, 2013 · 20 comments
Labels
Bug A bug Operations Operations or server issue Status: blocked Issue is blocked on another issue

Comments

@ncoghlan
Copy link

The current SSL cert is only valid for the full readthedocs.org spelling, resulting in a security warning if accessing the short URL over HTTPS. (So, not really a bug in the RTFD code itself, but I'm not sure where else to report site config issues)

@kmike
Copy link

kmike commented Apr 12, 2013

+1. This affects e.g. "Short URLs" section in project page (example: https://readthedocs.org/projects/write-the-docs-2013-notes/ - accessing second "Short URL" issues a security warning).

@nopjmp
Copy link

nopjmp commented May 10, 2015

This still seems to be an issue today. Are there any plans on extending the SSL certificate to *.rtfd.org and rtfd.org?

@ericholscher
Copy link
Member

We mainly don't have them because it's expensive, and the redirect domains
are less valuable than the main domain. If someone wanted to donate/sponsor
more SSL certs, we would happily host them.

On Sun, May 10, 2015 at 11:05 AM, Kyle Thompson [email protected]
wrote:

This still seems to be an issue today. Are there any plans on extending
the SSL certificate to *.rtfd.org and rtfd.org?


Reply to this email directly or view it on GitHub
#328 (comment)
.

Eric Holscher
Maker of the internet residing in Portland, Oregon
http://ericholscher.com

@agjohnson agjohnson added Operations Operations or server issue and removed Admin Only labels Jun 8, 2015
@gregmuellegger gregmuellegger added the Bug A bug label Sep 14, 2015
@anarcat
Copy link

anarcat commented Jan 5, 2016

let's encrypt is now an easy to use and free alternative to the commercial CAs. it should be fairly easy to set that up to fix this bug, but i can't sponsor/donate those without access to the server hosting rtfd.org.

@ericholscher
Copy link
Member

The issue is that we need a wildcard cert, which letsencrypt doesn't
support.

On Tue, Jan 5, 2016 at 9:40 AM, anarcat [email protected] wrote:

let's encrypt is now an easy to use and free alternative to the commercial
CAs. it should be fairly easy to set that up to fix this bug, but i can't
sponsor/donate those without access to the server hosting rtfd.org.


Reply to this email directly or view it on GitHub
#328 (comment)
.

Eric Holscher
Maker of the internet residing in Portland, Oregon
http://ericholscher.com

@anarcat
Copy link

anarcat commented Jan 5, 2016

true that. but since it's automated, you could actually generate one cert per vhost...

@anarcat
Copy link

anarcat commented Jan 5, 2016

in fact, some webservers actually do that on the fly, like caddy

@honzajavorek
Copy link

Also affected by this:

screen shot 2016-03-02 at 18 10 03

@kylef
Copy link

kylef commented Mar 8, 2016

If someone wanted to donate/sponsor more SSL certs, we would happily host them.

Now that Let's Encrypt is a thing, could this be used to cut the costs here?

@agjohnson
Copy link
Contributor

As stated above, let's encrypt does not support wildcard certs, as per certbot/certbot#66.

@mr-c
Copy link

mr-c commented May 4, 2016

I would pay for ssl +custom domain using letsencrypt.

@gwillem
Copy link
Contributor

gwillem commented Nov 18, 2017

@anarcat, the number of subdomains and requests/time that letsencrypt honours is limited and probably not enough for the number of sites hosted on RTD.

@anarcat
Copy link

anarcat commented Nov 18, 2017

@gwillem those are not hard limits - they can be modified as needed if you talk with them. see this comment for example.

how many sites are we talking about anyways?

@humitos
Copy link
Member

humitos commented Nov 19, 2017

@anarcat here you have the stats from last year: http://blog.readthedocs.com/read-the-docs-2016-stats/

@anarcat
Copy link

anarcat commented Nov 19, 2017

definitely above 20 certs/week of course :p you'd have about 200k certs per year, so about 4k per week... but i guess it's something that could be discussed.

now of course, LE will support wildcard certs starting in January 2018, so those numbers would become irrelevant if a wildcard is acceptable: https://letsencrypt.org/2017/07/06/wildcard-certificates-coming-jan-2018.html

@humitos
Copy link
Member

humitos commented Nov 19, 2017

So, it's seems that's a matter of time. I think we should wait until Jan 2018 :D

@tnir
Copy link

tnir commented Feb 27, 2018

FYI: Wildcard support by LE delay: https://community.letsencrypt.org/t/acmev2-and-wildcard-launch-delay/53654

Feb 27 Update: There are no known major issues with the ACMEv2/wildcard test endpoint. ACMEv2 and wildcard support quality assurance is continuing. No release date to announce yet.

@humitos
Copy link
Member

humitos commented Mar 14, 2018

Some good news, https://twitter.com/letsencrypt/status/973607502188195840

@davidfischer
Copy link
Contributor

As of today, we have an SSL certificate for rtfd.io. We don't really advertise rtfd.org anymore but I will probably still try to add a certificate for it. It's lower priority though.

honzajavorek added a commit to apiaryio/dredd that referenced this issue Jul 18, 2018
kylef pushed a commit to apiaryio/dredd that referenced this issue Jul 18, 2018
@davidfischer
Copy link
Contributor

There is a cert for *.rtfd.org as well now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug A bug Operations Operations or server issue Status: blocked Issue is blocked on another issue
Projects
None yet
Development

No branches or pull requests