I have about five different subdomains on my host that are all working fine with wordpress installed.
I recently switched from Godaddy to Namecheap and bought a new domain name.
I changed the domain on my WHM Server which was all fine with my current sites.
The problem I have is when adding a new subdomain and installing Wordpress the site breaks because of DNS issues.
The Wordpress auto install is also weird as it doesn't detect the root like it used to, it puts the sub domain name into a folder above public_html.
So old subdomains are working fine but adding a new subdomain brings dns errors with wordpress installed.
Any ideas please, I've spent a solid five hours on this already.
Thanks.
If I'm following you correctly, you...
Created an account and bought a new domain on Namecheap
In Namecheap's WHM (Webhost Manager), you changed the domain to the one you had with GoDaddy.
When you create a new subdomain in Namecheap's WHM, it's not resolving the subdomain
So based on the above assumptions, it sounds like your domain is still with GoDaddy, and it's still pointing to GoDaddy's name servers. So if you add a new subdomain in Namecheap, it won't do anything, because Namecheap doesn't have control of the DNS. And for that matter, I think your subdomains would still be pointing to GoDaddy's servers.
Again, assuming I followed your description correctly, I'd recommend you migrate your old domain to Namecheap since, I'd assume, you're going to close your GoDaddy account at some point. If you need to urgently create a subdomain, you would need to do that on GoDaddy's end.
Hope this helps.
Fixed the problem myself, for anyone with a similar issue. I even went through Hostgator support who couldn't figure out the problem.
Logged into WHM > DNS Functions > Edit DNS Zone
The sub domain in question was not named correctly, it was named as the directory name instead of the full url.
Related
I own a domain through GoDaddy with the .app extension (call it mydomain.app). I have a site hosted on Firebase Hosting for this domain and it works fine. However, the website only loads through https://mydomain.app and not https://www.mydomain.app. I have the DNS properly configured according to GoDaddy tech support and wonder if I'm supposed to explicitly add www.mydomain.app in Firebase hosting in addition to mydomain.app? Seems redundant. Or is this not necessary and I have a configuration problem on my hands?
Go to GoDaddy, where you added your A record to point to Firebase the first time.
Since it's working, that means you configured it to use
# ==> your FirebaseAppUrl.
Under it, now, add also another A record, to configure your www.mydomain.com,
by adding www A record, to point to the same place.
www ==> your FirebaseAppUrl.
Keep both records of course in GoDaddy.
I have installed a WordPress multisite by bitnami on AWS EC2, and then configures Route53 to assign a domain name to the website. I have been unable to access the subdomains created since then.
I get this error whenever i try to access the website. Even, the dashboard can't be reached.
I have updated the .htaccess file as per the setting available in wordpress admin.
I have had a similar issue. You have to add a new CNAME record in the DNS records with the subdomain name, pointing towards the website. Alternatively, you can also add a wildcard '*' CNAME to make sure your multisite works without issues.
Also, make sure where your DNS is being resolved if your DNS is being handled by your domain registrar, then you will have to make changes there.
Hope this helps.
I'm pretty new to the Plesk AdminPanel. I own a Domain called riggiramone.ch. For a friend's project I'm trying to set Wordpress up on the subdomain mugi.riggiramone.ch. I did set up the subdomain and made it point at a subfolder of httpdocs (httpdocs/mugi). Then I have installes wordpress via the Plesk-own tool there.
My problem is that the subdomain mugi.riggiramone.ch is not reachable! I don't know why, I checked all the permissions.
Is there anything I did forget?
I think you are using external DNS server and due to that you are getting this issue. I will suggest you please check your main domain DNS zone and update the correct "A" record for your sun-domain and once you update it correctly you will not get any issues with your sub-domain.
I signed-up in AWS(Amazon Web server) for my Wordpress site. I also installed wordpress through AWS-ec2. I followed the steps inside AWs-ec2 documentation like LAMP and others needed.As I go through inside AWS-EC2 environment, I launched an instance where i can work for my Wordpress. Having an instance creates a default public domain name for my wordpress (http://ec2-xxx-xx-xxx-xx.us-west-2.compute.amazonaws.com/).
Now, my problem is I want to make our own domain name like example.com as our wordpress site instead of default domain name given by AWS-ec2. and, what are other requirements or tools needed to deploy it? We bought our domain name in GoDaddy.
Your answers will be highly appreciated.Thank you.
DNS
You need to start with setting up DNS. To do this you can use the service provided by Godaddy or use Route53 in amazon. You will set up records to point to your instance.
Apache
If you are using Virtualhosts, you will need to set up your Virtualhost to respond to the new domain name. If you are not using virtual hosting, it will return the same site regardless of which domain you used.
Wordpress
Wordpress does save the domain you installed it with in the settings. If you change the domain these settings may cause some issues. If you can't get into the Admin UI to fix this, update wp_options table in mysql.
My website doesn't work without www. It is not working since I installed WordPress.
Pardon me, I am not trying to market my site. But here it goes
http://www.stratageeks.com works
http://stratageeks.com doesn't
My settings in wordpress
If I remove www from both those places than the situation is other way, I have problem with www
Do I need to digg some place else? CName or what?
I believe the problem is with your DNS settings. You can check in with your hosting provider and make sure that the A Name for stratageeks.com, and that the CNAME www. points to stratageeks.com. The A Name usually contains the IP to your server and CNAME points to a web address