30 Jan

Important Announcement – Server Migration – hera.ihostman.com

We would like to inform you that we have moved our server with hostname hera.ihostman.com” to new hardware. The migration is already completed. We have also updated the nameservers IPs so that all active clients gets new server as soon as possible.

Below is the server hardware details:
====================================
Processor: 3.5ghz Hexa-Core E5-1650 V2 Ivy Bridge Xeon
Memory: 64gb Ddr3
Primary Hard Drive: 960gb SSD
Second Hard Drive: 2TB SATA HDD
Public Connection: 1GBPS
====================================

As you can see we have moved to Solid State Drive which will give faster data transfer for our client. This server is four times stronger then our previous server and we expect our clients will have more smooth service from this server.

New Server Shared IP: 104.156.55.181

Our clients are requested to use IP URL to access cPanel, Webmail and WHM to avoid any confusion until the DNS propagation is completed on your end. Please ping your domain and if it shows the new IP, it means the propagation has completed on your end. Clients are also requested not to update the MySQL Databases for next 48 hours, once the propagation is completed on your end, you can update else you might face data loss.

Login URLs:
===========
WHM: http://104.156.55.181:2086
cPanel: http://104.156.55.181:2082
Webmail: http://104.156.55.181:2095
===========

We have done our best to move every single data from our old server to new server so we expect all site will work fine and there will be no data loss. But if you face any problem with your site loading or see data loss please contact our support desk by sending email to following address: support@tetrahostbd.com or visit the following URL: http://www.tetrahostbd.com/contact

We appreciate your patience during this work and welcome any feedback.

 

Thank you,
Network Engineering, TetraHost

04 Aug

Scheduled Maintenance – Server Replacement/Upgrade – hera.ihostman.com – 09/08/2013 or 10/08/2013

This is a important technical alert from TetraHost. You may be affected by this announcement if you have a shared or reseller hosting account with TetraHost. Please review the following information.

Platform: Linux
Server: hera.ihostman.com
Server Primary IP: 50.97.95.98
Scope of Work: Server Replacement / Upgrade
Reason: Server has reached end of service life
Time: Ongoing from 09/08/2013 or 10/08/2013
Start Time: 12:00 AM GMT +6
End Time: 10:00 PM GMT +6
Duration: 22 hours
Services affected: Public Access to site

We are currently upgrading all of our cPanel Linux shared and reseller hosting servers. This is being done to increase performance and remove older server equipment from our network which has reached the end of its service life. Over the past few weeks we have noticed that the server performance has gone down to a bit. It is also creating some high load on the server when it tries to run High IO task. We do not want our client to face low performance with their hosted site on TetraHost. This is why we will be moving the server to a better hardware.

The new setup is going to be great. Here is our new server configuration:

Data Center: Dallas, Softlayer
Processor: Single Processor Quad Core Xeon 1270 – 3.50GHz (Ivy Bridge) – 1 x 8MB cache w/HT
Operating System: CentOS 6.0 (64 bit)
Ram: 16GB DDR3 1333
Disk Controller: SATA RAID 10 Disk Controller
Hard Drive: 4 x 1TB on RAID10
Uplink Port Speeds: 100Mbit

As you can see above, we will be using the latest server processor which is Ivy Bridge. The server RAM is also upgraded from 8GB to 12GB. This time TetraHost will be having a new server hardware which is RAID10. RAID will make the server data transfer faster and will secure our clients data.

We do not anticipate any interruption to service while this migration takes place but as it involves a change of IP address, client may not be able to access their site for sometime. If the name servers for your domain name(s) are not set to TetraHost name servers (specifically ns5.ihostman.com and ns6.ihostman.com), the DNS records will not be updated automatically. In which case you will need to update your DNS records manually via your DNS provider. The nameserver domain which is registered by TetraHost will be changed from our side. If your accounts is assigned a dedicated IP and your name servers do not point to ours, please contact us to find out the new IP your account will be given.

We appreciate your patience during this work and welcome any feedback.

Thank you,
Network Engineering, TetraHost

13 Apr

Global Brute Force Floor Attack on WordPress Sites

As I write this article, there is an on going and highly distributed, global attack on WordPress installations across virtually every web host in existence! This attack is well organized and again very, very distributed. The attack can be called as “brute-force” attack as well. Due to the nature of the attack, memory consumption on targeted servers has increased. In certain cases, this has resulted in degradation of performance!

At this moment, we highly recommend you log into any WordPress installation you have and change the password to something that meets the security requirements specified on the WordPress website.  These requirements are fairly typical of a secure password: upper and lowercase letters, at least eight characters long, and including “special” characters (^%$#&@*).

The main force of this attack began last week, then slightly died off, before picking back up again yesterday morning.  No one knows when it will end. TetraHost started a thread on a popular forum where web host owner’s is sharing their experience with the attack and solutions. Here is the thread.

We are taking several steps to mitigate this attack throughout our server farm, but in the same breath it is true that in cases like this there is only so much that can actually be done. Again, this is a global issue affecting all web hosts. Our hope is that this attack ends soon, but it is a reminder that we must all take account security very seriously.

To ensure that your customers’ websites are secure and safeguarded from this attack, we recommend the following blog article and apply the security protection ASAP:

https://blog.tetrahostbd.com/2012/01/31/wordpress-protection

Other ways of Hardening a WordPress installation are shared here at:

http://codex.wordpress.org/Hardening_WordPress

The TetraHost support team has been hard at work with fighting the situation! We’ve taken proactive steps to reduce the impact of this event. We thank you for your patience.

Having trouble? You can always file a ticket at support@tetrahostbd.com.

20 Jan

New Server Configuration

As promised before im here to let you know about our new server configuration.

Here it is:
======================
Processor: Intel Xeon-SandyBridge E3-1270-Quadcore [3.4GHz] | More Info
Motherboard: X9SCI-LN4F Intel Xeon SingleProc SATA
RAM: 8GB – Hynix DDR3 2x4GB DDR3 x8
Hard Drive: 1 TB HDD – 2 x 500 GB Western Digital WD Caviar RE4
Uplink Port: 100 MBPS Dedicated Port
OS: CentOS 6.0-64 Bit
Control Panel: Latest cPanel/WHM

Server Main IP: 50.97.95.98
Datacenter Physical Location: Texas, Dallas
Datacenter Name: Dallas 5, Server Room 02
Datacenter: Softlayer, USA.
======================

Here is some picture of our Datacenter from Softlayer’s Flickr Album:

DC Build Week 1
DC Build Week 2 & 3
DC Build Week 5 & 6
DC Build Week 7
Softlayer’s new HQ and DC Completed
Dallas 05

Enjoy the lightning fast service with our new server!

18 Jan

Server Upgrade

As you know already, our main server which is “hera.ihostman.com” will be moved to a better hardware. We have already ordered the new server from our Datacenter which is Softlayer, USA. The new server physical location is Texas, Dallas. We have chosen Dallas location because the connectivity from Bangladesh is fast then any other location. We will inform you about the new Server Configuration very soon via our blog post.

We are expecting to start the transfer process from 20th January, 2012 at mid-night 12.00 AM(GMT +6). Please note, We do not expect any downtime during the transfer process. We will take every steps to keep all our client account up and running smoothly/properly.

To make the process faster, we may take down the following two service for 24-48 hour:

1. cPanel
2. FTP Server

So, while both the service set to down, user will not be able to access cPanel or upload any file to server using FTP. It is also recommended not to update any site while we ran the transfer process to avoid any file missing issue. Please note again, HTTP service or Web Access will stay up during this process.

We are expecting to complete the transfer process in 24hours time. As soon as the transfer process is completed, we will update the DNS Server.

*** Update regarding the transfer process will be informed via our blog post.

We hope to have your full co-operation during the transfer process.

 

Regards,
NOC, TetraHost

06 Apr

Uptime Report, March’2011

Here we are attaching the uptime report of “hera.ihostman.com” server for the month of March’2011. As you can see there was only 5 minute downtime recorded which caused while we were rebooting the server after successfully upgrading the kernel of this server.

Server Name: Hera (hera.ihostman.com)
Month: March
Monitor Period: 1min interval
Downtime Reason: Kernel Upgrade
Uptime Monitor Site: http://www.pingdom.com/reports/o8tg5oi83rib/Uptime Report, March’2011

06 Apr

Uptime Report, February’2011

Here we are attaching the uptime report of “hera.ihostman.com” server for the month of February’2011. As you can see there was 22 minutes downtime recorded which caused mainly while we were rebooting the server after successfully upgrading the kernel of this server.

Server Name: Hera (hera.ihostman.com)
Month: February
Monitor Period: 1min interval
Downtime Reason: Kernel Upgrade & Small Datacenter Network Outage
Uptime Monitor Site: http://www.pingdom.com/reports/o8tg5oi83rib/Uptime Report, February’2011

28 Feb

Uptime Report, January’2011

Here we are attaching the uptime report of “hera.ihostman.com” server for the month of January’2011. As you can see there was 17 minute downtime recorded which caused while we were rebooting the server after successfully upgrading the kernel of this server.

Server Name: Hera (hera.ihostman.com)
Month: January
Monitor Period: 1min interval
Downtime Reason: Kernel Upgrade
Uptime Monitor Site: http://www.pingdom.com/reports/o8tg5oi83rib/

Uptime Report - January, 2011

02 Dec

Datacenter Scheduled Maintenance – Short Notice – Hostname: hera.ihostman.com – 12/05/2010

Datacenter Scheduled Maintenance – Short Notice – Hostname: hera.ihostman.com – 12/05/2010

Date: Sunday, December 5, 2010 (12/05/2010)
Start time : 12:00 PM
End time : 02:00 PM
Services affected: All Hosted website at server hera.ihostman.com.
Location: Washington DC Duration: 1 hour (Expected to complete the maintenance within 15-20min)

==================================================
Our Datacenter which is SoftLayer, Their Engineers will be performing a short notice IOS upgrade on FCR01.WDC01(Code name of our Washington Datacenter, where our server is located) to correct intermittent issues resulting in packetloss and latency for customers behind this router. This maintenance will take place on 12/05/2010, between 12:00 PM – 2:00 PM (GMT +6) .

During this maintenance, customers on hera.ihostman.com will notice a complete loss of connectivity to their website on the frontend network (public network). While the upgrade duration is scheduled for 1 hour, we only expect between 15-20 minutes of downtime as the router reloads and fully converges.

This maintenance will impact any website hosted on Hera Server(hera.ihostman.com)/ or having nameservers as ns5.ihostman.com & ns6.ihostman.com. Services of Devils Server(devils.ihostman.com) will not be impacted by this.
==================================================

If you have any problems after this time frame with regard to connectivity to your website, or if you have any questions regarding the maintenance at any point, please open a email/ticket in the customer manage portal or contact our support via phone.

Support Email: sales@tetrahostbd.com / support@tetrahostbd.com
Support Phone: +88 019 13377417

We appreciate your patience during this work and welcome any feedback.

Thank you,
Network Engineering

17 Aug

The Art of Troubleshooting Thyself!

TetraHost often receives tickets from our clients who claim that their website is not accessible. However, most of the time it turns out that the issue is actually at the client’s side itself. So in this blog we try to help you to run some self diagnostic tests which will equip you to figure out whether the issue is at your side before opening a support ticket.

Note: It is recommended that you check Network Issues page on your Clientarea so that you will get notified whenever there is an ongoing server/network related issue. TetraHost staff will post a report when any issue is detected by our 24/7 monitoring system. If you do not find any new topic after a few minutes, please go through the following steps to check whether the issue is at your side:

1) Check using third party monitoring services:

There are several website monitoring services available that can check whether your website is up or not. Most of them can also check it from multiple locations across the world. Some of the services that allows free website monitoring checks are:

http://www.alertra.com/spotcheck.php
http://www.hyperspin.com/en/quicktest.php
http://www.watchmouse.com/en/checkit.php
http://www.siteuptime.com/users/quickcheck.php

If the third party monitoring services are also reporting your website as down, please open a Support Ticket in our Help Desk. However, if they are reporting your website as “UP”, the issue is likely at your side itself. Let us see how we can further troubleshoot the issue at your side.

2) Traceroute:

The next step to diagnose the issue is to run a Traceroute command from your windows PC to your domain name. Trace route is a network utility that traces the path taken by your network to reach a host. It shows all nodes the packet travels from sender to destination (also reffered as “hops” in the network), the domains if available, IP addresses and the amount of time in milliseconds that took the reach that specific host. To run a traceroute command, you can do the following steps:

a) Assuming that you are using a Windows PC, click Start > Run
b) Type: cmd (and Press Enter)
c) Type the traceroute command at the prompt: tracert yourdomain.com (and press Enter)
d) Wait for a few seconds for the traceroute command to complete. Once the traceroute is completed, it will show “Trace Route Complete”.
e) To copy the trace route result, right click the Command Prompt window and click on “Mark”. Now drag and select the result to highlight it and press Enter to copy it.

Paste and Save this information in a text file which you can attach when submitting a Support Ticket later.

* If the trace route shows a “Unable to Resolve Host” message, it is likely to be a DNS issue at your side. You may be having a DNS cache or your ISP’s DNS server aren’t updated yet. In such cases, you can try flushing your DNS cache or you can use third party DNS addresses from OpenDNS, etc. to resolve this issue.

* If the trace route result shows “Request Time Out” within your ISP’s network range, it is likely that your ISP is having issues and you may have to contact them regarding this issue along with the traceroute result.

* If the trace route result shows “Request Time Out” towards the end (just before reaching the server), it is likely that your PC’s IP Address is blocked in the server’s firewall. Please open a Support Ticket in our Help Desk to get your IP unblocked from the firewall along with the trace route result and your IP address.

The above troubleshooting tests will help you find and resolve issues at your side quickly without the need for contacting us through the Help Desk. If there is an ongoing issue reported at our side, then it will be posted in the Network Issues area. In such cases, please do not open a Help Desk ticket as it would delay our efforts to bring back the server online since we will have to attend to your ticket at the same time. Please refresh the Network Issues page or subscribe to the topic to receive an email notification when there is an update.