I am about to migrate/move the data from a Windows Plesk server to a Linux Plesk server. Which in itself is a humongous pain in the a***!
On top of that I am developing a new version of a website on the current WPlesk(Windows Plesk). It is being developed in Wordpress. The current website is running a system called nemCMS, which requires a WPlesk to run.
When I move the data and domain to the new LPlesk(Linux Plesk), will I then be able to set up the htaccess redirects from the old - now non existing nemCMS site & URLs - without losing page rank etc.?
I hope you are able to help me out!
Thanks!
Officially migration from WPlesk to LPlesk and vice versa is not supported. You can do it only with creation the same domain/hosting on destination server and migration site content manually. Be sure that site is not connected to any Windows only web technologies :)
For redirection you can just change type of hosting for domain on WPlesk to Forwarding.
Related
Our website not running on new server Tour website we have 2 servers one of them the site working good, we have moved the portal to other server, so when we point the dns it is not working...Web not working and then you can see the panel of that server in second imageCWP web control panel I need the solution, kindly give the proper solution...
You are using CentOS Web panel as the hosting control panel. While browsing the website check the apache error logs on the server at path
/usr/local/apache/logs/
and those logs will give you idea of whats happening.
So I'm a web designer with experience in HTML, CSS and Java. I've used FTP to manage my site a couple of times for my company.
Overall I have experience in using Joomla and WordPress CMSs, but that's just the problem: I have barely any experience in even understanding DNSs, server stuff, domain management. I could really use some help on this.
Firstly, our IT Manager left so now I'm in charge as the sole web designer of the company. The website URL is www.????.org.uk and that's where the live website is.
Issue here is that sometimes I type in the same URL WITHOUT the www, which results in ANOTHER website (actually a beta I worked on a while ago that I'm sure the IT Manager set up for me).
We have a 123reg account and a HeartInternet Reseller hosting account. I understand that you buy domains, and you can forward them to a hosting platform to manage them and 'serve' them on servers to make them live. So in this case I'm betting it's owned and bought using 123Reg, and hosted on HeartInternet.
Here's the second issue I don't understand. We have a bunch of domains bought, most redirecting to www.????.org.uk, but we ALSO have the URL WITHOUT the www.
Remember what I said earlier? All things point to www version, but we own a domain WITHOUT the www and I can't find the domain listed anywhere with the www, so how in the world can I manage the www site (which is the live site)?
Please do teach me a little if you can about this and point me to the right direction. Thank you!
From what I saw several times before:
By default the www is use-less and points to the default ip:port registered at ????.org.uk. For a reason (that I don't understand) some people create a new DNS entry with a sub-domain called "www" pinging to a different ip and/or port. This results in www.????.org.uk acting like someSubDomain.????.org.uk.
Have you checked if this could be your case?
If it is, I suggest you change the "www" subdomain to "dev" or "beta". This will make www.????.org.uk and ????.org.uk redirect to the same "website" and beta.????.org.uk to the beta version of your company's site.
Be aware that a DNS change could require up to 24h to be spread and updated on the ISP's servers.
I am launching a new redesigned website on windows hosting. I am wondering what is the best way to launch this new website without having any downtime on the existing one?
MY only fear is having a user go to visit a page and it's not there or the supporting files are not uploaded yet.
One of the simplest ways to handle this is to put a load balancer or proxy server in front of the application server. Then set up another application server with the new code. Once it is ready, you can change the proxy server to point to the new application server with the new code. Once you are sure nobody is using the old application server, you can shut it down. This, of course, relies on your ability to get that setup in place. If you are on a budget, you might be able to do it all on a single box. For instance, you could use nginx as a reverse proxy to your application on the same box. Getting that in place could potentially cause a tiny window of downtime - not sure if that's acceptable. Then you might be able to set up the new application on the same box with a different port - again, I'm not sure if that would work for your setup. Anyway, the reverse proxy approach is a pretty common one, and one of the great reasons for deploying to the cloud. You only pay for the short period of time when you need both boxes.
You should make sure that your new website launches all at once and that you set up the proper redirection rules for all previous pages. Once you are launching the new website, pick a time at night where you have low traffic volume, and simply upload all the new code at once to the webserver. This eliminates the fear you have of the "supporting files not uploaded yet". One of the key things to do is make sure all your old pages redirect and map over to new pages on the site just in case anyone clicks into your site using external links.
Two good resources to read:
http://www.rise.net/blog/ideal-way-launch-website-rebrand
http://googlewebmastercentral.blogspot.com/2008/04/best-practices-when-moving-your-site.html
The best methos is to upload the site via FTP, and if you have RD access to login into the Windows server and to copy the new site for a few seconds. In this way you will not have any downtime as when you directly upload the site via FTP.
Is there a good way of remotely managing 301 redirects in IIS? I have recently taken ownership of a small retail ASP.NET website I've been tasked with providing our SEO provider the ability to change redirects for old products etc without having direct access to the server, or needing us to make the change.
The website is ASP.NET 4.0, running on Windows Server 2008 with IIS 7.
you could maintain a list of the required redirects via an app.config file - have a module which takes the request and checks the request against the file
if there is a match then you could redirect to a known place. The trouble is that it could be a little slow - instead of a config file you could store the redirects in the database as an alternative
Note: I originally posted this on ServerFault, but I haven't gotten any responses at all. Since it looks like I'm on track to get the Tumbleweed badge over there, I figured I would try here also.
Our existing public website consists of a mish-mash of asp.net pages with mostly static content and some real web applications that are set up as virtual directories. We're now looking at installing Umbraco, which requires that you install it at the root of the website.
Since the CMS would be at the root of the website, I'm assuming it's a bad idea to run our existing pages and web applications underneath Umbraco (due to the URL rewriting it performs and inheriting web.config settings, etc.) So how do we make everything co-exist peacefully both while we transition to the CMS and after we're finished?
My only idea so far was to set up the CMS and the applications as separate websites and then use some sort of URL rewriting/reverse proxy to make everything resolve correctly:
* www.example.com would keep resolving to our old homepage
* www.example.com/dept1 would keep resolving to the old dept1 page
* www.example.com/dept2 would resolve to the new dept2 page on the CMS
* www.example.com/app would resolve to an existing web application
We ending up setting up Umbraco as it's own website in IIS and then we bought ISAPI Rewrite so that we could seamlessly pass through CMS content for certain URLs.