My main domain on cpanel is example.com and my secondary site is hosted on the same server at sample-domain.zzz
But when people go to sample-domain.zzz/404-this-page-wont-exist it ends up taking them to sample-domain.zzz as a HTTP 200 :(
I can't figure out how to prevent this. Basically I need WP to stop taking over my other domains redirects. Hope this makes sense
Related
I'm not sure if this is possible. Not too familiar with Mod Rewrite.
I have domain1.tld registered on a hosting company and then I'm hosting a website on domain2.tld. I have forwarded domain1.tld and masked it. It works fine. Now I want domain2.tld to also show domain1.tld if I type it into the address bar.
It's running a WordPress site, so all my links are domain2.tld/link, but it only displays domain1.tld and my favicon also is gone. Is there a way I can get around this or would it be better to set up a hosting account where domain1.tld is registered, move the website there and redirect domain2.tld to domain1.tld. This would definately be the quickest and easiest way. I cannot point domain1.tld to domain2.tld or transfer it as the host does not support this TLD.
I assume your account at domain2.net does not support additional "Addon" or "Parked" domains (possible with some cPanel or maybe Plesk accounts)? I'm not sure whether a restriction on the TLD would apply here, since you're not "transferring" anything, just changing NAMESERVER or A records?
would it be better to set up a hosting account where domain1.tld is registered, move the website there and redirect domain2.tld to domain1.tld
Otherwise... Yes, that would certainly be a preferable solution.
If not, you are still going to need some kind of hosting account at domain1.tld from which you can forward requests (as a reverse proxy) to domain2.tld. Using "masked" (or "framed") forwarding is not a particularly good solution, as you have found. However, acting as a reverse proxy would require some configuration at domain1.tld, and depending on the next bit (see below) this might require more configuration.
so all my links are domain2.tld/link
If you want your site to be displayed at domain1.tld then this is something you would need to resolve. Can you make the links root-relative? Does WordPress need to know the domain/host on which it is running?
It is possible that the reverse proxy can handle this (ie. changing the link URLs in the HTML), but this requires more configuration. Or, you can roll your own proxy server.
But this all involves you having a hosting account (with some capability) anyway, so you might as well host your site there to begin with?
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
Recently I added SSL to my WordPress site but it started causing some problems (conflicts with Woocommerce and WP Super Cache plugins). The problem the I was having because of SSL was that the the Woocommerce cart was sometimes showing empty even after adding a product ans sometime the cart was not proceeding to checkout page. Do you think it had something to do with WP Super Cache or SSL or both? Anyway, I couldn't get it solved and removed the SSL after 2 days. But meanwhile Google had indexed the HTTPS URLs of my site and was showing them in the search results and they were returning SSL connection error. Now my question is how can I redirect all those HTTPS URLs to the HTTP ones? I asked my web host for help but said the redirection is not possible through htaccess or any other method. Was he right? How long will Google take to 'forget' these HTTPS links and show the HTTPS links again in search Results?
There are two standard ways to redirect:
At the DNS level
At the HTTP level
The DNS level can't help you because it just changes hostname. You want to keep the same hostname but change the scheme. This means you need an HTTP server to do the redirect.
In order to redirect from https to http you need to have an HTTPS service running on the computer with the IP address that the hostname resolves to.
Without that, there is nothing the receive the HTTP request over SSL and response with "Oh, this has moved to plain HTTP".
If the SSL service isn't running, then there is nothing that can do that.
(.htaccess is just a (suboptimal) means to configure an HTTP server, that does no good if you don't have the HTTP server listening on SSL).
Personally I'd fix the https issues. The world is going more https everyday so it's a backwards step to go from https to http. If you elaborate on what issues you had someone might be able to help.
However if you really want to do this then you need to run both http and https and redirect all traffic from https to http. How you do this depends on your set up (in Apache you'd do it using htaccess config).
How long it takes Google to fronded your site depends on many factors including the size and popularity of your site - which governs how often Google crawls your website. Give it a month at least for a small site. You can give it a kick by submitting your site to Google Search Console (the new name for Google Webmaster Tools).
Btw StackOverflow is primarily for programming questions so questions like this might be better asked on the http://webmasters.stackexchange.com sister site.
I have a Wordpress multi-site network setup so that all subdomains *.hosting.abc.com are a WP site in the network. I'm using Wordpress 3.6.
Most of the sites have custom domain mappings, for example, www.xyz.com points to xyz.hosting.abc.com. In the domain mappings settings, www.xyz.com is set as the primary.
Everything is working great except than when I visit www.xyz.com/wp-admin/ I get redirected to xyz.hosting.abc.com/wp-login.php but I expected I would get redirected to www.xyz.com/wp-login.php.
Is there a way to configure the network so that users aren't redirected away from their primary domain for the login?
Really, the main reason is that hosting.abc.com is not a real site and it has only dummy content. I don't want to draw attention to it, and for that matter, it got blocked by Bluecoat so people who work somewhere that uses Bluecoat for proxying can't log into their site. (yes, I'm one of the people blocked)
Hi I am hoping for some advice.
I have just managed to get a .co domain so I wish to point all requests from my .co.nz domain to the .co
I am running IIS7.5
I have created a services site e.g. services.mydomain.co.nz and the website mydomain.co.nz both are running on their own website and app pool.
At the moment I don't want to break any of the web services so I want to keep the services site as services.mydomain.co.nz but I want to automatically redirect website users to the .co domain instead of .co.nz
So far I have added a new host header in IIS and this allows me to hit the website using the .co domain but I can still hit the site using .co.nz
Do I need to create a url rewrite function to help with this?
You can use http redirection in IIS to direct all requests at the old domain to exactly the same path at the new domain.
You want to choose options as I have in this photo:
Include the full base url to the new site, ending at the slash after the domain name. then leave the other options as I have them; this way, any request at the old domain will be sent a 301 "permanent" code to redirect to the new, equivalent page on the new site.
Note that it's important that you do not check the first of those checkboxes under 'Redirect Behavior'; that will make it send all requests to the home page of your site, rather than to the same path url.
This should be on a separate IIS site, by the way.