I got a free domain from freenom (.gq) and i tried connecting it to my github repo (genarcy.github.io) by putting in githubs dns but it wouldnt work. it keeps saying dns unsuccessful. The picture below is my dns. The document github i didnt understand
You need to also add the domain to your GitHub repo settings > pages > custom domain
Related
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 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.
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've migrated my Wordpress blog to OpenShift recently. It works perfect until when you try to add a custom domain alias to your installation.
The OpenShift URL for my blog is blog-latifetunc.rhcloud.com
I added the following URL as alias: blog.latifetunc.com
(Sorry I couldn't attach images since I don't have enough reputation points. Instead I put links to images. This is my first question in StackOverflow.)
http://www.alpertunc.com/q1.png
I successfully added the CNAME record for my domain to point blog.latifetunc.com to blog-latifetunc.rhcloud.com in GoDaddy
http://www.alpertunc.com/q2.png
The problem pops up when I try to reach my blog with this alias. It says:
Safari can't verify the identity of the website "blog.latifetunc.com".
The certificate for this website is invalid. You might be connecting to a website that is pretending to be "blog.latifetunc.com", which could put your confidential information at risk. Would you like to connect to the website anyway?
(I can't even post more than two links without 10 reputation points :( So please put the above URL in front of below images as well.)
q3.png
If you click "Continue" it works fine but this alert is very scary for many users. I searched for hours for a solution with no luck. I considered buying a security certificate as well but then I thought this blog was working with an alias in its previous installation too. However we never had such an alert in browser while visiting either via the main domain or the alias.
The previous installation was on IIS and the binding were as following:
q4.png
Then when my brain was about to explode I found out that the alert is due to https. When I checked Settings from my Wordpress dashboard I realised that somehow OpenShift installs Wordpress on https and sets the permalinks to https.
q5.png
In fact whatever you type that points to *.rhcloud.com is converted to https. I know that because I added the CNAME for www.latifetunc.net to point to blog-latifetunc.rhcloud.com as well but didn't add the alias in OpenShift Applications. So www.latifetunc.net resolves to blog-latifetunc.rhcloud.com but since there is no alias defined (hence there is no vhost entry in Apache) it gives error. But even that error is in port 443!
q6.png
My main problem is to get rid of the certificate error while visiting my blog via my alias domain name. I really appreciate any help on that one.
My related question is that why on earth permalinks start with https on OpenShift Wordpress installation? If I can solve that, probably I'll solve my main problem as well.
Thanks a lot!
I checked blog.latifetunc.com on safari,chrome,firefox, and opera and I didn't get any warnings so you much have figured out a solution. However for others who may stumble across this I've provided some information:
By default OpenShift applications accept traffic on both http and https. So if you're wanting to have a custom domain but aren't worried about ssl than you can simply just use the http connection to your application (http://myapp.com). If you are wanting to apply a SSL certificate and you're on one of the plans that allow it (bronze or silver). The documentation to apply it, is in the SSL Section of the OpenShift Online User Guide.
So, I got Wordpress installed and working just fine. I can access the site and the wp-admin via the public DNS that I get from the instance.
However, once I create an elastic IP and associate it with the instance, I can no longer access wp-admin and the home page style sheets and JavaScript files are not loaded.
I am attempting to access the site and the wp-admin using the new public IP from the elastic IP. Same thing is true if I try to use the public DNS from either the elastic IP or the EC2 instance.
When I view the page source I see that the reason things aren't loaded is because the URL for all of the assets (.css, .js. etc,) is pointing to the bold public DNS
When I disassociate the elastic IP things do not go back to working again.
I'm missing something but don't know what.
Any help would be appreciated
Your wordpress admin is already associated with your publicDNS. This is because, when you have logged-in the wp-admin console, you have created a new admin user. This information with respect to your publicDNS was saved in the mysql db. So you won't be able to access wp-admin from the elastic IP.
What you can do ?
You can log-in to your wordpress mysql and update all the references of the publicDNS to Elastic IP. Once it is done, you will be able to access the wp-admin from the static IP.
I run into the same problem. A quick fix is to hardcode your site URL into the wp-config.php which you can edit via FTP.
define('WP_HOME','http://yoursite.com');
define('WP_SITEURL','http://yoursite.com');
Worked fine for me.
See also https://codex.wordpress.org/Changing_The_Site_URL for guideline.
I too faced the same issue, followed the steps in this page to get my issue fixed.
http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/hosting-wordpress.html
Follow steps under this section:
"Help! My Public DNS Name Changed and now my Blog is Broken"
Pasting it here for quick reference: Login via ssh to your ec2 instance then run the below commands:
Download the wp-cli with the following command
curl -O https://raw.githubusercontent.com/wp-cli/builds/gh-pages/phar/wp-cli.phar
Search and replace the old site URL in your WordPress installation with the following command. Substitute the old and new site URLs for your EC2 instance and the path to your WordPress installation (usually /var/www/html or /var/www/html/blog)
php wp-cli.phar search-replace 'old_site_url' 'new_site_url' --path=/path/to/wordpress/installation --skip-columns=guid