12Wonder
February 23rd, 2005, 01:57 AM
The magic move is still underway and we expect it will be completed sometime in the next day or two. There are a few known issues we're getting asked about a lot so hopefully this will answer some questions:
1) Add-on domains and url masking:
Until the IP's assigned to the server and name servers are modified and resolve in the name server registry, those of you using add-on domains will find that the URL masking is not automatically working. The site will still be up, but the url will display as http://subdomain.primarydomain.com. If you want to mask things yourself quickly we have a solution:
Go to your cpanel using the new IP url described in #5 below. Go to Subdomains. Click on "Setup Redirection" and choose the subdomain that belongs to your addon domain. This will take you to a page where you can enter the addon domain url. Enter "http://www.addondomain.com/" without the quotes of course, and replacing addondomain.com with your real addon domain name. Be sure to include the trailing slash. This should solve your url masking problem.
Status update 02/24/05: Resolved
2) Add-on domains and email:
Ditto the reason explained above re IP's. Email authentication requires the domain to resolve to the correct IP. Because the sites are virtually 'straddling' servers, email for addon domains is not being properly routed and so gets rejected. This should resolve once the registrys have the correct servername & name server ip's. This is not something you need to do or even can do on your end; it is the IP's which we have assigned to the actual ns1 & ns2 etc. However we cannot change these IP's until all sites are on the new server. This should resolve when the move is complete. Regular email for primary domains on all hosting accounts should already be working normally (unless there is some other reason such as you maxed out your disk space on your own, etc.).
Status update 02/24/05: Resolved
3) FrontPage
a) Publishing with FrontPage: even though your site is still up, you will not be able to publish to FrontPage until those IP's get changed. Same reason as above. You must have a www.domain.com url to publish to, and FrontPage gets 'confused' easily...
b) FrontPage extensions may break. Occasionally a move to a different server will break FrontPage extensions. This is because the sites are moved outside the FrontPage environment. If this happens you should go to your cPanel and click "FrontPage extensions". Install FrontPage extensions; or if it says "installed" already, click "Uninstall" then click "Clean up old extensions" a FEW TIMES (not just once). Then reinstall FrontPage extensions. You will probably have to republish your site via FrontPage to make sure you have everything updated in there.
c) Not being able to see new FrontPage web pages or changes to pages: Since you will not be able to publish to your www url until after the move is complete, not being able to see changes you published is a cache issue with your own computer. FrontPage is pretty fierce about hanging onto cache & temp files. In order for your FrontPage program to recognize the new location of the site, do this: First make sure your FrontPage publish settings are correct. You should be publishing via http, NOT ftp. The location to publish to should be in the form "http://www.yourdomain.com/" with the slash, but of course no quotes. Then close FrontPage. Open a new browser window but do NOT browse to your web page. In your browser clear out your cookies as well as all Temporary Internet Files both online & offline. Shut down your computer for 8 to 10 minutes to let your ram dump, then reboot. Then open FrontPage again and attempt to publish your entire web. This usually does it.
d) When trying to publish via FrontPage you get the error: "Unable to Build Data Connection Data Time Out": This is probably a combination of broken frontpage extensions AND your own computer's cache. The solution that has been working is: First, follow instructions in 3-b above. Then follow the instructions in 3-c above.
4) Not seeing pages online which you know you just uploaded via FTP: If you are NOT using FrontPage and want to upload page via FTP tonight or tomorrow, you can use the new IP we gave you as the hostname (instead of ftp.domain.com). That way you will be sure to be uploading to the new server, which is where your site will eventually be displaying all your files from.
Status update 02/24/05: Resolved. You may go back to using ftp.yourdomain.com for ftp. However make sure you are not using cached information; check the ip in ftp login status notes to make sure you are using the new 72.x.xxx.xxx IP. If you still see the old ip, your computer's cache is interferring and you will need to close your ftp program and all browser windows. Then open a browser window but do NOT browse to your web page or cpanel. In your browser clear out your cookies as well as all Temporary Internet Files both online & offline. Shut down your computer for 8 to 10 minutes to let your ram dump, then reboot
5) Inability to access cpanel: Same kind of Cookies/cache issue mentioned in 3-c above. If you need to access cPanel tonight or tomorrow, use https://xx.x.xxx.xxx:2083 where the x's are the ip number we gave you in your "Server move underway" email we sent out a couole of nights ago.
Status update 02/24/05: You may now go back to using http://www.yourdomain.com/cpanel to access your cpanel. If on the cpanel home page under General Account Information you do not see the new 72.x.xxx.xxx IP (under Hosting Package Name), your computer's cache is still accessing the old server for cpanel. If this occurs, open a new browser window but do NOT browse to your web page or cpanel. In your browser clear out your cookies as well as all Temporary Internet Files both online & offline. Shut down your computer for 8 to 10 minutes to let your ram dump, then reboot.
6) Incorrect amount of total monthly bandwidth usage reported in new cpanel. Yep. Because this is a new server and at a new data center, bandwidth tracking started at zero on the new server. So those of you on magic, even those close to or over your bandwidth limit a day or two ago, get to start the count at a nice fresh zero one week before the end of the month. It will reset to zero again on the first day of March just like the first day of any month. If you were close to your bandwidth limit on the old server, you will still continue to get bandwidth warnings sent out by the old server after every automatic bandwidth check until the end of the month.
7) "Unlimited" disk space showing for your total available disk space quota in cpanel. Just a cpanel glitch we'll be fixing sometime this week. It's not a top priority right at the moment since it should not affect the functioning of anything in the hosting accounts.
Status update 02/24/05: Resolved
8) Fantastico not showing up in cpanel: We have one fantastico license per server. When fantastico is moved from the old server to the new one it will show up in your cpanel again. Should be sometime in the next couple of days.
Status update 02/24/05: Resolved
9) Fantastico programs' admin areas not accessible: Same IP issue as mentioned earlier. Should resolve once the ip's do.
Status update 02/24/05: Resolved
10) Do not make any changes in your cpanel such as adding/modifying email accounts, using File Manager, setting up subdomains or addon domains, etc if you use the old domain.com/cpanel url -- you will be making changes on the old server and they may not make it to the new server in time when the move becomes permanent. For the next few days just use the new IP cpanel url described in #5 above. After the move is complete (we will announce when it is), you can go back to using the domain.com/cpanel url.
Status update 02/24/05: Resolved - you can use http://www.yourdomain.com/cpanel url now. Also see #5 above.
11) 1-2-Wonder Web Services (http://www.12wonderwebservices.com/) web site hanging a maintenance page. Yes we've got that page up for several hours tonight Feb 22/early morning hours of Feb. 23 while our own site is one of the last to be moved from the old magic to the new one. We don't want any orders coming in where half get left on the old server and half end up on the new server. Also, we need to move our SSL certificate for our site to the new server, and orders placed during the move would not be secure until the SSL cert is in place on the new server. We do expect the maintenance page at our site to disappear after a few hours, and the site will show a funky green & orange cpanel page that says "There is no site configured.." etc. for awhile. This is expected until the dns cache catches the update. When all is moved and the ip's have resolved we'll be fully functional again. This is NOT at all what normal accounts on magic have experienced, but we have a few special circumstances with IP's, licenses, certificates, etc. at our 1-2-Wonder Web Services site which make all this other stuff happen with it.
Status update 02/24/05: Resolved/Completed
If anyone still has any questions or needs to get hold of me, I will most likely be pulling an all-nighter (or very nearly so) to monitor everything. You can reach me by email at support@12wonderhosting.com even while the main 1-2-Wonder Web Services site is under maintenance. That email address resides on a totally different server and is unaffected by the move.
Status update 02/24/05: Resolved - you can submit support tickets and email us as usual etc.
Or feel free to post in these forums. Most likely someone else has had, or will have, the same question and your post and its answer/s could be helpful to someone else in future.
Anne
1) Add-on domains and url masking:
Until the IP's assigned to the server and name servers are modified and resolve in the name server registry, those of you using add-on domains will find that the URL masking is not automatically working. The site will still be up, but the url will display as http://subdomain.primarydomain.com. If you want to mask things yourself quickly we have a solution:
Go to your cpanel using the new IP url described in #5 below. Go to Subdomains. Click on "Setup Redirection" and choose the subdomain that belongs to your addon domain. This will take you to a page where you can enter the addon domain url. Enter "http://www.addondomain.com/" without the quotes of course, and replacing addondomain.com with your real addon domain name. Be sure to include the trailing slash. This should solve your url masking problem.
Status update 02/24/05: Resolved
2) Add-on domains and email:
Ditto the reason explained above re IP's. Email authentication requires the domain to resolve to the correct IP. Because the sites are virtually 'straddling' servers, email for addon domains is not being properly routed and so gets rejected. This should resolve once the registrys have the correct servername & name server ip's. This is not something you need to do or even can do on your end; it is the IP's which we have assigned to the actual ns1 & ns2 etc. However we cannot change these IP's until all sites are on the new server. This should resolve when the move is complete. Regular email for primary domains on all hosting accounts should already be working normally (unless there is some other reason such as you maxed out your disk space on your own, etc.).
Status update 02/24/05: Resolved
3) FrontPage
a) Publishing with FrontPage: even though your site is still up, you will not be able to publish to FrontPage until those IP's get changed. Same reason as above. You must have a www.domain.com url to publish to, and FrontPage gets 'confused' easily...
b) FrontPage extensions may break. Occasionally a move to a different server will break FrontPage extensions. This is because the sites are moved outside the FrontPage environment. If this happens you should go to your cPanel and click "FrontPage extensions". Install FrontPage extensions; or if it says "installed" already, click "Uninstall" then click "Clean up old extensions" a FEW TIMES (not just once). Then reinstall FrontPage extensions. You will probably have to republish your site via FrontPage to make sure you have everything updated in there.
c) Not being able to see new FrontPage web pages or changes to pages: Since you will not be able to publish to your www url until after the move is complete, not being able to see changes you published is a cache issue with your own computer. FrontPage is pretty fierce about hanging onto cache & temp files. In order for your FrontPage program to recognize the new location of the site, do this: First make sure your FrontPage publish settings are correct. You should be publishing via http, NOT ftp. The location to publish to should be in the form "http://www.yourdomain.com/" with the slash, but of course no quotes. Then close FrontPage. Open a new browser window but do NOT browse to your web page. In your browser clear out your cookies as well as all Temporary Internet Files both online & offline. Shut down your computer for 8 to 10 minutes to let your ram dump, then reboot. Then open FrontPage again and attempt to publish your entire web. This usually does it.
d) When trying to publish via FrontPage you get the error: "Unable to Build Data Connection Data Time Out": This is probably a combination of broken frontpage extensions AND your own computer's cache. The solution that has been working is: First, follow instructions in 3-b above. Then follow the instructions in 3-c above.
4) Not seeing pages online which you know you just uploaded via FTP: If you are NOT using FrontPage and want to upload page via FTP tonight or tomorrow, you can use the new IP we gave you as the hostname (instead of ftp.domain.com). That way you will be sure to be uploading to the new server, which is where your site will eventually be displaying all your files from.
Status update 02/24/05: Resolved. You may go back to using ftp.yourdomain.com for ftp. However make sure you are not using cached information; check the ip in ftp login status notes to make sure you are using the new 72.x.xxx.xxx IP. If you still see the old ip, your computer's cache is interferring and you will need to close your ftp program and all browser windows. Then open a browser window but do NOT browse to your web page or cpanel. In your browser clear out your cookies as well as all Temporary Internet Files both online & offline. Shut down your computer for 8 to 10 minutes to let your ram dump, then reboot
5) Inability to access cpanel: Same kind of Cookies/cache issue mentioned in 3-c above. If you need to access cPanel tonight or tomorrow, use https://xx.x.xxx.xxx:2083 where the x's are the ip number we gave you in your "Server move underway" email we sent out a couole of nights ago.
Status update 02/24/05: You may now go back to using http://www.yourdomain.com/cpanel to access your cpanel. If on the cpanel home page under General Account Information you do not see the new 72.x.xxx.xxx IP (under Hosting Package Name), your computer's cache is still accessing the old server for cpanel. If this occurs, open a new browser window but do NOT browse to your web page or cpanel. In your browser clear out your cookies as well as all Temporary Internet Files both online & offline. Shut down your computer for 8 to 10 minutes to let your ram dump, then reboot.
6) Incorrect amount of total monthly bandwidth usage reported in new cpanel. Yep. Because this is a new server and at a new data center, bandwidth tracking started at zero on the new server. So those of you on magic, even those close to or over your bandwidth limit a day or two ago, get to start the count at a nice fresh zero one week before the end of the month. It will reset to zero again on the first day of March just like the first day of any month. If you were close to your bandwidth limit on the old server, you will still continue to get bandwidth warnings sent out by the old server after every automatic bandwidth check until the end of the month.
7) "Unlimited" disk space showing for your total available disk space quota in cpanel. Just a cpanel glitch we'll be fixing sometime this week. It's not a top priority right at the moment since it should not affect the functioning of anything in the hosting accounts.
Status update 02/24/05: Resolved
8) Fantastico not showing up in cpanel: We have one fantastico license per server. When fantastico is moved from the old server to the new one it will show up in your cpanel again. Should be sometime in the next couple of days.
Status update 02/24/05: Resolved
9) Fantastico programs' admin areas not accessible: Same IP issue as mentioned earlier. Should resolve once the ip's do.
Status update 02/24/05: Resolved
10) Do not make any changes in your cpanel such as adding/modifying email accounts, using File Manager, setting up subdomains or addon domains, etc if you use the old domain.com/cpanel url -- you will be making changes on the old server and they may not make it to the new server in time when the move becomes permanent. For the next few days just use the new IP cpanel url described in #5 above. After the move is complete (we will announce when it is), you can go back to using the domain.com/cpanel url.
Status update 02/24/05: Resolved - you can use http://www.yourdomain.com/cpanel url now. Also see #5 above.
11) 1-2-Wonder Web Services (http://www.12wonderwebservices.com/) web site hanging a maintenance page. Yes we've got that page up for several hours tonight Feb 22/early morning hours of Feb. 23 while our own site is one of the last to be moved from the old magic to the new one. We don't want any orders coming in where half get left on the old server and half end up on the new server. Also, we need to move our SSL certificate for our site to the new server, and orders placed during the move would not be secure until the SSL cert is in place on the new server. We do expect the maintenance page at our site to disappear after a few hours, and the site will show a funky green & orange cpanel page that says "There is no site configured.." etc. for awhile. This is expected until the dns cache catches the update. When all is moved and the ip's have resolved we'll be fully functional again. This is NOT at all what normal accounts on magic have experienced, but we have a few special circumstances with IP's, licenses, certificates, etc. at our 1-2-Wonder Web Services site which make all this other stuff happen with it.
Status update 02/24/05: Resolved/Completed
If anyone still has any questions or needs to get hold of me, I will most likely be pulling an all-nighter (or very nearly so) to monitor everything. You can reach me by email at support@12wonderhosting.com even while the main 1-2-Wonder Web Services site is under maintenance. That email address resides on a totally different server and is unaffected by the move.
Status update 02/24/05: Resolved - you can submit support tickets and email us as usual etc.
Or feel free to post in these forums. Most likely someone else has had, or will have, the same question and your post and its answer/s could be helpful to someone else in future.
Anne