[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 112: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 112: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 112: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 4752: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3887)
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 4754: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3887)
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 4755: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3887)
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 4756: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3887)
Our migration to Bluehost is now complete! : Announcements • SCEPCOP Forum
View Active Topics          View Your Posts
Switch to desktop style
Announcements and site updates.
Post a reply

Our migration to Bluehost is now complete!

18 Apr 2014, 08:01

Announcement:

Our hosting on Godaddy is expiring in a few days. Now is the time to move to , which I've been meaning to for the last three months but never had the time. So I will be starting the migration process now.

This is the first time I've ever moved a site to a different webhost, so I don't know how much downtime there will be. Hopefully little or none. I am paying Bluehost $99 to move all my sites and content over to their servers since I don't know how to do it. They said that the process could take between 24 and 48 hours. Hopefully the transition will be smooth and not noticeable.

After we move to a shared Bluehost server, I will have them begin the migration to a VPS (virtual private server) as I planned months ago. On a VPS, we will have a dedicated IP address and be on a private server, which should in theory raise our ranking and credibility in Google and increase our traffic. One of my friends did this and his website traffic doubled afterward.

Hopefully, this will improve the performance of this site too, as Bluehost has higher quality servers and less downtime. Have any of you experienced any downtime or lags on this forum lately?

Anyway, I will keep you all updated. If you experience any downtime in the next few days, you will know why. Thanks for your attention.

Sincerely,
Winston

Re: Attn: We are moving to Bluehost. Possible downtime.

18 Apr 2014, 08:05

One more thing.

In the next two days during the migration (or until I let you know that the migration is complete) please SAVE all the new forum posts that you post in an offline file such as Notepad or MS Word so they don't get lost.

The reason is because during the migration, this entire site and forum will be copied to Bluehost's servers. This means that a copy will still remain on Godaddy's servers, until the domain name's DNS is pointed to Bluehost.

So if you post something in the forum, and it goes into the version on Godaddy's servers, and then the domain name DNS gets pointed to Bluehost servers, your post may be lost if it is posted AFTER the migration is done, but BEFORE the domain name DNS gets re-routed.

You see what I mean?

So just in case, in the next two days, please save all your posts offline in Notepad or Word. That way, if it gets lost, you can simply repost it by copying and pasting.

Thanks,
Winston

Re: Attn: We are moving to Bluehost. Possible downtime.

18 Apr 2014, 10:41

The Easter break is probably a good time to do it, as many ppl will be on holiday and distracted anyhow. Apart from the obvious metaphor of the site dying and being resurrected over 2 days at Easter....

Re: Attn: We are moving to Bluehost. Possible downtime.

19 Apr 2014, 08:02

Re: Attn: We are moving to Bluehost. Possible downtime.

27 Apr 2014, 15:52

Update:

The Bluehost migration team and I are still working out the problem of migrating my email accounts from Godaddy to Bluehost. I didn't know it was this complicated. Their support team sometimes give me incomplete answers too, so I have to ask the same question several times. I'm not sure if the email accounts can be moved now. Or if they have to move everything all at once.

So the migration hasn't started yet. I'll let you all know when it does, so you can save your posts.

Re: Attn: We are moving to Bluehost. Possible downtime.

28 Apr 2014, 02:40

Attention:

I've just been told by Bluehost support that the migration has just begun. Please SAVE all your new posts that you are writing and submitting in an offline file starting NOW until I tell you that it's done. I'm not sure how long the migration will take.

If you don't, the posts may be gone if they were submitted after the forum database has been migrated over. If that happens, you can just repost them, as long as you saved them first.

Thanks for your attention.

Re: Migration to Bluehost has begun. Please SAVE all your po

28 Apr 2014, 22:09

Wait. Scratch my last post about saving your posts.

I have a better idea. After the migration, before I change the nameservers of this site to Bluehost, I'll just lock this forum so no posts can be made. Then I'll change the nameservers and back up and download the database of the forum and then upload it to the new hosting server at Bluehost. That way, the forum will be locked from posting until the migration and nameservers are complete.

I will place a message at the top of the forum when it is locked to explain what's going on.

However, after I change the nameserver, I'm not sure if the re-routing to Bluehost servers will be immediate or take a few days. I'll have to ask about that.

Man this is so complicated and confusing.

Re: Migration to Bluehost has begun. Please SAVE all your po

01 May 2014, 14:45

scepcop is risen

I think you would have had to lock the forum before the db migration commenced to prevent losing posts? volume of posting isn't high anyhow...

Re: Migration to Bluehost has begun. Please SAVE all your po

02 May 2014, 11:12

Re: Attn: We are moving to Bluehost. There may be downtime.

18 May 2014, 04:44

My friend has a better idea:

I lock this forum, back it up and upload the new version to the new server, then make the DNS changes and unlock the forum on the new server. That seems the best solution.

But this means that some members here may not be able to access the forum for 24 to 48 hours though, if their computer does not recognize the DNS changes. It's a necessary consequence.

I'll let you all know when all this begins.

Re: Attn: We are moving to Bluehost. There may be downtime.

18 May 2014, 04:45

Attention Everyone:

I'm going to change our nameservers to Bluehost sometime today and then migrate the forum database there. When I do this, I will have to lock this forum, or else whatever you post will go onto the old server and be lost. While the forum is locked, the database of the forum will be migrated to Bluehost to make sure that all posts are retained.

After the nameservers are changed, it may take up to 24 hours or more for all the servers in the world to register the change and update to the new server at Bluehost. What this means is that while your server is registering the nameserver change, you may be locked out of the forum for up to 24 hours. It depends on how fast your server updates the nameserver change. For some of you, the lockout may only be for a while, but for others, the lockout could last up to 24 hours or more.

When the forum is locked, I will put a big bold message in red at the top of the forum to explain what's happening.

If the lockout occurs while you are trying to submit a post, then click the Back Button on your browser and then copy and paste your post into a text file to save it to post later.

Thanks for your patience.

Sincerely,
Admin

Re: Attn: Forum will be locked during migration to Bluehost

12 Jul 2014, 18:46

ATTENTION:

The forum will be locked sometime today while we migrate the database to our new server at Bluehost and redirect the domain nameservers there. The purpose of the lockdown is to prevent any new posts from being lost during the migration. The migration could take from 2 to 6 hours or more, depending on how long your ISP registers the nameserver change. If you try to submit a post just before the lockdown, press the back button on your browser and copy and paste your post into a text file to submit later. Your post should still be there when you press the back button. Thank you for your patience. We apologize for the inconvenience.

Re: Attn: Forum will be locked during migration to Bluehost

12 Jul 2014, 21:10

Re: Attn: Forum will be locked during migration to Bluehost

13 Jul 2014, 09:28

Whew it's finally done. Well that was fast. I didn't know the domain nameservers would redirect to our server on Bluehost so fast. It only took about an hour for me. I was told it could take 24-48 hours. I guess it depends on where you are. Maybe since Bluehost's servers are in Utah and I'm in Las Vegas, I'm in close proximity to them, and so the nameserver change propagated for me right away.

Anyhow, if you see this post, it means that your ISP has registered the nameserver change too, since I am posting this on our Bluehost server.

Hope you all have a smoother experience on the forum now that we are on Bluehost's servers, which are supposed to be better.

From here, we will be moving to a VPS (virtual private server), which is like having our own private server, instead of sharing it with many other sites. This should give us better ranking on Google and thus more traffic and popularity as well. So we have a bright future to look forward to. :)

Btw, if you've changed your avatar in the last two months, you will notice that the changes are lost. This is because the avatars are not contained in the forum database. They are in the forum files which were migrated two months ago. So if you changed your avatar in the last two months, you will have to re-upload it. Sorry for the inconvenience.

I'm so glad this is finally done. I feel like a huge weight has been lifted off my shoulder, as I've been trying to figure out how to do this for a long time now, and felt stressed out about it.

Re: Our migration to Bluehost is now complete!

13 Jul 2014, 16:07

Ok I'm going to try to download the avatars from the old server and upload them to the new one, so you guys won't have to re-upload them. I have no way of mass uploading files to the new server yet though, because Windows FTP won't connect to the new server yet for some reason. I might have to use an FTP client. But I'll try.
Post a reply