A number of months ago I created the site cascocc.com. All is well. I then created another site coloradospringshomebuilders.com. All was well, I started development.
I then got an SSL for cascocc.com and installed it, all was well. Some items were not being delivered using SSL so I used the plug in force SSL to get the fancy green bar to show up.
Now coloradospringshomebuilders.com redirects to cascocc.com and I can not figure out how to fix it. I have reverted all my htacess files to the most basic possible. Am I missing one or what am I missing?
Any ideas?
EDIT: I deleted ALL .htaccess files on the entire server. The second site is still redirecting to the first and trying to use the firsts site SSL cert. I do not understand how this is happening
1st sites .htaccess file
2nd sites .htaccess file
This problem sounds like your Virtual hosts are not setup correctly. The SSL setting is overriding any other setting and redirecting to the page that is setup with SSL.
That can only be solved in the server settings (in this case most likely the virtual host). Depending on where you host your sites you might not have access to this, so I would advise to direct this question to your hosting provider.
This whole "redirect" is happening before the server reads the .htaccess files, that's why you can't solve this problem there.
Related
I just migrated the my website from my old domain to new domain. Its migrated but when I am clicking on something like pages or category its redirecting me to the old site with this error:
The site can't provide a secure connection. shopskart.in sent an invalid response. ERR_SSL_PROTOCOL_ERROR
Screenshot of error message
I also did these changes in wp-conf and wp-options but still I am getting same issue. Someone said its because its forcing site to https due to SSL I had but now I don't have SSL and don't want one right now.
You probably copied the old SSL file to your new site, and it's still active. You should disable it. Also check if there's any setting (in backend or database) pointing to https in stead of http, since you won't be using a secure connection anymore (Why not? You should!). Check the htaccess file as well! If the problem still occurs try clearing your browsercache.
From where i can find the ssl file. Or code. Actually the website was created by my developer and now he refused to give the data when i asked him. So i migraded using wp plugins and dont know where he pasted the ssl certificate.
I have a Wordpress site that is migrated to a new server. Along with the migration, it now also has a subfolder /en which is a different version of the website targeted for international audience. The problem I am facing is that if I try to load the site example.com/en, on the first load it redirects to example.com. But if I load example.com/en on the second try it goes to the subfolder website. And it is browser specific. I have this problem on Chrome and Safari but not on Firefox
I have already tried clearing the cache in the CMS level and also on the browser, this hasn't helped in any way. Could it be because of DNS switching from older server to the new server?
Thanks
Here are some ideas on how to find the root of the problem:
Check the site from a different network / device to make sure it's not the DNS cache
Check the .htaccess file of the server, maybe theres a misconfiguration
Use a site like this one to trace the redirect
If nothing helpes you could just wait a few hours, maybe the DNS servers take some time to update all the settings.
I am getting a Cloudflare error 525 in my Wordpress.
I'm working on a subdomain where the domain has https that work fine through cloudflare but the subdomain does not.
Hosting: Godaddy
The SSL certificate is UCC bought from Godaddy.
Crypto SSL in Cloudflare: FULL
I made all the changes in Wordpress mainly following these steps: force https pages wordpress
And all URLs are changed from http:// to https://.
Can anyone help me, I'm running out of ideas and I do not know what else I should do?
That error indicates that the ssl handshake is failing on the subdomain. The subdomain might be configured differently at a web-server level, or there may be Page Rules that change the behavior
https://support.cloudflare.com/hc/en-us/articles/200278659-Error-525-SSL-handshake-failed
In case someone still get this error, here is how I fixed it.
This was driving me crazy because the site was working fine and then the error started to manifest intermittently: error page shows, then by refreshing a couple of times the site loaded but with some missing images. So it was a mess.
Tried to reach out for godaddy support but it was not very useful. They checked the files, database, open ports and even changed the propagating DNS, but still the error was persisting.
At the end I tried:
Disable my ssl plugin in wordpress (really simple SSL)
Go back to http setting
In cloudflare, set the SSL setting to flexible
I found out that Cloudflare takes over the writing of the https links, so the plugin was creating a redirect loop and that was causing the handshake to fail.
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.