question Is there a parking service that supports https?

[Dimitar Nestorov]

Google Chrome refuses to visit the new .app domains without https

 

[un1]

Here is how to activate your SSL cert:

I could activate for "one and only one" (of several domains registered). As I try to activate for other domains, the interface forwards me to a generic paid SSL packages (shopping) page. I examined any single item in the interface, yet could not activated the SSL cert for the 2nd domain.

 

[Jurgen Wolf]

Probably...
I can't confirm regarding multiple .app domains because I have regged the only one...

 

[Jurgen Wolf]

You may try this...
Reg/transfer every .app domain into the separate contract/package...
95% that 1and1 provides 1 FREE SSL cert per each contract/package...
Because, for example, I have another contract where I keep some .ORG - and I activated SSL for it also.

 

[Jurgen Wolf]

Left sidebar in your 1and1 panel, click: Contract and Product Overview
Then click yellow button CREATE ANOTHER CONTRACT - you will get empty contract (without domains).
Then click this contract (open it) - and reg/transfer your next .app domain into it.

 

[Jurgen Wolf]

+ you may move your existent domains between your contracts...
So create as many contracts - as you want...
And then move every .app domain into its own contract...
So in this way you should get FREE SSL cert for all your .app domains.

 

[Jurgen Wolf]

Here is described how to move the domains between your contracts:
https://help.1and1.com/domains-c369...packages-within-the-same-account-a792490.html

 

[domainer111]

I use DigitalOcean.com $5 per month, unlimited domains, unlimited SSLs. A few lines of code installs the SSL from LetsEncrypt. But then the site has to be configured.

I can see why this is impractical from a domain parking viewpoint.

I do park a few domains with @Donny and I'm not sure what's going to happen once the Chrome changes kick in.

 

[un1]

Here is described how to move the domains between your contracts:

thanks for detailed description.

by the way, i received a message from undeveloped:

Hi,
Google forces HTTPS even before the redirect in Chrome for .app domains. We're currently negotiating a deal to get SSL on more than 1M parked domains. Once we got a deal we can implement SSL on all landers to avoid this issue.
Kind regards,

I guess this issue will be resolved soon.

 

[Michael M]

Check out this thread... I made a free "app" to create an SSL and forward your new app domains to a lander. Let me know if you need any landing services added that are supporting .app domains. (Sedo is not yet)


https://www.namepros.com/threads/free-app-ssl-forwarding-for-landers.1081373/

 

[matt_bodis]

We've looked into supporting HTTPS across multiple domains but have not found any solution. If you guys find any way to do this, we will gladly try to implement it. It's definitely something we'd be very interested in doing.

We'd have to find a way to bind a signed SSL certificate to multiple domains. Not sure if it is possible. We can probably make the HTTPS semi-work, but you'll be given an alert in Chrome and other browsers that the SSL is not signed and have to agree to go forward to the parked page. In such a scenario, you'll lose most visitors thus it isn't ideal and the reason we haven't ever proceeded with such an implementation.

I will look into LetsEncrypt. First time I hear of them.

 

[matt_bodis]

There will not be any parking companies that support SSL. Let's encrypt is a great idea, but you have to load every certificate on every box. Let's say you have 30 servers and 2,000,000 domains. Do you know how long apache or nginx would take to reload when a new cert is added?

We looked into it and tried. It's not worth it.

Donny

Guess I missed this post. Thanks Donny for saving us a ton of time.

 

[Michael M]

We've looked into supporting HTTPS across multiple domains but have not found any solution. If you guys find any way to do this, we will gladly try to implement it. It's definitely something we'd be very interested in doing.

We'd have to find a way to bind a signed SSL certificate to multiple domains. Not sure if it is possible. We can probably make the HTTPS semi-work, but you'll be given an alert in Chrome and other browsers that the SSL is not signed and have to agree to go forward to the parked page. In such a scenario, you'll lose most visitors thus it isn't ideal and the reason we haven't ever proceeded with such an implementation.

I will look into LetsEncrypt. First time I hear of them.

It is possible - I have done it above in a post for everyone until you guys figure it out.

Check out this thread... I made a free "app" to create an SSL and forward your new app domains to a lander. Let me know if you need any landing services added that are supporting .app domains. (Sedo is not yet)


https://www.namepros.com/threads/free-app-ssl-forwarding-for-landers.1081373/

With LetsEncrypt you can only put 100 domains per SAN certificate - so a service like yours can't solve the problem with one cert. But if you have questions I can help you guys implement something at no charge (for advice).

I probably need to add Bodis as a lander option as it is not there yet. What is the URL structure for Bodis?

 

[Donny]

@matt_bodis - Yeah, it's a little tough to deal with, since each of us have load balancers, you would have to put the cert on each server. And adding a single name would require you to add the new cert and reload apache or nginx, with so many certs it's really slow.

Not sure how possible this is going to be anytime soon.

Hope you are feeling better.

Donny

 

[Michael M]

@matt_bodis - Yeah, it's a little tough to deal with, since each of us have load balancers, you would have to put the cert on each server. And adding a single name would require you to add the new cert and reload apache or nginx, with so many certs it's really slow.

Not sure how possible this is going to be anytime soon.

Hope you are feeling better.

Donny

When there is a will, there is a way. I would imagine all the parking and registrars need to get this figured out for a landing page to be possible on .app without technical knowledge from domainers or an external solution they may be hesitant to use.

Also keep in mind the entire web is going towards SSL, so this is coming guys. Landing/Parking/Registrars need to get this figured out on their level.

 

[matt_bodis]

@Donny - thanks. You make some great points. And yeah getting there.

@Michael M - very true indeed. The future definitely is in HTTPS. Actually, as with .app domains, even the present is now with HTTPS. So a solution is definitely required either sooner or later.

It won't hurt for us to look into it while taking all of Donny's great points into account.

 

[domains21]

Maybe it would be worth looking into how Cloudflare does it with their Universal SSL ?

 

[Michael M]

@Donny - thanks. You make some great points. And yeah getting there.

@Michael M - very true indeed. The future definitely is in HTTPS. Actually, as with .app domains, even the present is now with HTTPS. So a solution is definitely required either sooner or later.

It won't hurt for us to look into it while taking all of Donny's great points into account.

Thanks for keeping an open mind...

Also, just a thought... Many hosting companies host 10s to 100s of thousands of websites with their own SSL cert without a problem. (though they generally charge the customer for the SSL cert)

It is just a new idea to the Domaining/Parking/Landing Service companies - but with SEO in mind at a minimum it is time for these companies to start working towards it.

 

[Michael M]

@matt_bodis - Yeah, it's a little tough to deal with, since each of us have load balancers, you would have to put the cert on each server. And adding a single name would require you to add the new cert and reload apache or nginx, with so many certs it's really slow.

Not sure how possible this is going to be anytime soon.

Hope you are feeling better.

Donny

@Donny
@matt_bodis

It might take adding a third server into the situation to keep the load balancing going, but only restart one webserver at a time in a sequence - if a full restart of the entire webserver is needed.

(Windows Server guy myself so would have to play with it to see how to achieve in apache or nginx)

But...

I know this seems "extreme" to make a separate site for tons of domains - but couldn't you guys:
1. Create a separate web site for each domain (which point to the same root dir on the server)
2. Systematically create an SSL for each domain using LetsEncrypt to keep it free
3. Assign the cert to that site, and restart that site
4. Renew the LetsEncrypt certificates in an automated routine

 

[matt_bodis]

That was my thought, to keep the HTTPS domains on seperate VMs/servers from the non-HTTPS. That would actually be the way we'd do it on our end.

I've assigned it to our dev for the next week to look at. I guess once we look at it we'll know what we're dealing with pretty quickly.

Right now pretty sure Donny had quite a look into it so not getting too excited.

 

[matt_bodis]

I'll be sure to post our findings then. Thanks for bringing entire idea up.