I'm using Wordpress multi sites with the domain mapping plugin. My websites used to run on sub domains the name looked like this example.test.com and the main site was test.com. With the domain mapping plugin I managed to turn sub domains into normal looking domains. my sub domain now looks like example1.com. My question now is: Do when I install an ssl certificate on which domain do I need to install this on, the sub domain or the domain I map to ?
Normal SSL certificates are for single domain or subdomain only. But, you can get Wildcard SSL, and that one SSL covers all subdomains for a single domain. Or get Let's Encrypt free SSL for each subdomain (if your host supports it).
Related
Users can create subdomains with my root domain using my angular project. So, we are using wildcard subdomain to create subdomains. We are nginx. Now, our requirement is, if user wants a custom sub domain, then he should able to point his custom sub domain with our wildcard subdomain. How we can achieve this?
Eg: User has subdomain user.abc.com and we are providing *.xyz.com.
User created a sub domain hello.xyz.com, now he wants to redirect his user.abc.com to hello.xyz.com. How can we achieve this scenario with nginx.
In your nginx conf file if you mention server_name *.domain.com; all of your subdomains should be pointed to the same angular project.
However, note that you will also need to create a name server for the subdomain created by the customer pointing to server IP.
For e.g., if you're using AWS DNS service Route 53 then whenever customer creates the new subdomain then you will have to create the same under route 53 and point it to application server IP
I have a wordpress installation and I have a security certificate installed for the main site, however, it is a subsite installation and how do I make the security certificate work for all the wildcard (*) subsites?
For securing sub domains of the main domain you will have to enable wildcard ssl certificate at only main domain name.
For example:
If you have domain name xyz.com and want to secure its all sub domain names then you will have to enable wildcard ssl certificate at *.xyz.com then it will automatically will secure its all first level sub domains like blog.xyz.com, payment.xyz.com etc.
As per you requirements, you need to obtain a new Wildcard SSL certificate to protect your subsites (sub-domains). It will protect your entire website and its multiple sub-domains. To obtain this certificate, you have to add a single asterisk (*) just before your domain name (i.e. - *.yoursite.com), it will allow to secure all first-level sub-domains.
As you mentioned that you already have an SSL certificate for your main website, but managing individual certificates for your main site and each sub-domain will be horrible and time consuming for administrators. Wildcard SSL certificate is perfect, flexible and money saving certificate in the state of sub-domains security.
I've set up a parked domain and set it's nameservers to cloudflare nameservers. but I have a strange problem. I can access the parked domain only with https (e.g. https://domain.xyz).
If I access it using http it will redirect to defaultwebpage.cgi. but if I access one of the files or folders or pages (e.g. http://domain.xyz/test) the page will load without any problems. the problem only exists on the homepage (e.g. http://domain.xyz).
the cloudflare is using flexible setting.
It's not cloudflare issues, Might be there is an issues with your local end, Please try to clear your browser cache and try again. OR try to check your domain through proxy sites.
Did you create any Page Rules in Cloudflare? I understand that you use a Cloudflare Flexible SSL certificate. In order to redirect http traffic (with our without www) to https traffic you need to add a Page Rule in Cloudflare. Did you do that?
Create a page rule like this in Cloudflare:
http://*.domain.xyz/* that redirects to https://www.domain.xyz/$1
I am building an eCommerce platform and I would like to give my user's the ability to point their domain (e.g. bobsburgers.com) to an HTTPS-protected subdomain on my site (e.g. bobsburgers.shoplolz.com). Getting a wildcard certificate for the dynamic subdomain is simple, but how does one allow their users to use their own domain while requiring HTTP? I'm currently hosted on Heroku but I'm curious at a higher level how this can work, if at all.
Based on my research the only way to do this is to have the site owner upload an SSL certificate and use an HTTPS-enabled reverse proxy which can be configured dynamically to accept new SSL certificates for newly added domains.
I manage a hosting server using WHM. I have two cPanel accounts on this server, one for exampletest.com (account name is exampletest) and one for example.com (account name example). We have a Wordpress site that was working well at exampletest.com but we keep running into problems when we try to migrate it to example.com. I believe it has to do with one WordPress plugin that doesn't migrate well.
So we had the idea to simply take the example.com domain and point it to the exampletest cPanel account, then update the domain for WordPress in the database. However, one potential issue I can see is that we have many active email addresses on the example account. I fear that associating the example.com domain to the exampletest account will break the email addresses.
Keeping the above in mind, I have a couple questions:
Will associating the example.com domain to the exampletest account break the emails? If so, is there a workaround (moving the email addresses to the new account somehow?)
Is there a better way to go about doing this that I'm not thinking of?
The best way of transferring your wordpress site would be to copy the files, create a database user with the same login details and import the database. Wordpress shouldn't be able to tell the difference.
One way would be to assign a static IP address to exampletest and point example.com's A record to that IP.
Due to the way WHM's DNS and port binding is set up it will not let you set up the same domain on two seperate accounts.
You could treat www. as a seperate subdomain and add the subdomain www.example.com to exampletest as an addon domain and remove the www A record from example first. Redirect all web traffic from example.com to www.example.com or use another sub-domain such as www2.
Another option would be transfer the emails, you can either use the transfer tools in WHM > Transfers or use http://imapsync.lamiral.info/