I need to keep an old version of website in tact as a subdomain, so subdomain.domain.com points to the old IIS server running DNN and the default page appears fine.
However, any interior pages, /contact.aspx for example, return a 404 error. If I revert to ugly urls (default.aspx?TabId=##) the page works but attempts to redirect to domain.com instead of subdomain.domain.com.
Unfortunately I am unfamiliar with IIS and DNN, but the task is the task! Any help would be greatly appreciated. I will supply any additional details should anyone know what details I need to supply...
Note: a binding for the subdomain has been added, but the above happens with our without this addition.
Have you added that "subdomain" as an Alias in DNN? You can do this in the PortalAlias table
Related
OK, our old website is Wordpress installed on a NGINX bitnami distribution in AWS.
Our new website is on managed hosting on a new domain name.
For the migration, we'd used the plugin 'Simple 301 redirects' to map each page to the new site structure.
However, for reasons we can't fathom and have only just spotted, all the redirects are reporting as 302 - which is hurting our SEO.
Our theory is that re-implementing the 301s but at server level config on the NGINX server will be used before it hits the WP installation, and hopefully achieve an actual 301 redirect.
I can find a number of support articles that might help us: https://www.digitalocean.com/community/tutorials/how-to-create-temporary-and-permanent-redirects-with-nginx although this article suggests using return instead of rewrite: https://www.nginx.com/resources/wiki/start/topics/tutorials/config_pitfalls/?highlight=rewrite#taxing-rewrites
If our theory is correct, we'll create a new server config that redirects each individual page (we need to do this, as the site structure has changed in some cases - it is about 250 pages FYI).
Would somebody be able to offer any additional advice on this?
We're still baffled as to why it is returning 302 redirects rather than 301...!
Greatly appreciated!
I have a redirect issue on the website
The dmhdubai.com page isn’t working
dmhdubai.com redirected you too many times.
It was run on cloudflare then i changed the nameservers new server and changed back to the original nameservers .
What can be the problem?
#info, it appears your website dmhdubai.com is not stuck in a redirect loop. You'll need to clear your browser cache to remove any past redirects caused by previous directives.
You can check your website's redirect route at www.wheregoes.com/retracer.php.
I'm a new in web development so the question is maybe pretty simple, but I can't handle it by myself.
I have a wordpress website which hosts on hostmonster.com and it has a URL, let's say, http://aaa.com/bbb.org. So it is located in the subdirectory bbb.org of the main directory http://aaa.com in my host monster account.
I also have a domain name, let's say, http://bbb.org on godaddy.com and now I want to make my site available on address http://bbb.org. How to do that?
I did the following thing. I forwarded http://bbb.org to http://aaa.com/bbb.org in settings on godaddy.com, but it's not what I need, because user still see old address (http://aaa.com/bbb.org) in his address line. So what am I doing wrong?
I think you don't want to redirect from http://aaa.com/bbb.org.If so you will be need 5 step.
STEP 1: TRANSFERRING FILES
The first step in moving your website to your new domain name is to create an account on your server or shared hosting plan for the new domain and then transfer over all of the old website files to the new account you have created for the new domain. Be sure to just copy the files over and do not in any case delete the files from the old account for the old domain name yet.
STEP 2: CHANGE NAMESERVERS
Be sure and change the nameservers of the new domain name to point to the newly created account that you have created on your server or shared hosting plan. Keep in mind that it will typically take between 48 and 72 hours for the DNS to propogate throughout the web.
STEP 3: CHANGE FILES
The next step is to change all instances of the old domain to the new domain within the files that you have transferred over to the new account on your server. You will most likely be able to accomplish this very quickly if you just use the find and replace feature in your FTP client (i.e. Dreamweaver, FileZilla, etc.). Making all of your links absolute links rather than relative links is usually the best way to go for SEO purposes so if this is something that you had ever considered changing over then now would be a good time to go through and audit all of your website files to change relative links to absolute when appropriate.
STEP 4: CREATE 301 REDIRECTS
Setting up 301 redirects in your .htaccess (assuming you have a Linux server) under your old account is very important. A 301 redirect will work to automatically and permanently redirect visitors and search engine bots who visit www.olddomain.com/my-page to www.newdomain.com/my-page. This is very important from an SEO perspective because 301 redirects have the potential to pass through the “link juice” of any backlinks pointing to the old domain to the new domain along with any accompanying search engine rankings. This is also very important from a user perspective because anyone that tries to visit any page on your old domain will be automatically sent to the appropriate page on your new domain. Read this guide on how to set up 301 redirects to get all of the nitty gritty 301 redirect setup details.
STEP 5: TEST
Make sure that your nameservers have been set up on your new domain and that the DNS has finished propogating. Once you verify that the DNS is resolving correctly for the new domain then it is time to test out all of the old pages that you are redirecting from the old domain to the new domain and then also test by looking through each page of the new site and make sure that there are no errors (from find and replace errors when changing files or other issues).
If all of the pages of your old site have been indexed by Google then a quick way to test out that the 301 redirects have all been set up and working properly is to simply do an advanced Google search query that will return all of the pages from your old site indexed by Google. You can do this simply by typing “site:olddomain.com” into Google (without the “”). Now all you have to do is click on every page and if you have set up the 301 redirects properly then each time you click on the page link your server should automatically and instantly redirect you to the appropriate new page on your new domain.
That all you need ?
Typically, a hosting solution will have DNS redirecting that it will help you. The issue is that you might be using GoDaddy for your DNS managing. In which cause the redirecting DNS with hostmonster will not come through.
The best thing to do is have your GoDaddy point to the nameservers from HostMonster and have HostMonster control DNS. Then you can just create a redirect inside HostMonster and point bb.org it to http://aaa.com/bbb.org but your URL will just be bbb.org.
This sounds like a Masking problem, (you have enabled forwarding, but not masking) http://support.godaddy.com/help/article/422/forwarding-or-masking-your-domain-name
Also, note that you 301 redirects will be cached by clients, so use 302 redirects unless you are sure you've set it up the way you want it.
Make sure to follow the above answers. But using the The Duplicator plugin will streamline the actual Wordpress website migration very easily.
I have developed a wordpress based site using xampp 1.8.3. On my local machine all is wordìking fine. On the server I am using php 5.4.12.
On the server I copied the site on a subfolder name site, wich is the same subfolder name I had in xampp/htdocs. Then i changed all occurances of localhost to mydomain.com with the searchreplacedb2.php script (http://interconnectit.com/products/search-and-replace-for-wordpress-databases). I am confident that the tool is working properly and the issue does not depend on it as I have used it several other times with succcess.
Therefore since on my local machine the site was in localhost/site, on the hosting server is on mydomain.com/site.
The proble is that accessing the site home page produces a wordpress managed 404 page with no css being loaded. The title, menu and other site specific text is displayed, therefore the db is being read correctly. Trying to access any page other than the home page gets a webhost managed 404 page. This happens also if I try to access page through non symbolic urls, ei. mydomain.com/site/?page_id=5; therefore it is should not be a redirection issues.
what can be the issue? How can I proceed in troubleshooting it?
Thanks, in advance for your time.
You need to double check everything, first:
Flush the rewrite rules by visiting settings->permalinks then try your pages. Then try:
List item login to phpmyadmin for each domain, check out the database... options table... verify the "siteurl", and "home" columns. make sure they match the respective domains. Then try:
List itemCheck the DNS zone template. Could very well be possible DNS conflicts.
I have an ASP.Net MVC 3 Website hosted on a shared Windows hosting package. I wish for my site to automatically add a 'www' prefix to all my site pages when the user does not type it in, ie, mytestpage.com redirects to www.mytestpage.com.
I have browsed extensively through Stackoverflow and other Internet sites to find a solution to this, but to no avail. The solutions given are to either configure IIS itself, however, I do not have access to IIS as I am using a shared hosting package.
Others have said to add the prefix via the web config file IIS7 URL Rewrite - Add "www" prefix however this seems only to work with IIS 7.
Is there any other way I can achieve this?
Your help is greatly appreciated.
Thanks.
On my solutions I do a check on Application Start whether the request has www or not. If not, I redirect to www.
And all my links are relative, of course.