SWH Server Updates

To my surprise, there are still a few sites whose webmasters have not updated their domains DNS settings to let their sites point to the new server.

Note that we have copied all sites on the old server to the new. But you have to login to your domain registrar to update the DNS settings according to the following nameservers:

NS1.SELFWEBHOSTING.WS
NS2.SELFWEBHOSTING.WS
NS3.SELFWEBHOSTING.COM
NS4.SELFWEBHOSTING.COM

Note that these nameservers are served from different locations so that sites hosted by us can still be visible even though one of these nameservers are down. If your domain registrar does not allow you to enter all four nameservers (they should, but just in case they don’t), then you need to use at least these two nameservers:

NS1.SELFWEBHOSTING.WS
NS3.SELFWEBHOSTING.COM

To test if you are very serious about your website, we are going to suspend all sites on the old server - not deleting, just suspending which can be unsuspended after you contact us.

If your site’s domain has NOT set to point to the new server OR has set but not yet resolved to our new server, you will see an account suspending page when you access your website.

Follow the instructions on the account suspending page to contact us so that we could unsuspend your site on the old server and give you some time to update your domain DNS.

We have made some changes from our side so that the following name servers also point to the new server:

NS1.SELFWEBHOSTING.COM
NS2.SELFWEBHOSTING.COM
DNS1.SELFWEBHOSTING.COM
DNS2.SELFWEBHOSTING.COM
NS1.SELFWEBBUILDING.COM
NS2.SELFWEBBUILDING.COM

Note that we cannot gurantee that they will work right away as we just made the changes recently. At the time of this writing/updating, all six nameservers appear to have resolved to the new server. Also we did this in order to make a smooth transition for your site. We may use these nameservers for other purposes in the future. So please try your best to use the designated nameservers that are given in the beginning of this post.

This means that if you set your domain to point to any of these nameservers, your site should show up from the new server without you doing anything. If not, the changes we made may have not been sensed fully by the entire World Wide Web.

Note that you will see that your site on the new server is NOT as updated as the new server because of the time lag between doman DNS changing/resolving and site transfer. In this case, you can use the following IP-based site URLs to compare the differences and make content updates:

Old server:

http://70.84.139.138/~username (access your site using correct username)
http://70.84.139.138/cpanel (access server control panel)

New server:

http://82.103.130.19/~username (access your site using correct username)
http://82.103.130.19/config (access server control panel)

End Note: Login form for the new server control panel has been incorporated into most pages on our main website at selfwebhosting.ws - here is an example: http://www.selfwebhosting.ws/demo.php
.
.
.

Since we have transferred all sites on the old shared server to our new dedicated server, we are going to shut down the old server in 10 days starting from today.

If you have not updated your domain DNS, please do so now, otherwise one one will be able to access your site even it exists on the new server.

So you need to point your domain to the new server by February 27, 2006.

How to do it? You need to log into your domain registrar and update DNS settings to all four nameservers that were sent to you.

If you need help, please let us know by submitting a support ticket.

Meanwhile, we are redesigning our website here: www.selfwebhosting.ws

We have finished installing our new billing script here: http://www.selfwebhosting.ws/orders and we are in the process of integrating it with our existing affiliate program.

One user reported that Squirrelmail could not be accessed at all. Now we have fixed the problem and you should be able to access both Squirrelmail and UebiMiau webmail from the control panel or directly from your browser. Cheers!

We have copied all sites on the old shared server over to the new dedicated server and we are backing up each site on the new server on a daily basis. We have not detected any Netbus worm yet

Please check your site on the new server using the IP-based URL in your welcome letter to make sure everything works OK. If everything does work OK, please update your domain DNS according to the settings listed in your welcome letter. Please do so as soon as possible.

The old server will still function for another 30 days but we could not guarantee its operation - that was the reason why chose to switch over to the new dedicated server in the first place, remember?

Updating your domain DNS now gives you a chance to examine your site on the new server for 30 days. If indeed there are some minor issues here and there, 30 days are plenty for you to pinpoint these issues and solve them. Any you have your full working site on the old server to compare settings if you do need to refer to it.

After the 30 days have passed (starting from today), we will close down the old server.

So again, if your site was hosted with a Standard package in the past, that means that it is on the old shared server and we have already copied your site over to the new dedicated server. But we need you to make the DNS changes so that your domain will point to your site on the new server.

Note that for sites hosted with the Advanced package, they are already on a dedicated server. So no need to change anything whatsoever.

If you do not understand what this means, please submit a support ticket through one of the following links:

(1) Control Panel on the new server:

http://82.103.130.19:2222/CMD_TICKET?domain=yourdomain.com

Make sure to replace yourdomain.com with your own domain. The login info have been given to you in the latest welcome letter sent to your email in our record from the server.

Make sure your contact email address is set correctly by clicking the “Site Summary / Statistics / Logs” link right after login. This is the email address the system uses to send a copy of your ticket update.

If for any reason the above support link does not work for you, please use this one…

(2) Presale Support Desk:

http://www.helplogin.com/ticket/open.php

This is meant for general public who have not signed up for any services with us to submit a question. You should definitely use this one if nothing else works for you.

Direct email contact works but we cannot guarantee your email will reach us. Use one of the above ticket systems can allow us to track and update your ticket easily. And each ticket system sends a copy of new update to your email as well. Thank you for your understanding on this.

Lastly, we highly recommend that you subscribe to the RSS feed of this blog as we use it to post any updates related to your site and our server. We will try to email you important updates but as we said email is not a guaranteed way to commnicate during the increasing problem of email spamming and filtering.

So if you care about your site and our server, please subscribe to the RSS feed of this blog. Do it now if you have not. If you do not know how, please read this post:

http://selfwebhosting.com/update/3/how-to-subscribe-to-the-rss-feed-of-this-blog

All the best!

As you can see from here:

http://selfwebhosting.com/update/11/site-transfer-order/

We have finished all the server-side intallations (OS, control panel, site builder, script autoinstaller, etc.) however the site transfer is only half done. The reason being that we are transferring one site at a time (to monitor which site might carry the Netbus worm) and we do it manually without using any site transfer script.

We are proposing a faster site transfer plan and we need your help…

We are going to set up a hosting account for each of the following domains:

1. chinasprung.com
2. hereisillinois.com
3. mooganinzambia.com
4. jeranon.com
5. nsonzi.com
6. kenten.com
7. tierpal.com
8. vince-coleman.com
9. kindacheezy.com
10. harmonicaresources.com

You will receive a welcome letter from our system whenever your account is created on the new server.

IF (yes it is a big if), you are like me in keeping a most upated copy of your site on your own computer, you can start uploading your site and setting up your email account(s) as soon as you receive the welcome letter. The FTP address for the uploading is the same as the shared IP address you receive in your welcome letter.

PAY ATTENTION TO THIS: IF you do not know how to do it or you do not have a copy of your site on your local computer, then we need you to login to the control panel as soon as you receive the welcome letter from our new server. Then you click the “Support Center” link under “Your Account” to submit a support ticket to request us to do the site transfer. Without specificly requesting for our help, we will not do the transfer for you until after the end of January.

So you have a week to decide on this matter. We require you to submit a support ticket in order not to create a conflict between you and us in terms of who is doing the site transfer during this period.

This also gives you an opportunity to decide if you would like to rebuild your site with siteZen site builder which is included automatically in your account. Since using siteZen site builder will overwrite files in the public_html folder, it is better to start fresh. This builder works with an IP based URL and it does not require your domain’s resolving to the new server as long as you do not publish it. So if you DO want to use the siteZen builder to build your site on the new server fresh, then you need to follow these guidelines:

(1) DO NOT update your domain DNS - let the general public access your existing site on the old server while we build your site on the new server.

(2) SAVE what you build with siteZen builder (from an IP-based URL) but DO NOT publish the content.

(3) Update your domain DNS and wait till it fully resolves to the new server and then login to your site builder and click the “PUBLISH” button.

Since most of you are very experienced webmasters, the do-it-yourself approach should speed up the site transfer process tramendously. However, please abide the following guidelines in uploading your site content…

(1) DO NOT upload the old server’s site backup file to the new server.

Yes, extracting your site content from this backup file saves you the hassle of having to examine and change the permission setting for each file, but it also carries over all the hidden files that exist on the old server.

So the bottom line is, unless you know how to remove these hidden files, do not take this route.

(2) DO NOT upload files located outside the public_html folder.

The new server uses DirectAdmin as the control panel and the old server uses cPanel. This means that the two systems have a complete different setup in terms of file/folder structure.

Luckily, the public_html folder on the new server functions the same as the old server. This means that as long as you upload files in the public_html folder on the old server to the new server’s public_html folder for your account, everything works fine.

(3) Please DO contact us if you need help to restore MySQL databases and make them work with your PHP or CGI scripts.

This is the hardest part of restoring your site on the new server and it does require some basic knowledge as to how MySQL works and how scripts interact with MySQL.

So hope this works better and faster. If you have any concerns about this approach, please do not hesitate to contact us or simply add a comment to this posting.

NOTE: PLEASE SCROLL DOWN FOR THE STATUS OF THIS TRANSFER…

OK, just let you know how we are going to do it this time for the site transfer from the shared server to the dedicated server:

(1) We won’t copy your site from compressed backup, but directly do file to file transfer using FTP to ensure no hidden files get transferred.

(2) We will copy static html and image files first and then rebuild scripts and databases needed according to the active ones that are using - many people simply tried installing a script and then abandoned it without deleting files associated. Some leave 777 permission setting for certain files and even folders - this is dangerous!

(3) We are going to transfer site one by one. By this I means we will work on one site only until we are sure it is fully working on the new server (inlcuding working after domain DNS update and resolving), then we move onto the next site. This gives us the chance to pinpoint the issue when it occurs.

This method also speeds up the transfer time as far as a particular site is concerned.

Note that your site on the shared server is fully working and we will not remove it from it until YOU and WE are absolutely sure there is no need for it. So just treat if as a fully functioning site (it is!) and keep updating it. We will contact you when it comes for us to copy your site onto the server. Then you can take a rest and let us do the transfer and continue update your site content when it is fully working on the new server.

Again, we are not going to rebuild your site on the new server based on earlier backup copy, but directly from your existing server. We do this to make sure nothing is missed during the transfer.

Here is a list of what we do on the server and the order of sites we are going to do the transfer work on (in the order of ease):

(A) Reinstall of OS for the server (DONE!)
(B) Reinstall of DirectAdmin control panel (DONE!)
(C) Reinstall of billing script (DONE!)
(D) Reinstall of siteZen site builder (DONE!)
(E) Reinstall of Installatron script autoinstaller (DONE!)

1. paceoilfieldhauling.ca (DONE!)
2. harmonicaresources.com (DONE!)
3. cochranephotography.net (DONE!)
4. ruminzhang.net (DONE!)
5. actionzambia.org (DONE!)
6. artreagous.com (DONE!)
7. ascensionlutherancalgary.com (DONE!)
8. burials-at-sea-by-captain.com (DONE!)
9. chinasprung.com (DONE!)
10. davesdelights.com (DONE!)
11. hereisillinois.com (DONE!)
12. mooganinzambia.com (DONE!)
13. jeranon.com (DONE!)
14. nsonzi.com (DONE!)
15. kenten.com (DONE!)
16. tierpal.com (DONE!)
17. vince-coleman.com
18. kindacheezy.com (DONE!)
19. shaneh.org (DONE!)

If your site is not listed, it is most likely on our Advanced package which is hosted already on a dedicated server - so do not worry.

We have a big problem with the new server!

After transferring all accounts over to the new server, we find that some worms get transferred together with our client accounts. While it is very hard to locate every one of them, the data center suggests that we must reinstall everything and not use any script to do server to server transfer. What does this mean?

(1) Don’t update your site DNS to this new server.

If you have done it already, then you need to change it back to:

NS77.WEBSITEWELCOME.COM
NS78.WEBSITEWELCOME.COM

This ensures that your site is visible from the old server. Very important!

(2) We will redo everything from beginning and transfer each site manually :-(

(3) We will not recreate scripts that may carry worms.

After the data center (for the new dedicated server) had finished the scheduled network maintenance, we had a problem with the siteZen site builder script installed on the server. Since this script is installed on the root level, we needed to reboot the server while we were fixing the problem.

Now the problem has been resolved and we have basically finished installing all scripts from the root level. This makes us to announce the next step - updating your site’s DNS servers!

In order to ensure the DNS update is smooth and fast, we need you to do it from your side. This is what you do:

(1) Login to your domain manager (where you purchased your domain name)

(2) Pick the domain that is hosted with us - this is done by putting a check mark in front of the domain and then clicking the “Set Nameservers” button if your domain registrar is MegiWeb or GoDaddy.

(3) Now enter the following custom name servers that will point your domain to the new server:

NS1.SELFWEBHOSTING.WS
NS2.SELFWEBHOSTING.WS
NS3.SELFWEBHOSTING.COM
NS4.SELFWEBHOSTING.COM

Make sure you enter all four name servers as they are located at several geophysical locations in the world to ensure your domain resolves properly and quickly to our server even after a server downtime.

Note that we have not touched your site on the old shared server. This means that even your domain has not resolved to the new server, your site is still available for everyone to see - they will not notice any difference!

Give the DNS change at least 24 hours to resolve to the new server. During this time, it is not a good idea to add contents to your site using a domain based URL. Use these IP-based URLs instead:

OLD SERVER (in case you want to grab something there):

Your site access: http://70.84.139.138/~username/
Control panel login: http://70.84.139.138/cpanel
FTP: 70.84.139.138

NEW SERVER (your site’s new home):

Your site access: http://82.103.130.19/~username/
Control panel login: http://82.103.130.19/config
FTP: 82.103.130.19

In order not to miss any emails that you will receive after you initiate the DNS update but before your domain actually resolves, check your emails at both servers - by logging into the control panel rather than using your email client program.

How do you know your site has resolved to the new server?

A simple method is to make a minor change to the home page of your site at the new server - so minor that only you can notice it. Then once a while after you make the DNS update, check your website (using the domain-based URL of course) to see if you are able to see the change.

I would like to use this opportunity to introduce to you several functions of the DirectAdmin control panel (including some usefull plugins):

Note that we give the IP-based URLs here . Once your domain resolves to the new server, you can replace the IP in these URLs with your own domain name. For example, an IP address like this:

http://82.103.130.19:2222/CMD_TICKET?domain=yourdomain.com

will become this after your domain resolves:

http://yourdomain.com:2222/CMD_TICKET?domain=yourdomain.com

Or simply this: http://yourdomain.com:2222/CMD_TICKET

Now the functions…

(1) Support Center
http://82.103.130.19:2222/CMD_TICKET?domain=yourdomain.com

This comes with the DirectAdmin control panel and is located right under “Your Account” after control panel login (or can be accessed directly using the URL above).

This will be used for us to support our existing customers for technical issues. Please use it to submit any support ticket as email is not reliable and is hard to keep track.

(2) siteZen Site Builder:
http://82.103.130.19/zen (before domain resolves)

We have enabled your site to use it without extra charge. The login info is the same as your control panel login.

You can play with it until the end of this month - we now only have an evaluation license right now. By the end of January this year, we will disable siteZen from
all accounts unless we receive a specific request to keep it - by then we will have to pay for a commercial license.

(3) Installatron
http://82.103.130.19:2222/CMD_PLUGINS/iTron

This is a DirectAdmin plugin we purchased and it is basically an script autoinstaller similar to Fantastico in cPanel. It allows you to install most popular scripts with a few clicks.

To know other functions of your DirectAdmin control panel for your site, please go to this wonderful site explaining every aspect of this new control panel:

http://www.site-helper.com

So much for this comminication. In the next few days we will be building our main site at

http://selfwebhosting.ws

We will also install a billing script and upgrade/integrate our existing affiliate script with this new site. By that time we will add a reseller hosting package which is fully commissionable for all affiliates.

After completing server to server transfer for sites in the Standard package, we have logged into each individual site to fix followings that were not handled properly by the site transfer script:

(1) Passwords for protected direcotries (if any)
(2) Passwords for MySQL databases (if any)

Now we have done what we can from our side and we are ready to proceed to the next step - update DNS servers for these sites!

But we will wait until the network maintenance is completed. Yes, this afternoon starting from 16:00 to 16:30 (MST, Mountain Standard Time), we will preform scheduled network maintenance. If you have already pointed your site to this server, you may experience short network outages during the given timeframe.

So if you do not know the DNS servers for this new server, do not ask for them until we finish our network maintenance at the data center.

We had some problem using a server script to transfer accounts on the shared server to our new dedicated server. That explains why our future main site (selfwebhosting.ws) was down starting yesterday evening. Now we have fixed the problem and all hosting accounts have been transferred to the new server!

If you are our existing customer, you will receive email from me shortly telling the IP address from which you can login to your hosting account control panel to see if everything is alright.

We will give you a few days to examine the transfer. If everthing is fine, then we will give you instructions as to how to update your domain DNS - we have investigated our earlier proposal of updating name servers from our side (so you do not have to do anything), but this proposal does not work for some sites. So to make things easy in the future, we require that you update your site’s DNS to the new server. You do not have to do it now - we will do it together when everyone is happy with the transfer we did from our side.

We have upgraded your account for the following settings - I am sure you are going to like it

Bandwidth: 10 GB / month
Disk Space: 2 GB
Addon Domains: 10
Sub-Domains: Unlimited
Email Accounts: Unlimited
Email Forwarders: Unlimited
Mailing Lists: Unlimited
AutoResponders: Unlimited
MySQL Databases: 25
Domain Pointers: Unlimited
Ftp Accounts: Unlimited
Anonymous Ftp Accounts: Yes
CGI Access: Yes
PHP Access: Yes
SpamAssassin: Yes
SSL Access: Yes
Cron Jobs: Yes
System Info: Yes

Please check your inbox for my email.