I want to secure all my subdomains, without creating a subdomain on itself and then create a certificate.
I'm using .htaccess to redirect a subdomain to a folder. So a subdomain is not created on itself. It's just a nameholder to replace a folder.
My problem is: when I want in Plesk to create a *.domain.de subdomain and want to secure it with Let's Encrypt, then I got a error message: "Securing wildcard domains is not supported. Please deselect this option to proceed."
QUESTION:
Is there any other way to secure all subdomains automaticly wihtout creating a single cretificate for it?
I though the answer is simple. You would be a BIG help :)
thank you
AND
I answered my question on myself :D thank you for your votes for ym first question.
(1) I followed these simple steps:
https://support.plesk.com/hc/en-us/articles/115000490174-How-to-install-wildcard-certificates-with-Let-s-Encrypt-
(2) Created a *.domain subdomain via Plesk
(3) Opened the "Hosting Settings" for this subdomain in Plesk
(4) Under the point "Security" choose a certificate
(5) Save the new settings
NOW IT WORKS!
Hope I helped a lot of you.
You are a great community!
Related
As a complete newbie, I've been skulking through this site for about the past twelve months to find solutions to errors. The following issue has driven me to distraction to such a degree that I decided to join the fun and see if anyone can help.
I have a main site which has an essential SSL certificate. I recently created another site as an add-on domain to the main hosting. However, this means the add-on tries to run as https, causing a security error and blocking most of the html and css document. I'd be very grateful if anyone could offer advice on how to work around this.
The certificates are valid only for the domain specificed in the CN.
However you are not only one with this requirement, so what you can do:
use a wildcard certificate - the wildcard certificates are usually more expensive, but they cover all subdomain on that level (*.domain.com covers www.domain.com, mail.domain.com, ... but not domain.com itself)
use Subject Alternative Name - it is an explicit list of domiains covered by the certificate
im wondering and looking around for a possibility of a wildcard/catch all domain setting. I couldnt find anything online so ...
I basically want every domain that points to my site via an A-Record and which gets requested, to display my htdocs default folder.
At the moment every request for a domain that isnt setup as a webspace gets redirected to the default site. <- Thats not what I want.
Does anybody know a solution for this?
Thanks :)
I have Plesk 11.5.30 with Apache running
Do you mean you want to create wildcard subdomain on your domain ? Please have look at https://kb.plesk.com/en/2239
So I've recently implemented and activated SSL certification on my webshop. Now I need to change all the links on it to https:// from http://
There are a few hardcoded links on the site that I'm in the process of changing but most of the links are generated by a function that fetches the url from the PS database and I've managed to figure out that you add "true" value as argument and it will fetch the https url.
The thing is that there are a lot of diff. modules and it would take a lot of time to do such thing. So I thought there might be an easier way to do this? Some kind of configuration that will add "true" value as argument for all getPageLink() functions.
The SSL is working fine. The only thing Firefox, Chrome etc are complaining on is that some elements are not https. Any help would be appritiated.
Edit : I figured there has to be some kind of global variable that respresents the domain name. So I went to the database and found PS_SHOP_DOMAIN and PS_SHOP_DOMAIN_SSL. From what I've been able to figure out is that PS only apply SSL on the order and account pages. But I need it for all pages. so I changed the value for PS_SHOP_DOMAIN to https://domain.com but this did not make any difference. Am I on the right path?
Did you enable SSL here:
Preferences -> General -> Enable SSL
Regards,
I am currently building an application that I will host and will have multi-tenants (SaaS) called over the web, I would like them to be able to have subdomain.theircompany.com be able to point to subdomain.mycompany.com (or if they wish, point a full TLD to a subdomain with me).
The way I have been expecting this to work is to simply have a wildcard 'ServerAlias *.mycompany.com' in my Apache config pointing to my application, which then extracts the host being called...They then redirect via a CNAME entry on their host.
My question is, would this approach allow external subdomains to be pointed to a CNAME URL instead of IP? As this runs on one account on my system, am I able to install an SSL for a single wildcard if that customers wants to be running on SSL?
Any other suggestions/approaches would be greatly appreciated!
Thanks
A CNAME will work for the purposes of naming, but not for the purposes of a wildcard SSL cert.
Specifically, example.theircompany.com can have a CNAME record with a value of example.yourcompany.com. This will mean that example.theircompany.com will transparently resolve to your site. In other words, a browser still sees example.theircompany.com, not example.yourcompany.com.
As such, the SSL cert must be for the theircompany.com domain, not the yourcompany.com domain.
I have working https protocol on my subdomain. I would like to change current url:
http://www.mydomain.com/cgi-bin/mt/mt.cgi
to
https://ssl.mydomain.com/
How can I do it? Could anybody help me step by step? I am beginner in this field. I tried Google and also Movable Type forum, but no answer so far. Maybe this could help you http://www.movabletype.org/documentation/appendices/config-directives/admincgipath.html. Thank you for your help, I really appreciate it.
Thomas
The AdminCGIPath config directive is exactly what you need to apply.
Assuming that you have already set up SSL with your hosting provider and placed your MT application files in the correct web root for the SSL domain (which can be the same domain as your main site), here are the steps to change the MT admin path to use the SSL
Open the mt-config.cgi file.
Add the following line:
AdminCGIPath https://ssl.mydomain.com/cgi-bin/mt/mt.cgi
Save the mt-config.cgi file.
At this point you should be able to access MT via SSL by going to: https://ssl.mydomain.com/cgi-bin/mt/mt.cgi
Rather than access MT at the root of this domain--which I don't suggest because you may want to host other SSL apps--I suggest that you place a redirect script in your index file.
You can do this with Meta Refresh Tag or html meta refresh
That should answer your question.