I installed a wordpress site. The visitors can only see the site without the prefix WWW. If someone types the website name with www, there is a "site not installed page". I am with OVH hosting and they are blaming the wordpress but I am sure that someone without good knowledge answered as the problem was the same even before the wp installation took place. If I change wp url location in the backend to www.mysite.com there is a backend lockout till I edit the database directly with the url without www.
My questions:
1> How to make my website accessible with both versions of the url (www+no www)? I want the www to appear in the address bar.
2> I do not want SEO rank loss due to duplicate content.
Please help as the customer care sucks and for 2 weeks they cant solve this problem. I am sure someone out here can please provide a few steps which I can follow and implement what I want. Thanks a lot in advance.
You may want to check with your hosting provider. I think technically, they are different URLs. Your host should be able to link both I would imagine.
Related
It's possible I don't know how to ask the right question, but I can't seem to find an answer to what's going on here anywhere. I have a Wordpress installation at example123.com, and want to set up a node application to run at licensing.example123.com. The problem I'm running into is when I put in licensing.example123.com, I keep getting forwarded to the wordpress site. I can't figure out a way to stop it. I don't see any special rules in .htaccess.. Does anybody have any ideas? Further details can be furnished upon request. TIA!
http://sidparmar.ca/portfolio/ This is my portfolio website and an only home page is working with the domain name. Every link is broken unless replaced by IP of my VPS which is 64.20.53.42.
So usually it should work like sidparmar.ca/portfolio/contact/ (give me an error "The requested URL /portfolio/resume/ was not found on this server.")
but currently, it is only working if I type 64.20.53.42/portfolio/contact/ as URL.
Please let me know if you have any suggestions/advice or pointer that I should look into. Any help is appreciated.
Has your site been like this since you installed Wordpress? If so, then where did you install wordpress (i.e. what directory)? It looks like you did not install it in the web root directory of your web server. Also, when you installed Wordpress, are you sure you specified the correct URL of your website?
My suggestion based on the limited information you provided and the minor amount of custom content of your website is to simply delete your database and files, create a new database, and re-installation Wordpress following exactly the correct instructions. Your VPS host may have an outlined process for you.
Alternatively, if this is a new issue, do you think you caused it? If so, what did you do? If not, you should probably contact your VPS host to see if you or they need to make an update in your DNS settings.
Found the answer by myself! Yeah!
I just added "ServerAlias www.domainname.ca" to my apache2 conf file (000-default.conf) which you can probably find at /etc/apache2/sites-available directory in your VPS.
Not sure why this worked or what exactly caused the problem but I am sure that it happened because of Yoast SEO plugin.
I have been optimising my site for load time and have managed to get my site down to <700kb with only 34 requests.
However, it's still not exactly snappy. On http://tools.pingdom.com/ it is apparently "slower than 75% of tested sites". Which is strange for a sub-1mb site with not many requests. The site is www.succeedenglish.com. It has just launched and is seeing about 30 visitors per day so it can't be traffic volume.
The problem I guess is the server. When I run a test on Pingdom, the URL makes up 5.5 seconds of a 6.25 second load time. A similar result is seen on http://www.webpagetest.org/
What does that URL mean? and how can I solve it?
The site is on WordPress with a Bluehost shared plan. I know shared isn't the best but it should be able to handle such a small site with so few visitors.
I'd really really appreciate any help. Thanks in advance.
After having a look at the speed test on pingdom, I noticed something that is unnecessarily adding 2.2 seconds to the load time. The URL request is being doubled.
Heres why, when you try to access www.succeedenglish.com you will notice that your wordpress website is redirecting to succeedenglish.com (without the www).
I did a test without the www and its faster:
http://tools.pingdom.com/fpt/#!/dM0eyP/succeedenglish.com
This is because the website URL in the settings found in the WP backend is set without the "www".
Heres my suggestion, login to the backend of wordpress and update the URL to include the "www".
You will find the fields to update under "General Settings". You will have to update 2 fields: "WordPress Address (URL)" and "Site Address (URL)"
That will sort out the unnecessary redirect onload.
However, if you also have images (image URLs) within posts and custom fields (used by some plugins), you would need to update all the URLs throughout the database.
To do this you can use a simple plugin called Velvet Blues Update URLs.
https://wordpress.org/plugins/velvet-blues-update-urls/
You can install it via the WordPress backend and then access the plugin here: Tools -> Update URLs.
What you want to do is replace all "http://succeedenglish.com/" urls with "http://www.succeedenglish.com/". Please remember to include the "http://", otherwise you will end up with incorrect URLs, just be cautious
Just be sure to check out the plugins instructions.
This will improve the load time.
Let me know if you come right.
So, I've read a few articles/blogs on this issue, but here's mine:
When I activate "Force SSL" in Woocommerce settings, I get a 404 on any pages that have HTTPS.
I have a dedicated SSL certificate on my domain, and that is no problem. It is not caused by plugins, I have tested that.
I've heard that you need to modify the "default-ssl" file on your server. You apparently need to modify your htaccess file to match the settings of your "default-ssl" file. If this is not accessible on a shared hosting server, then this is not a viable solution for anyone who doesn't have a VPS or access to root level SSH.
I've also been told that you need to reset your WP permalink settings to default. This is bad for SEO and quite frankly, an "I failed" non-solution.
If there is a way to get around this problem that can be fixed by having access only to cPanel and FTP, then answer this question. If it is definitely not possible via these means, please tell me why.
I'm not sure whether this is something that is going to benefit others, but if you're on shared hosting, testing on a subdomain is a bad idea. Rather test on "www.yourdomain.com/testing/", as opposed to "testing.yourdomain.com". Don't ask me why, the nerdy reasons I will leave to the back-end guys who answer my questions with grammatically unintelligible questions and down-votes.
You can have custom domains on your Woocommerce site after all. Don't test on a subdomain.
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.