M8Solutions.com Poor Experience
Jun 3, 2008
I would like to start off by saying M8 has always maintained an excellent uptime, HOWEVER, support has been a nightmare to work with and responses take forever. What prompted me to send this was our sites have been down for over 3 hours so far and you cannot contact anyone by phone and when you email there is no response.
After realizing that a response was going to take a while we decided to try a few things on our own and It appears as though we have been blocked by their firewall or something because we can access the sites via a anonymous proxy. We are still waiting for this issue to be fixed.
Why were we blocked ? Read on
We asked them about a week ago to update our instance of Sugar CRM and we told them that shortly we will be moving another domain to them and when we do this we will want to move our version of sugar.
They did the upgrade (again, response time was horrible), when it was done we went to our URL and found that it had never been updated. I asked them about this and I found out that they moved it to a new service and that the url we were using would not work with all the scripts I had running.
I accepted that and said fine, no problem, we will get our new domain over there and everything will be good. The only problem I had with this is now we are forced to move this stuff right away because our request was not done the way it should have been. Please note, we paid them $100 to update our Sugar version which is no problem…
I started to get ready to move our data and could not connect via FTP, I entered a ticket and a LONG wait later I get the reply, to login to your control panel do this. Needless to say that is NOT what I needed. I needed to know how to login via ftp because all attempts would not work. Keep in mind, that we also upgraded our plan with them.
Anyway, it appears that because we tried to FTP in so many times we have been blocked, however, this would not have been the case if they had answered our support question in a reasonable amount of time… My one contact there when you send him emails comes back with
Hi. This is the qmail-send program at m8solutions.com.
I'm afraid I wasn't able to deliver your message to the following addresses.
This is a permanent error; I've given up. Sorry it didn't work out.
<REMOVED FOR PRIVACY>
user is over quota
--- Enclosed are the original headers of the message.
Can anyone please help with hsphere and how to FTP because apparently they are not going to help and now my entire office is unable to do any work because we cannot access our stuff…
Please note, I am a very patient person, but when it takes days to get an answer to a simple question and we are spending more money with them I lose my patience. I do not like to bash any company because we all have our problems, but this is crazy…
We let them know that we were going to do a post on WHT and still no response back. I feel horrible about posting this and will update you once this has been resolved..
View 6 Replies
ADVERTISEMENT
Aug 4, 2009
I signed up for a VPS at UltraVPS using their promotional coupon and special offer posted on WHT.
First- it took them 7 hours to activate my account, after bugging them.
Second- it takes them nearly 7 hours to respond to a support ticket.
Third- I am unable to login into the VPS control panel nor the FTP using the login information they have provided. I am not a newbie in hosting, I have several different VPS accounts.
It seems like this is a one-man operation.....
View 14 Replies
View Related
Jun 3, 2008
I met these guys through this website and they promised me exactly what I was looking for... a fast, responsive web host with PHP5, MySQL and 5GB - 10GB of storage. I was previously with HostDepartment and they obviously oversell... my site load times were counted in minutes. Anyways, things started great for the first two weeks... the site was always up and clients were amazed at the speed and performance of the site. I considered bringing over 7 other "business" websites because the performance was so great.
Then about 3 weeks ago... the site went offline. It's the internet, stuff happens...
DDoS attacks, DNS conflicts, Server Upgrades, someone trips on the power cord, whatever. I file a ticket and the site is back up in about an hour or two. So, i forget about it. Few days later, its down again... for a LONG period of time... multiple hours.
I file another ticket and I'm told they are in the process of mitigating a DDoS attack.
The outage then starts showing a pattern.. my site will be up late in the evening and early in the morning... but from 11amCST to about 11pmCST.. its unavailable. After another day, I contact them and they say they are still being assaulted by DDoS but they have put measures in place to correct it... that was at the end of May. My site has been down for 2 days straight.. since around 11am CST on June 1st. I came online briefly during the morning of June 2nd... but went back offline around 11am on the second and has never returned. The previously quick responses to my tickets have been non-existant now... I have yet to hear a response to my ticket from June 1st.. I did add a note to it once a day at 11am for the purpose of tracking that the site was still down. I understand that may move it to the end of the queue... but it has been updated once a day, so there was plenty of time between updates to see it.
I highly advise to avoid these guys... I wasn't going to write this until I could access to my site again for fear of losing my database info... but at this point, it seems like my sites are already lost.
View 16 Replies
View Related
Mar 30, 2008
I had read a lot of good things on these forums about ASmallOrange. So I finally decided to sign up with them for my friend's website which I manage & design.
Unfortunately my experience was anything but good. The issue was that I am based in India & I design my friend's website who is based in the US. Since my friend is a non tech savvy person he gave me his credit card number and asked me to manage everything from signing up for a new web host to designing the site.
Since ASmallOrange's billing department found that the address is registered based in USA but the IP address of the person signing up was not from USA, they marked the account as fraud.
I must say that I very well appreciate this system of fraud detection followed by them & am very much impressed by it. What I was not impressed with was the fact that they didn't bother to inform me about the same nor did they try to verify the authenticity of the account. Unaware of this, me & my friend kept waiting for more than 24 hours for my account to get activated. It was only when I raised a support ticket that they informed me that my account has been marked as fraud.
Subsequent to this I informed them about the circumstances under which this account was signed up & asked them to carry out whatever verifications they need to do with the end client or through the credit card company.
To my surprise again there was no reply from their end & this morning I find that my support thread was closed without reverting on the issue.
I guess its time for me to move on and host somewhere else. My own websites are hosted with Dotable and am very happy with them.
View 14 Replies
View Related
Jun 11, 2008
About a month ago I transferred a live site from a host to siteground as they supported all the functions I needed. I could have transferred the site myself, but to help convince to move to siteground promised me a free no downtime guaranteed transfer (which apparently is company policy) So I let them do it. There was downtime during the transfer but not a big deal I was ok with that But then a few days later my site went down big time. Someone called me to tell me it was down and I didn't have access to a computer so I called siteground. The operator (besides having trouble understanding english) wouldn't even report that my site was down to support!! Finally I get back to the computer and report it myself. Their 15 min or less turned out to be about 45 Then when I ask if I am going to be compensated for the extreme amount of downtime like the promise but I get turned down at every turn the excuse being technically it was downtime because it loaded a blank page STILL downtime in my book since it was siteground's fault I hadn't touched it. To add injury upon insult my site that ran perfectly smooth before has numerous problems. Every time I submitted a ticket they either tried to make it sound like it was my fault (again I hadn't touched it) or gave me the "normally this is a paid service but we made an exception for you" line as if I would need the service if they hadn't messed up the transfer. My overall experience with their service left me disgusted. Not to mention when I cancelled the "guaranteed money back" withholds nearly 4 months worth of the year I paid in advance. I have since transferred the SAME site MYSELF to atechosting and now have had it running for a few days there and had no downtime during transfer or a single problem since.
I will say performance wise they were fine even though their was some 169 on my server.
View 7 Replies
View Related
Jun 30, 2008
Today we have been very badly handled by iweb night support team.
The server went down and still down,
They did not answered phone and also did not update us for problem status. They kept saying the admin is working on the issue.
They asked root password and who knows what they are doing with it.
We are moving our accounts from their data center as we speak.
They employ irresponsible and incapable people and not trusted any longer.
Netelligent.ca is highly recommended for the ones looking for canadian dedicated server at the moment
View 1 Replies
View Related
Nov 7, 2009
I have been working with Xen over the last week or so and I can't figure out why the performance is downgraded so much when booting into Xen. There are certain things that seem just as fast but other things just don't seem normal.
I have tried this on two different quad-core systems, one new generation (York) with CentOS5 and one old (Kent) with Debian Lenny but neither seem to produce good speeds.
For example, when I use the default kernels I can usually get about ~600 score out of unixbench-wht and things such as top and core systems show up as 0% cpu when running top.
When I boot into Xen kernel however, whether it been from Dom0 or the guest OS, top uses about 3% CPU and unixbench-wht produces scores under 250.
I have set vcpus to 4 and have even tried vcpu-pin 0 0, 1 1, 2 2, 3 3 but nothing seems to be changing anything. The disk speeds seem about the same (hdparm). I'm assuming it is something with the CPU,
View 2 Replies
View Related
Dec 20, 2008
Does any one know what's up with solidhost?
I have a VPS plan with them that includes 6 dedicated IP's. they have only issused me 2 so I have asked them to issues 2 more. I have sent about 10 emails to their billing department (which handles this) and no one has responded. The technical department is replying to me but only in regards to technical prblems.
View 12 Replies
View Related
Nov 20, 2007
I have two netscreen 25 firewalls linked together via an ethernet cable.
If I connect the ethernet cable to switches I get around 90Mbps. However, if I connect the firewalls together I barely get more than 30Mbps (25Mbps average using iperf). All rules are set to talk to each other and the setup works, but I don't understand where the speed has gone.
The firewall ports and firewall performance per port is rated at 100Mbps and there is little traffic on the other network ports. I have both interfaces set to auto neg duplex as if set to 100 full I get even worse performance.
View 14 Replies
View Related
Apr 14, 2007
I finally ditched Site5 at a host. So _anything_ should be better, right?
After only a week or so with ServInt I'm wondering if I made the wrong decision.
Now I thought a few hours resolution time with Site5 was frusterating, try waiting 6 hours, or 18 (my current ticket, still not resolved, with no reply after asking for an update several hours ago).
And having a tech answer the phone doesn't help much either if they don't have a clue how to troubleshoot.
First the tech insists that MX records need to be pointed to my host for OUTGOING smtp to work!
Then after sending him the necessary log files twice, he still insists I'm not giving him enough information to fix the problem and that MX records must be setup. When I call and ask if he read the log file snippets I had sent him, "no" was the answer! AAAAAARGH!
And then being told many times, that the problems been fixed. And then finding out it's not and that they never even TESTED IT before saying so!
Is it time to pack up and leave before I migrate all my customers there?
View 14 Replies
View Related
Jun 29, 2009
Im getting the following error:
This message was created automatically by mail delivery software.
A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed:
email@shaw.ca
SMTP error from remote mail server after initial connection:
host idcmail.shaw.ca [24.71.223.11]: 554-idcmail.shaw.ca
554 Your connection from IP has been rejected due to poor reputation
.....
View 5 Replies
View Related
May 10, 2009
I have been lurker for long time already but now decided to ask this question I have been wondering about past few months.
I rent an dedicated server from KeyWeb, with dedicated 100mbps link. The server itself isn't that good & fast, but it's just perfect for my gaming server (E4500, 2GB DDR-2 ram and 2 x 320GB sata 2 drives)
Now to the problem. Always when I download some big files with this server from ftp or html server, and if I only open one connection, speed is very poor... Like 1MB/s or so, but if I use some download manager or torrent client which opens more than just one connection, +10 or so... Then the speed is very good, sometimes it goes up to 15MB/s. The server is actually connected to 1gbps switch but I think the port is limited to 100mbps.
At speedtest (dot) net, I get results like 17mbps down and 8mbps down.
So... Is that normal or is there something wrong? I've not contacted them yet, but if this isn't normal. I will Ofcourse I'll try to solve this on my own.
and before someone asks if this ftp I'm downloading from is not fast enough... I can tell you, it's. I downloaded one big file from it at school and at max speed was about 9MB/s
View 14 Replies
View Related
Jan 4, 2008
I have read on this forums and google CSF seem to be the best firewall out there, so i installed it configure and run it. After the installation i found that i received a lot time out error on web service. Page take a lot longer to load. I think it's my configuration.
Can someone take a look at my configuration if possible please share your configuration. I really like to have CSF run without poor performance on web service.
TESTING = "0"
TESTING_INTERVAL = "5"
AUTO_UPDATES = "1"
ETH_DEVICE = "eth1"
ETH_DEVICE_SKIP = ""
TCP_IN = "20,21,22,25,53,80,110,143,443,465,953,993,995,2077,2078,2082,2083,2086,2087,2095,2096,8184"
TCP_OUT = "20,21,22,25,37,43,53,80,110,113,443,587,873,953,2087,2089,2703"
UDP_IN = "20,21,53,953"
UDP_OUT = "20,21,53,113,123,873,953,6277"
ICMP_IN = "1"
ICMP_OUT = "0"
SMTP_BLOCK = "1"
SMTP_ALLOWLOCAL = "0"
MONOLITHIC_KERNEL = "0"
DROP = "DROP"
DROP_LOGGING = "1"
DROP_IP_LOGGING = "1"
DROP_ONLYRES = "0"
DROP_NOLOG = "67,68,111,113,135:139,445,513,520"
PACKET_FILTER = "1"
DROP_PF_LOGGING = "0"
VERBOSE = "1"
SYSLOG = "0"
DYNDNS = "0"
RELAYHOSTS = "1"
DENY_IP_LIMIT = "100"
GLOBAL_ALLOW = ""
GLOBAL_DENY = ""
GLOBAL_IGNORE = ""
LF_GLOBAL = ""
LF_DAEMON = "1"
LF_TRIGGER = "0"
LF_TRIGGER_PERM = "1"
LF_SELECT = "1"
LF_SSHD = "3"
LF_SSHD_PERM = "1"
LF_FTPD = "3"
LF_FTPD_PERM = "1"
LF_SMTPAUTH = "3"
LF_SMTPAUTH_PERM = "1"
LF_POP3D = "5"
LF_POP3D_PERM = "1"
LF_IMAPD = "5"
LF_IMAPD_PERM = "1"
LF_HTACCESS = "5"
LF_HTACCESS_PERM = "300"
LF_MODSEC = "0"
LF_MODSEC_PERM = "1"
LF_CPANEL = "3"
LF_CPANEL_PERM = "3600"
LF_CSF = "1"
LF_SSH_EMAIL_ALERT = "1"
LF_SU_EMAIL_ALERT = "1"
LF_SCRIPT_ALERT = "1"
LF_SCRIPT_LIMIT = "100"
LF_SCRIPT_PERM = "0"
LF_DIRWATCH = "60"
LF_DIRWATCH_DISABLE = "1"
LF_DIRWATCH_FILE = "1"
LF_INTEGRITY = "3600"
LF_INTERVAL = "300"
LF_PARSE = "5"
LF_EMAIL_ALERT = "1"
LT_EMAIL_ALERT = "1"
LT_POP3D = "60"
LT_IMAPD = "0"
RT_RELAY_ALERT = "1"
RT_RELAY_LIMIT = "100"
RT_RELAY_BLOCK = "0"
RT_AUTHRELAY_ALERT = "1"
RT_AUTHRELAY_LIMIT = "100"
RT_AUTHRELAY_BLOCK = "0"
RT_POPRELAY_ALERT = "1"
RT_POPRELAY_LIMIT = "100"
RT_POPRELAY_BLOCK = "0"
RT_LOCALRELAY_ALERT = "1"
RT_LOCALRELAY_LIMIT = "100"
RT_LOCALRELAY_BLOCK = "0"
LF_DSHIELD = "86400"
LF_DSHIELD_URL = [url]
LF_SPAMHAUS = "86400"
LF_SPAMHAUS_URL = [url]
LF_BOGON = "86400"
LF_BOGON_URL = [url]
CT_LIMIT = "300"
CT_INTERVAL = "60"
CT_EMAIL_ALERT = "1"
CT_PERMANENT = "1"
CT_BLOCK_TIME = "1800"
CT_SKIP_TIME_WAIT = "0"
CT_STATES = ""
PT_LIMIT = "30"
PT_INTERVAL = "60"
PT_SKIP_HTTP = "0"
PT_USERPROC = "8"
PT_USERMEM = "100"
PT_USERTIME = "1800"
PT_USERKILL = "0"
PT_LOAD = "30"
PT_LOAD_AVG = "5"
PT_LOAD_LEVEL = "6"
PT_LOAD_SKIP = "3600"
PT_SMTP = "0"
IPTABLES = "/sbin/iptables"
MODPROBE = "/sbin/modprobe"
IFCONFIG = "/sbin/ifconfig"
SENDMAIL = "/usr/sbin/sendmail"
NETSTAT = "/bin/netstat"
PS = "/bin/ps"
FUSER = "/sbin/fuser"
VMSTAT = "/usr/bin/vmstat"
LS = "/bin/ls"
MD5SUM = "/usr/bin/md5sum"
TAR = "/bin/tar"
CHATTR = "/usr/bin/chattr"
HTACCESS_LOG = "/usr/local/apache/logs/error_log"
MODSEC_LOG = "/usr/local/apache/logs/error_log"
SSHD_LOG = "/var/log/secure"
SU_LOG = "/var/log/secure"
FTPD_LOG = "/var/log/messages"
SMTPAUTH_LOG = "/var/log/exim_mainlog"
SMTPRELAY_LOG = "/var/log/exim_mainlog"
POP3D_LOG = "/var/log/maillog"
IMAPD_LOG = "/var/log/maillog"
CPANEL_LOG = "/usr/local/cpanel/logs/login_log"
SCRIPT_LOG = "/var/log/exim_mainlog"
View 14 Replies
View Related
Feb 7, 2007
I have had major problems with connecting to my shared hosting space from my home. Sometimes I can only view one page before it times out and other times I can not view any pages.
I have tried tracert, which seemed fine and there is no problem accessing the IP from any other location, only my house.
Has anyone got any ideas of what I could do? If I can not figure it out I am either going to have to get another ISP or move all my web sites.
View 4 Replies
View Related
Jul 15, 2006
I don't have a problem with Bluehost, but after getting this email tonight I would have thought that it's not that hard to have enough fuel and a big enough generator to last more than five minutes after a power outage. It seems like pretty poor redundancy planning if a major host can't last more then five minutes with no power. Hospitals and other places don't have any problem doing it with similar or bigger power demands.
Dear Bluehost Customer,
This evening (July 14th) from about 5:25pm-6:55pm many of our servers
were offline causing significant downtime for many of our users. The
outage was due to a severe power outage in the north end of Orem, Utah
where our servers are located. We do have UPS backup as well as diesel
generators, but at about 5:30 they finally gave out. The power outage
was for much longer than that period of time, but the reserve power
was eventually consumed in its entirety. When it rains it pours.
For users on box65-box145 there have been periodic problems with the
Redhat linux kernel that we were using that was causing problems with
the filesystem that your data is stored on. This issue has been causing
periodic problems for users on those boxes. In the last few days we have
resolved that issue which also caused those boxes to require a reboot.
The downtime is extremely regretable. We apologize profusely for the
inconvenience to our customers and in turn to those who were trying to visit
your sites during the outage. With the fixes we have put in place in the
last few days coupled with other upgrades you should experience MUCH
better uptime in the future.
Thanks for you patience,
Matt Heaton / President Bluehost.com
View 5 Replies
View Related
Feb 2, 2009
Why has Ipower turned into a such a poor hosting service? I have been with them for years and now they are leaving me little choice, but to find a new provider. For years they were able to provide me with a smooth service. Over the last year I have experienced tons of down time, long wait time for customer service, and recently downed email service for way toooo long.
View 10 Replies
View Related
Jan 4, 2007
I've got some hardware based on SuperMicro PDSMi and trying to run CentOS 4.4 on it.
It all installs fine however Disk Performance is extremely poor:
hdparm -t /dev/hda
/dev/hda:
Timing buffered disk reads: 12 MB in 3.30 seconds = 3.64 MB/sec
hdparm shows the hard drive is running in funny mode:
/dev/hda:
multcount = 16 (on)
IO_support = 0 (default 16-bit)
unmaskirq = 0 (off)
using_dma = 0 (off)
keepsettings = 0 (off)
readonly = 0 (off)
readahead = 256 (on)
geometry = 20023/255/63, sectors = 164696555520, start = 0
And strange thing DMA can't be enabled:
hdparm -d1 /dev/hda
/dev/hda:
setting using_dma to 1 (on)
HDIO_SET_DMA failed: Operation not permitted
using_dma = 0 (off)
View 8 Replies
View Related
Nov 24, 2006
I'll second what is said about Lunarpages. They are an absmal McHost whose priority is to lure in as many customers as possible without bothering about the quality of their service. I challenge anybody to ring their telephone support line and see if somebody picks it up. I have tried to call ten times in the last six months and never been able to get through once, despite hanging on for ages.
Just today my entire website was down because Lunarpages moved it to a new server (without asking me) and screwed up. The website, Azam.biz has over 17,000 references to it in Google and is critical to my business. I sat drowing in sweat for hours. I couldn't get hold of anybody at Lunarpages by telephone or live chat and the one support response I received ws addressing an unrelated issue.
Worse thing of the lot is Lunarpages censors criticism them on their forums more so than any webhost I have ever know. Every time I post a comment about downtime or not being able to get hold of anybody on the telephone, they delete the post saying it is "incorrect". I have never met a company with such a Stalinesque censorship policy.
I have feared posting anything negative about Lunarpages on other forums because I've been worried about them closing down my account. But, after having suffered so much stress because of them today, I don't care any more.
I am going to back up by entire site now, because I'm worried they will close down my account after reading this. They are not the type of company to take on board criticism and use it to improve their offerings; their obsession is to stifle any criticism.
I am now suffering pain in my heart for the first time in my life because of how badly Lunarpages have treated me today. Their arrogance shows no bounds - they are smug, full of hype and don't give a damn about ruining customers' businesses.
View 7 Replies
View Related
Oct 7, 2009
I have seen number of web host with poor performance gain allot of sales.
number of ppl complaining on wht about such host.
I wonder how come customer go there, and how come they have such large sales, on other hand I saw some quality web host with fewer clients?
View 14 Replies
View Related
Feb 2, 2009
I had 2 annual accounts with joeusa.com for my website hosting (2 websites). I was a 3-year customer, somewhat disatisfied with tech support service but without time to change hosting servers. My email quit receiving on one website/account about 2 weeks ago. Joe told me they had changed out a hosting server & that was likely the issue. I continued to have no email with Joe being evasive & nonhelpful. Upon logging into the control panel, I noted I was blocked out. I finally got him to agree to check on it, & he stated that the host spam blockers were not activated, & there was too much spam. I had made no changes, so the spam blockers had to be deactivated when they changed servers with no notification to me.
Joe shut down both of my accounts refusing me a prorated refund. I had paid one on Sept. 6 through PayPal for 1 year & the other on Nov. 6 through PayPal, also for a year. I was told by PayPal that they do not cover services, so FYI on PayPal, buyer beware. Joe gave me 24 hours to take my websites down. He also wiped out all of my email that was on the server that I had not been able to receive for the last 2 weeks & I lost all of it with no access to it.
I have email proof of what transpired & only want a prorated refund, what is fair, because I have not received near the full year service purchased for both accounts. He has refused, and I am considering filing fraud charges. My email documentation shows how a simple tech support issue turned into his cheating me out of my money when he cancelled both services & refused any prorated refund.
I have no idea why he has acted so vindictively, including wiping all non-spam email off the server that I was never able to receive, but, based on some of his comments, I believe that he either did not like our Judeo-Christian website or that he had been reading some of my personal email with political comments in the recent election. He was not even aware of my 2nd account until I made him aware that there were two, but he was aware of the ministry website/account, where the email issues were. The other account had no issues, but he cancelled both. Also, the Judeo-Christian ministry website had been hacked on his server by someone alleging to be Islamic about a year ago.
I am not making this report in vengeance. I am only trying to keep the same thing from happening to other consumers. This is a low-bid hosting company, and, once again the old adage, "You get what you pay for," is proven true.
View 14 Replies
View Related
Apr 8, 2009
I thought I would try the new "cloud" VPS service that WestHost is using to handle all their VPS customers now.
First, if you have a billing issue, expect at least a two day response time. I have had two questions for the billing department. The first was handled in two days with great apologies from the responder on the length of time it took to get back to me. I sent a followup ticket to the same billing department -- that was two days ago and still no response. So obviously, the apology was not genuine or they wouldn't have let it happen again.
Just wanted to make sure everyone understands that:
1) VPS.net has no refund policy in place. No refunds. I asked for one only one day after signing up, and the response is no refunds period.
2) My other hosting experiences allowed me to keep the same base price I signed up for as long as I maintained the hosting account with them. Not VPS.net. Pricing will change at their whim. If you sign up in April, you will receive a huge increase in May. Yeah, they say they "may" have some coupons or something in the future, but hey -- how can you budget your hosting expenses if you don't know what they will be exactly?
I have had accounts with a lot of hosting companies in my many years in this industry, but none as uncustomer friendly as VPS.net -- and its such a shame since their shared hosting sister company -- WestHost -- is famous for their customer service and friendliness.
View 8 Replies
View Related
May 7, 2008
This is a lesson for everyone, regardless of the type of hosting you're looking for, ALWAYS do your homework first!
I'm a bit embarrassed to admit it, but in March I signed up with a hosting company based solely on the claims on their website, and their wonderful presales responses to my questions. The company is M6.net.
It started off well enough, sales responded to my list of about 20 questions, and I received my reply during the weekend, which impressed me because I thought I was going to wait until the following Monday to hear back from them. I signed up for their Designer plan, which offers 200gb storage, and 1.2tb of bandwidth, with a max of 17 websites.
I signed up for the account and waited. No account setup confirmation email, nothing. So I submitted a support ticket, and it was resolved quickly. So I'm on my way now. I'm a .Net developer, so the first thing I notice is that .Net is disabled on my account. So I submit a support ticket, it was resolved within an hour.
So now I go about checking on all the other things that are supposed to be included with the account, one of which was smartermail. It was setup using hoarde. So I submit a support ticket. Along the way, there were 3 or 4 other things that I noticed that weren't setup right and needed to be corrected, so I submitted support tickets. This was all on day 1.
Unlike the first 2 issues, rather than hearing that it's resolved, for all my subsequent tickets I get a response telling me that my issue has been escalated to level3. I don't know what that means because there's no explanation included, but I figure it must mean that my tickets are important.
I don't hear anything back the first day, which is acceptable, because my requests obviously require more attention than my first tickets. So the next day (day 2), I submit another ticket inquiring about the status of all my outstanding tickets. I get a reply telling me that they are working on them.
All of day 2 passes with no resolution on what should be fairly simple fixes. Day 3 rolls around, and that's when I started getting annoyed. I submitted, you guessed it, a support ticket asking for a status, and I get the same reply, "they are working on them". At this point I'm getting really irritated so I decided to call them to see what was going on.
This was where I started to see the light. A man answered the phone, I could barely understand him because he had a heavy accent (which is no problem in and of itself) but there was also a lot of background noise that sounded like a tv. He answered and mumbled a company name that I could not understand, but it was not "M6", when I replied to him "Oh, I'm sorry, I was trying to reach M6 tech support", he stammered a bit and said something to the effect of "Oh, yes, right, this is M6, can I help you?". To which I replied "No, I really don't think you can", and I hung up.
I had a sinking feeling in my gut, because I realized at that point what a mistake I had made. It was then that I started researching them and found one blistering negative review after another. So on day 3 I submitted a ticket (my last one I might add) and requested that they cancel my account and issue my refund per their 30-day money back guarantee.
I've yet to see the refund.
The fact that you're reading this shows that you're already doing the right thing. Read reviews, weigh the good against the bad, especially watch for hosts who care enough to log on and rebut negative reviews, and ask lots of questions here on WHT.
View 2 Replies
View Related
May 28, 2008
I've been using Xilo.net for just over a year now using a reseller account but the time has come to expand to a dedicated server. The level of support I've received from Xilo hasn't been 100% fantastic and my account is sometimes offline for one reason or another - impacting my sites.
I was just wondering if anyone else has any experience with Xilo and if so what your thoughts are on them? I read the other post from last year about Xilo being useless in setting up a VPN but just wondered if anyone else has dealt with them since?
I'm really not sure whether or not to stay with Xilo for a dedicated server or to move on.
View 0 Replies
View Related
Apr 16, 2007
I have recently ordered webhosting on not so well known 3fn webhosting company. The reason why I decided for them is because I had some money on my webmoney account, and I needed new webhosting (they accept webmoney payment).
I decided to go for starter plan to test their quality of service, because they didnt want to give me test account, although their site says they offer them. When my account was set up, it all seemed good - I got Plesk which I prefer over cPanel, etc. But when I connected to ftp server I noticed the server isnt that fast as its supposed to be.
After a few days server speed started to annoy me. My website went offline so frequently so that I couldnt belive. I told the admin im unsatisfied with hosting speed, any their uptime - he said they're going to fix it (or something like that).
Website worked fine after a few minutes, but then it went offline again. Today I wanted to access some files I host on my webserver from school, but I noticed the site was offline again.
I sent complaint to them by email and told them my website uptime is only like 60%, and got no response.
I havent been so dissapointed for a long time..
View 3 Replies
View Related
Sep 30, 2009
I was looking for a windows reseller plan. I researched lots and found mochahost. They seemed to have a good deal and had all the features I wanted. Anyway, I signed up and immediately requested that they add ClientExec to my account. (Extra $4/month).
After a few hours I received a welcome email and all was good, but no info on ClientExec. I contacted tech support through their chat program (which appears to always be a guy named "Tod"). He told me I needed to open a separate ticket for it. So I did that.
After 24 HOURS, I received a response telling me they generated an invoice that I need to pay. Which I did right away. The response also told me that I needed to re-open the support ticket after I paid for it so they would know to turn on ClientExec for me. The only problem is the ticket was already open.??
I waited about 6 hours and then I contacted "Tod" in tech support again via chat. He told me to open another ticket letting them know I paid, which I did, now 48 HOURS AGO.
No response at all. I contacted "Tod" again right now and he can't help at all. In fact he told me to open another ticket. lol.
I did read some bad stuff about Mochahost, and now Im pretty worried. If I ever need support for my customers I can't wait 48 hours for a response.
View 14 Replies
View Related
Sep 24, 2006
Do you have some experiences with Lunarpages.com ?
I purchased win host and I have some negative experiences with them at this time.
View 9 Replies
View Related
Aug 10, 2008
I bought their hosting 8 months ago and they are simply jerk for hosting a big site on their shared hosting plans. Now I have transfered my domains to one.com which is very good for huge traffic sites.
View 4 Replies
View Related
Oct 2, 2009
I want to tell you guys about my lunarpages experience. First, I found them through a top 10 website review. BIG mistake I understand now. Not really that big of a deal if I can rely on them which is reall all I want. But I don't think I can.
First thing I did after creating my account was go to setup my email. I was very excited, this is my first domain ever. I set it up and then find out I can't receive email! After reporting this to their staff and setting up a ticket, I find out the next day that I wasn't receiving email because I had set my mailbox quota limit to 5000mb. Apparently that was too high they said! Why would they give you the option of doing that if it's just going to screw things up? That's just stupid. I knew I didn't need that much but I figured I'd set it and forget it and it would be no problem.
Then the next thing was just yesterday when I went to check my website and it was down. And so was their LPCP (control panel). I don't know how long it was down for but I noticed it for about half an hour.
I'm still within their 30 day refund policy since I only started the account on tuesday. What do you guys think I should do? Is it commomplace for websites to go down from time to time?
I would really appreciate any suggestions you guys might have as a reliable host. Also, how do I go about tranfering my domain name? Do i tell lunarpages I want to cancel first and then tranfer the domain or do I setup an account where I want to domain to go, then cancel?
View 14 Replies
View Related
Oct 29, 2008
writing this post to share with the community my "experience" with VPSLand.I've read a mix of good and bad experiences with this company, and this is just another... I'll let the dialog speak for itself......
View 5 Replies
View Related
Apr 3, 2009
CSF firewall official forum is pretty dull.. no answer there in last 3-4 days, so I turned to our good old WHT community.
1. In CSF, how do I block range of IP ?
Say I want to block IPs starting 164.44.x.x
2.
Btw, I found that my CSF is not able to catch DOS attack at all !!
below is my csf config file
Code:
###############################################################################
# Copyright 2006-2009, Way to the Web Limited
# URL: http://www.waytotheweb.com
# Email: sales@waytotheweb.com
###############################################################################
# Testing flag - enables a CRON job that clears iptables incase of
# configuration problems when you start csf. This should be enabled until you
# are sure that the firewall works - i.e. incase you get locked out of your
# server! Then do remember to set it to 0 and restart csf when you're sure
# everything is OK. Stopping csf will remove the line from /etc/crontab
TESTING = "0"
# The interval for the crontab in minutes. Since this uses the system clock the
# CRON job will run at the interval past the hour and not from when you issue
# the start command. Therefore an interval of 5 minutes means the firewall
# will be cleared in 0-5 minutes from the firewall start
TESTING_INTERVAL = "5"
# Enabling auto updates creates a cron job called /etc/cron.d/csf_update which
# runs once per day to see if there is an update to csf+lfd and upgrades if
# available and restarts csf and lfd. Updates do not overwrite configuration
# files or email templates. An email will be sent to the root account if an
# update is performed
AUTO_UPDATES = "0"
# By default, csf will auto-configure iptables to filter all traffic except on
# the local (lo:) device. If you only want iptables rules applied to a specific
# NIC, then list it here (e.g. eth1, or eth+)
ETH_DEVICE = ""
# If you don't want iptables rules applied to specific NICs, then list them in
# a comma separated list (e.g "eth1,eth2")
ETH_DEVICE_SKIP = ""
# Lists of ports in the following comma separated lists can be added using a
# colon (e.g. 30000:35000).
# Allow incoming TCP ports
TCP_IN = "20,21,22,25,53,80,110,143,443,465,587,993,995,2222,2221"
# Allow outgoing TCP ports
TCP_OUT = "20,21,22,25,53,80,110,113,443,2222"
# Allow incoming UDP ports
UDP_IN = "20,21,53"
# Allow outgoing UDP ports
# To allow outgoing traceroute add 33434:33523 to this list
UDP_OUT = "20,21,53,113,123"
# Allow incoming PING
ICMP_IN = "1"
# Set the per IP address incoming ICMP packet rate
# To disable rate limiting set to "0"
ICMP_IN_RATE = "1/s"
# Allow outgoing PING
ICMP_OUT = "1"
# Set the per IP address outgoing ICMP packet rate
# To disable rate limiting set to "0"
ICMP_OUT_RATE = "1/s"
# Block outgoing SMTP except for root, exim and mailman (forces scripts/users
# to use the exim/sendmail binary instead of sockets access). This replaces the
# protection as WHM > Tweak Settings > SMTP Tweaks
#
# This option uses the iptables ipt_owner module and must be loaded for it to
# work. It may not be available on some VPS platforms
#
# Note: Run /etc/csf/csftest.pl to check whether this option will function on
# this server
SMTP_BLOCK = "0"
# If SMTP_BLOCK is enabled but you want to allow local connections to port 25
# on the server (e.g. for webmail or web scripts) then enable this option to
# allow outgoing SMTP connections to 127.0.0.1
SMTP_ALLOWLOCAL = "1"
# This is a comma separated list of the ports to block. You should list all
# ports that exim is configured to listen on
SMTP_PORTS = "25"
# Drop target for iptables rules. This can be set to either DROP ot REJECT.
# REJECT will send back an error packet, DROP will not respond at all. REJECT
# is more polite, however it does provide extra information to a hacker and
# lets them know that a firewall is blocking their attempts. DROP hangs their
# connection, thereby frustrating attempts to port scan the server.
DROP = "DROP"
# Enable logging of dropped connections to blocked ports to syslog, usually
# /var/log/messages. This option needs to be enabled to use Port Scan Tracking
DROP_LOGGING = "1"
# Enable logging of dropped connections to blocked IP addresses in csf.deny or
# by lfd with temporary connection tracking blocks. Do not enable this option
# if you use Port Scan Tracking
DROP_IP_LOGGING = "0"
# Only log reserved port dropped connections (0:1023). Useful since you're not
# usually bothered about ephemeral port drops
DROP_ONLYRES = "0"
# Commonly blocked ports that you do not want logging as they tend to just fill
# up the log file. These ports are specifically blocked (applied to TCP and UDP
# protocols) for incoming connections
DROP_NOLOG = "67,68,111,113,135:139,445,513,520"
# Enable packet filtering for unwanted or illegal packets
PACKET_FILTER = "1"
# Log packets dropped by the packet filtering option PACKET_FILTER. This will
# show packet drops that iptables has deemed INVALID (i.e. there is no
# established TCP connection in the state table), or if the TCP flags in the
# packet are out of sequence or illegal in the protocol exchange.
#
# If you see packets being dropped that you would rather allow then disable the
# PACKET_FILTER option above by setting it to "0"
DROP_PF_LOGGING = "0"
# Enable SYN flood protection. This option configures iptables to offer some
# protection from tcp SYN packet DOS attempts. You should set the RATE so that
# false-positives are kept to a minimum otherwise visitors may see connection
# issues (check /var/log/messages for *SYNFLOOD Blocked*). See the iptables
# man page for the correct --limit rate syntax
SYNFLOOD = "1"
SYNFLOOD_RATE = "80/s"
SYNFLOOD_BURST = "150"
# Port Flood Protection. This option configures iptables to offer protection
# from DOS attacks against specific ports. This option limits the number of
# connections per time interval that new connections can be made to specific
# ports
#
# This feature does not work on servers that do not have the iptables module
# ipt_recent loaded. Typically, this will be with MONOLITHIC kernels. VPS
# server admins should check with their VPS host provider that the iptables
# module is included
#
# For further information and syntax refer to the Port Flood section of the csf
# readme.txt
#
# Note: Run /etc/csf/csftest.pl to check whether this option will function on
# this server
PORTFLOOD = ""
# Enable verbose output of iptables commands
VERBOSE = "1"
# Log lfd messages to SYSLOG in addition to /var/log/lfd.log. You must have the
# perl module Sys::Syslog installed to use this feature
SYSLOG = "0"
# Enable this option if you want lfd to ignore (i.e. don't block) IP addresses
# listed in csf.allow in addition to csf.ignore (the default). This option
# should be used with caution as it would mean that IP's allowed through the
# firewall from infected PC's could launch attacks on the server that lfd
# would ignore
IGNORE_ALLOW = "0"
# Enable the following option if you want to apply strict iptables rules to DNS
# traffic (i.e. relying on iptables connection tracking). Enabling this option
# could cause DNS resolution issues both to and from the server but could help
# prevent abuse of the local DNS server
DNS_STRICT = "0"
# Limit the number of IP's kept in the /etc/csf/csf.deny file. This can be
# important as a large number of IP addresses create a large number of iptables
# rules (4 times the number of IP's) which can cause problems on some systems
# where either the the number of iptables entries has been limited (esp VPS's)
# or where resources are limited. This can result in slow network performance,
# or, in the case of iptables entry limits, can prevent your server from
# booting as not all the required iptables chain settings will be correctly
# configured. The value set here is the maximum number of IPs/CIDRs allowed
# if the limit is reached, the entries will be rotated so that the oldest
# entries (i.e. the ones at the top) will be removed and the latest is added.
# The limit is only checked when using csf -d (which is what lfd also uses)
# Set to 0 to disable limiting
DENY_IP_LIMIT = "100"
# Limit the number of IP's kept in the temprary IP ban list. If the limit is
# reached the oldest IP's in the ban list will be removed and allowed
# regardless of the amount of time remaining for the block
# Set to 0 to disable limiting
DENY_TEMP_IP_LIMIT = "100"
# Enable login failure detection daemon (lfd). If set to 0 none of the
# following settings will have any effect as the daemon won't start.
LF_DAEMON = "1"
# By default, lfd will send alert emails using the relevant alert template to
# the To: address configured within that template. Setting the following
# option will override the configured To: field in all lfd alert emails
#
# Leave this option empty to use the To: field setting in each alert template
LF_ALERT_TO = "rickyjaffery@gmail.com"
# Block Reporting. lfd can run an external script when it performs and IP
# address block following for example a login failure. The following setting
# is to the full path of the external script which must be executable. See
# readme.txt for format details
#
# Leave this setting blank to disable
BLOCK_REPORT = ""
# Send an alert if log file flooding is detected which causes lfd to skip log
# lines to prevent lfd from looping. If this alert is sent you should check the
# reported log file for the reason for the flooding
LOGFLOOD_ALERT = "0"
# Temporary to Permanent IP blocking. The following enables this feature to
# permanently block IP addresses that have been temporarily blocked more than
# LF_PERMBLOCK_COUNT times in the last LF_PERMBLOCK_INTERVAL seconds. Set
# LF_PERMBLOCK to "1" to enable this feature
#
# Care needs to be taken when setting LF_PERMBLOCK_INTERVAL as it needs to be
# at least LF_PERMBLOCK_COUNT multiplied by the longest temporary time setting
# (TTL) for blocked IPs, to be effective
#
# Set LF_PERMBLOCK to "0" to disable this feature
LF_PERMBLOCK = "1"
LF_PERMBLOCK_INTERVAL = "86400"
LF_PERMBLOCK_COUNT = "4"
# Permanently block IPs by network class. The following enables this feature
# to permanently block classes of IP address where individual IP addresses
# within the same class LF_NETBLOCK_CLASS have already been blocked more than
# LF_NETBLOCK_COUNT times in the last LF_NETBLOCK_INTERVAL seconds. Set
# LF_NETBLOCK to "1" to enable this feature
#
# This can be an affective way of blocking DDOS attacks launched from within
# the same networ class
#
# Valid settings for LF_NETBLOCK_CLASS are "A", "B" and "C", care and
# consideration is required when blocking network classes A or B
#
# Set LF_NETBLOCK to "0" to disable this feature
LF_NETBLOCK = "0"
LF_NETBLOCK_INTERVAL = "86400"
LF_NETBLOCK_COUNT = "4"
LF_NETBLOCK_CLASS = "C"
# Safe Chain Update. If enabled, all dynamic update chains (GALLOW*, GDENY*,
# SPAMHAUS, DSHIELD, BOGON, CC_ALLOW, CC_DENY, ALLOWDYN*) will create a new
# chain when updating, and insert it into the relevant LOCALINPUT/LOCALOUTPUT
# chain, then flush and delete the old dynamic chain and rename the new chain.
#
# This prevents a small window of opportunity opening when an update occurs and
# the dynamic chain is flushed for the new rules.
#
# This option should not be enabled on servers with long dynamic chains (e.g.
# CC_DENY/CC_ALLOW lists) and low memory. It should also not be enabled on
# Virtuozzo VPS servers with a restricted numiptent value. This is because each
# chain will effectively be duplicated while the update occurs, doubling the
# number of iptables rules
SAFECHAINUPDATE = "0"
# If you wish to allow access from dynamic DNS records (for example if your IP
# address changes whenever you connect to the internet but you have a dedicated
# dynamic DNS record from the likes of dyndns.org) then you can list the FQDN
# records in csf.dyndns and then set the following to the number of seconds to
# poll for a change in the IP address. If the IP address has changed iptables
# will be updated.
#
# A setting of 600 would check for IP updates every 10 minutes. Set the value
# to 0 to disable the feature
DYNDNS = "0"
# To always ignore DYNDNS IP addresses in lfd blocking, set the following
# option to 1
DYNDNS_IGNORE = "0"
# The follow Global options allow you to specify a URL where csf can grab a
# centralised copy of an IP allow or deny block list of your own. You need to
# specify the full URL in the following options, i.e.:
# http://www.somelocation.com/allow.txt
#
# The actual retrieval of these IP's is controlled by lfd, so you need to set
# LF_GLOBAL to the interval (in seconds) when you want lfd to retrieve. lfd
# will perform the retrieval when it runs and then again at the specified
# interval. A sensible interval would probably be every 3600 seconds (1 hour)
#
# You do not have to specify both an allow and a deny file
#
# You can also configure a global ignore file for IP's that lfd should ignore
GLOBAL_ALLOW = ""
GLOBAL_DENY = ""
GLOBAL_IGNORE = ""
LF_GLOBAL = ""
# Country Code to CIDR allow/deny. In the following two options you can allow
# or deny whole country CIDR ranges. The CIDR blocks are downloaded from
# http://www.ipdeny.com/ipblocks/ and entirely rely on that service being
# available. The two-letter Country Code specified on that site should be used
# in the following settings. The iptables rules are for incoming connections
# only
#
# Warning: These lists are never 100% accurate and some ISP's (e.g. AOL) use
# non-geographic IP address designations for their clients
#
# Warning: Some of the CIDR lists are huge and each one requires a rule within
# the incoming iptables chain. This can result in significant performance
# overheads and could render the server inaccessible in some circumstances. For
# this reason (amongst others) we do not recommend using these options
#
# Warning: Due to the resource constraints on VPS servers this feature should
# not be used on such systems unless you choose very small CC zones
#
# Warning: CC_ALLOW allows access through all ports in the firewall. For this
# reason CC_ALLOW probably has very limited use
#
# Note: Use of this feature is bound by the TOS and Copyright agreements at
# http://www.ipdeny.com/usagelimits.php
#
# Each option is a comma separated list of CC's, e.g. "US,GB,DE"
CC_DENY = ""
CC_ALLOW = ""
# This option tells lfd how often to retrieve the CC CIDR's required for
# CC_ALLOW and CC_DENY (in days)
CC_INTERVAL = "7"
# Enable IP range blocking using the DShield Block List at
# http://www.dshield.org/diary.html?storyid=4483
# To enable this feature, set the following to the interval in seconds that you
# want the block list updated. The list is reasonably static during the length
# of a day, so it would be appropriate to only update once every 24 hours, so
# a value of "86400" is recommended
LF_DSHIELD = "0"
# The DShield block list URL. If you change this to something else be sure it
# is in the same format as the block list
LF_DSHIELD_URL = "http://feeds.dshield.org/block.txt"
# Enable IP range blocking using the Spamhaus DROP List at
# http://www.spamhaus.org/drop/index.lasso
# To enable this feature, set the following to the interval in seconds that you
# want the block list updated. The list is reasonably static during the length
# of a day, so it would be appropriate to only update once every 24 hours, so
# a value of "86400" is recommended
LF_SPAMHAUS = "1"
# The Spamhaus DROP List URL. If you change this to something else be sure it
# is in the same format as the drop list
LF_SPAMHAUS_URL = "http://www.spamhaus.org/drop/drop.lasso"
# Enable IP range blocking using the BOGON List at
# http://www.cymru.com/Bogons/
# To enable this feature, set the following to the interval in seconds that you
# want the block list updated. The list is reasonably static during the length
# of a day, so it would be appropriate to only update once every 24 hours, so
# a value of "86400" is recommended
#
# Do NOT use this option if your server uses IP's on the bogon list (e.g. this
# is often the case with servers behind a NAT firewall using ip routing)
LF_BOGON = "0"
# The BOGON List URL. If you change this to something else be sure it
# is in the same format as the drop list
LF_BOGON_URL = "http://www.cymru.com/Documents/bogon-bn-agg.txt"
# The following[*] triggers are application specific. If you set LF_TRIGGER to
# "0" the value of each trigger is the number of failures against that
# application that will trigger lfd to block the IP address
#
# If you set LF_TRIGGER to a value greater than "0" then the following[*]
# application triggers are simply on or off ("0" or "1") and the value of
# LF_TRIGGER is the total cumulative number of failures that will trigger lfd
# to block the IP address
#
# Setting the application trigger to "0" disables it
LF_TRIGGER = "0"
# If LF_TRIGGER is > 1 then the following can be set to "1" to permanently
# block the IP address, or if set to a value greater than "1" then the IP
# address will be blocked temporarily for the value in seconds. For example:
# LF_TRIGGER_PERM = "1" => the IP is blocked permanently
# LF_TRIGGER_PERM = "3600" => the IP is blocked temporarily for 1 hour
#
# If LF_TRIGGER is 0, then the application LF_[application]_PERM value works in
# the same way as above
LF_TRIGGER_PERM = "3600"
# To only block access to the failed application instead of a complete block
# for an ip address, you can set the following to "1", but LF_TRIGGER must be
# set to "0" with specific application[*] trigger levels also set
LF_SELECT = "0"
# Send an email alert if an IP address is blocked by one of the[*] triggers
LF_EMAIL_ALERT = "1"
#[*]Enable login failure detection of sshd connections
LF_SSHD = "5"
LF_SSHD_PERM = "1"
#[*]Enable login failure detection of pure-ftpd connections
LF_FTPD = "10"
LF_FTPD_PERM = "1"
#[*]Enable login failure detection of SMTP AUTH connections
LF_SMTPAUTH = "5"
LF_SMTPAUTH_PERM = "1"
#[*]Enable login failure detection of courier pop3 connections. This will not
# trap the older cppop daemon
LF_POP3D = "10"
LF_POP3D_PERM = "1"
#[*]Enable login failure detection of courier imap connections. This will not
# trap the older cpimap (uwimap) daemon
LF_IMAPD = "10"
LF_IMAPD_PERM = "1"
#[*]Enable login failure detection of Apache .htpasswd connections
# Due to the often high logging rate in the Apache error log, you might want to
# enable this option only if you know you are suffering from attacks against
# password protected directories
LF_HTACCESS = "5"
LF_HTACCESS_PERM = "1"
#[*]Enable failure detection of Apache mod_security connections
# Due to the often high logging rate in the Apache error log, you might want to
# enable this option only if you know you are suffering from attacks against
# web scripts
LF_MODSEC = "5"
LF_MODSEC_PERM = "1"
#[*]Enable detection of suhosin triggers and blocking of attackers
# Example: LF_SUHOSIN = "5"
LF_SUHOSIN = "0"
LF_SUHOSIN_PERM = "1"
# Check that csf appears to have been stopped. This checks the status of the
# iptables INPUT chain. If it's not set to DROP, LF will run csf. This will not
# happen if TESTING is enabled above. The check is done every 300 seconds
LF_CSF = "1"
# Send an email alert if anyone logs in successfully using SSH
LF_SSH_EMAIL_ALERT = "1"
# Send an email alert if anyone uses su to access another account. This will
# send an email alert whether the attempt to use su was successful or not
LF_SU_EMAIL_ALERT = "1"
# Enable Directory Watching. This enables lfd to check /tmp and /dev/shm
# directories for suspicious files, i.e. script exploits. If a suspicious
# file is found an email alert is sent. One alert per file per LF_FLUSH
# interval is sent
#
# To enable this feature set the following to the checking interval in seconds.
# Set to disable set to "0"
LF_DIRWATCH = "60"
# To remove any suspicious files found during directory watching, enable the
# following. These files will be appended to a tarball in
# /etc/csf/suspicious.tar
LF_DIRWATCH_DISABLE = "0"
# This option allows you to have lfd watch a particular file or directory for
# changes and should they change and email alert using watchalert.txt is sent
#
# To enable this feature set the following to the checking interval in seconds
# (a value of 60 would seem sensible) and add your entries to csf.dirwatch
#
# Set to disable set to "0"
LF_DIRWATCH_FILE = "0"
# This is the interval that is used to flush reports of usernames, files and
# pids so that persistent problems continue to be reported, in seconds.
# A value of 3600 seems sensible
LF_FLUSH = "3600"
# System Integrity Checking. This enables lfd to compare md5sums of the
# servers OS binary application files from the time when lfd starts. If the
# md5sum of a monitored file changes an alert is sent. This option is intended
# as an IDS (Intrusion Detection System) and is the last line of detection for
# a possible root compromise.
#
# There will be constant false-positives as the servers OS is updated or
# monitored application binaries are updated. However, unexpected changes
# should be carefully inspected.
#
# Modified files will only be reported via email once.
#
# To enable this feature set the following to the checking interval in seconds
# (a value of 3600 would seem sensible). This option may pur an increased I/O
# load onto the server as it checks system binaries.
#
# To disable set to "0"
LF_INTEGRITY = "10800"
# System Exploit Checking. This enables lfd to check for the Random JS Toolkit
# and may check for others in the future:
# http://www.cpanel.net/security/notes/random_js_toolkit.html
# It compares md5sums of the binaries listed in the exploit above for changes
# and also attempts to create and remove a number directory
#
# Modified files will only be reported via email once, though will be reset
# after an hour
#
# To enable this feature set the following to the checking interval in seconds
# (a value of 300 would seem sensible).
#
# To disable set to "0"
LF_EXPLOIT = "400"
# This comma separated list allows you to (de)select which tests LF_EXPLOIT
# performs
#
# For the SUPERUSER check, you can list usernames in csf.suignore to have them
# ignored for that test
#
# Valid tests are:
# JS,SUPERUSER
LF_EXPLOIT_CHECK = "JS,SUPERUSER"
# Set the time interval to track login failures within (seconds), i.e.
# LF_TRIGGER failures within the last LF_INTERVAL seconds
LF_INTERVAL = "300"
# This is how long the lfd process sleeps (in seconds) before processing the
# log file entries and checking whether other events need to be triggered
LF_PARSE = "5"
# Send an email alert if an account exceeds LT_POP3D/LT_IMAPD logins per hour
# per IP
LT_EMAIL_ALERT = "1"
# Block POP3 logins if greater than LT_POP3D times per hour per account per IP
# address (0=disabled)
LT_POP3D = "0"
# Block IMAP logins if greater than LT_IMAPD times per hour per account per IP
# address (0=disabled) - not recommended for IMAP logins due to the ethos
# within which IMAP works. If you want to use this, setting it quite high is
# probably a good idea
LT_IMAPD = "0"
# Connection Tracking. This option enables tracking of all connections from IP
# addresses to the server. If the total number of connections is greater than
# this value then the offending IP address is blocked. This can be used to help
# prevent some types of DOS attack.
#
# Care should be taken with this option. It's entirely possible that you will
# see false-positives. Some protocols can be connection hungry, e.g. FTP, IMAPD
# and HTTP so it could be quite easy to trigger, especially with a lot of
# closed connections in TIME_WAIT. However, for a server that is prone to DOS
# attacks this may be very useful. A reasonable setting for this option might
# be arround 200.
#
# To disable this feature, set this to 0
CT_LIMIT = "100"
# Connection Tracking interval. Set this to the the number of seconds between
# connection tracking scans
CT_INTERVAL = "5"
# Send an email alert if an IP address is blocked due to connection tracking
CT_EMAIL_ALERT = "1"
# If you want to make IP blocks permanent then set this to 1, otherwise blocks
# will be temporary and will be cleared after CT_BLOCK_TIME seconds
CT_PERMANENT = "0"
# If you opt for temporary IP blocks for CT, then the following is the interval
# in seconds that the IP will remained blocked for (e.g. 1800 = 30 mins)
CT_BLOCK_TIME = "1800"
# If you don't want to count the TIME_WAIT state against the connection count
# then set the following to "1"
CT_SKIP_TIME_WAIT = "0"
# If you only want to count specific states (e.g. SYN_RECV) then add the states
# to the following as a comma separated list. E.g. "SYN_RECV,TIME_WAIT"
#
# Leave this option empty to count all states against CT_LIMIT
CT_STATES = ""
# If you only want to count specific ports (e.g. 80,443) then add the ports
# to the following as a comma separated list. E.g. "80,443"
#
# Leave this option empty to count all ports against CT_LIMIT
CT_PORTS = ""
# Process Tracking. This option enables tracking of user and nobody processes
# and examines them for suspicious executables or open network ports. Its
# purpose is to identify potential exploit processes that are running on the
# server, even if they are obfuscated to appear as system services. If a
# suspicious process is found an alert email is sent with relevant information.
# It is then the responsibility of the recipient to investigate the process
# further as the script takes no further action. Processes (PIDs) are only
# reported once unless lfd is restarted.
#
# The following is the number of seconds a process has to be active before it
# is inspected. If you set this time too low, then you will likely trigger
# false-positives with CGI or PHP scripts.
# Set the value to 0 to disable this feature
PT_LIMIT = "60"
# How frequently processes are checked in seconds
PT_INTERVAL = "60"
# If you want process tracking to highlight php or perl scripts that are run
# through apache then disable the following,
# i.e. set it to 0
#
# While enabling this setting will reduce false-positives, having it set to 0
# does provide better checking for exploits running on the server
PT_SKIP_HTTP = "0"
# lfd will report processes, even if they're listed in csf.pignore, if they're
# tagged as (deleted) by Linux. This information is provided in Linux under
# /proc/PID/exe. A (deleted) process is one that is running a binary that has
# the inode for the file removed from the file system directory. This usually
# happens when the binary has been replaced due to an upgrade for it by the OS
# vendor or another third party (e.g. cPanel). You need to investigate whether
# this is indeed the case to be sure that the original binary has not been
# replaced by a rootkit
#
# To stop lfd reporting such process you need to restart the daemon to which it
# belongs and therefore run the process using the replacement binary (presuming
# one exists). This will normally mean running the associated startup script in
# /etc/init.d/
#
# If you don't want lfd to report deleted binary processes, set to 0
PT_DELETED = "1"
# User Process Tracking. This option enables the tracking of the number of
# process any given cPanel account is running at one time. If the number of
# processes exceeds the value of the following setting an email alert is sent
# with details of those processes. If you specify a user in csf.pignore it will
# be ignored
#
# Set to 0 to disable this feature
PT_USERPROC = "10"
# This User Process Tracking option sends an alert if any linux user process
# exceeds the memory usage set (MB). To ignore specific processes or users use
# csf.pignore
#
# Set to 0 to disable this feature
PT_USERMEM = "100"
# This User Process Tracking option sends an alert if any linux user process
# exceeds the time usage set (seconds). To ignore specific processes or users
# use csf.pignore
#
# Set to 0 to disable this feature
PT_USERTIME = "1800"
# If this option is set then processes detected by PT_USERMEM, PT_USERTIME or
# PT_USERPROC are killed
#
# Warning: We don't recommend enabling this option unless absolutely necessary
# as it can cause unexpected problems when processes are suddenly terminated.
# It is much better to leave this option disabled and to investigate each case
# as it is reported when the triggers above are breached
#
# Note: Processes that are running deleted excecutables (see PT_DELETED) will
# not be killed by lfd
PT_USERKILL = "0"
# Check the PT_LOAD_AVG minute Load Average (can be set to 1 5 or 15 and
# defaults to 5 if set otherwise) on the server every PT_LOAD seconds. If the
# load average is greater than or equal to PT_LOAD_LEVEL then an email alert is
# sent. lfd then does not report subsequent high load until PT_LOAD_SKIP
# seconds has passed to prevent email floods.
#
# Set PT_LOAD to "0" to disable this feature
PT_LOAD = "30"
PT_LOAD_AVG = "5"
PT_LOAD_LEVEL = "8"
PT_LOAD_SKIP = "3600"
# If a PT_LOAD event is triggered, then if the following contains the path to
# a script, it will be run in a child process. For example, the script could
# contain commands to terminate and restart httpd, php, exim, etc incase of
# looping processes
PT_LOAD_ACTION = "/sbin/service httpd restart"
# Port Scan Tracking. This feature tracks port blocks logged by iptables to
# syslog. If an IP address generates a port block that is logged more than
# PS_LIMIT within PS_INTERVAL seconds, the IP address will be blocked.
#
# This feature could, for example, be useful for blocking hackers attempting
# to access the standard SSH port if you have moved it to a port other than 22
# and have removed 22 from the TCP_IN list so that connection attempts to the
# old port are being logged
#
# This feature blocks all iptables blocks from the iptables logs, including
# repeated attempts to one port or SYN flood blocks, etc
#
# Note: This feature will only track iptables blocks from the log file set in
# IPTABLES_LOG below and if you have DROP_LOGGING enabled. However, it will
# cause redundant blocking with DROP_IP_LOGGING enabled
#
# Warning: It's possible that an elaborate DDOS (i.e. from multiple IP's)
# could very quickly fill the iptables rule chains and cause a DOS in itself.
# The DENY_IP_LIMIT should help to mitigate such problems with permanent blocks
# and the DENY_TEMP_IP_LIMIT with temporary blocks
#
# Set PS_INTERVAL to "0" to disable this feature. A value of between 60 and 300
# would be sensible to enable this feature
PS_INTERVAL = "300"
PS_LIMIT = "10"
# You can specify the ports and/or port ranges that should be tracked by the
# Port Scan Tracking feature. The following setting is a comma separated list
# of those ports and uses the same format as TCP_IN. The default setting of
# 0:65535 covers all ports
PS_PORTS = "0:65535"
# You can select whether IP blocks for Port Scan Tracking should be temporary
# or permanent. Set PS_PERMANENT to "0" for temporary and "1" for permanent
# blocking. If set to "0" PS_BLOCK_TIME is the amount of time in seconds to
# temporarily block the IP address for
PS_PERMANENT = "0"
PS_BLOCK_TIME = "3600"
# Set the following to "1" to enable Port Scan Tracking email alerts, set to
# "0" to disable them
PS_EMAIL_ALERT = "1"
# Account Tracking. The following options enable the tracking of modifications
# to the accounts on a server. If any of the enabled options are triggered by
# a modifications to an account, an alert email is sent. Only the modification
# is reported. The cause of the modification will have to be investigated
# manually
#
# You can set AT_ALERT to the following:
# 0 = disable this feature
# 1 = enable this feature for all accounts
# 2 = enable this feature only for accounts with uid 0 (e.g. root)
AT_ALERT = "2"
# This options is the interval between checks in seconds
AT_INTERVAL = "60"
# Send alert if a new account is created
AT_NEW = "1"
# Send alert if an existing account is deleted
AT_OLD = "1"
# Send alert if an account password has changed
AT_PASSWD = "1"
# Send alert if an account uid has changed
AT_UID = "1"
# Send alert if an account gid has changed
AT_GID = "1"
# Send alert if an account login directory has changed
AT_DIR = "1"
# Send alert if an account login shell has changed
AT_SHELL = "1"
# Display Country Code and Country for reported IP addresses
CC_LOOKUPS = "1"
# Messenger service. This feature allows the display of a message to a blocked
# connecting IP address to inform the user that they are blocked in the
# firewall. This can help when users get themselves blocked, e.g. due to
# multiple login failures. The service is provided by two daemons running on
# ports providing either an HTML or TEXT message.
#
# This feature does not work on servers that do not have the iptables module
# ipt_REDIRECT loaded. Typically, this will be with MONOLITHIC kernels. VPS
# server admins should check with their VPS host provider that the iptables
# module is included.
#
# For further information on features and limitations refer to the csf
# readme.txt
#
# Note: Run /etc/csf/csftest.pl to check whether this option will function on
# this server
#
# 1 to enable, 0 to disable
MESSENGER = "0"
# Provide this service to temporary IP address blocks
MESSENGER_TEMP = "1"
# Provide this service to permanent IP address blocks
MESSENGER_PERM = "1"
# User account to run the service servers under. We recommend creating a
# specific non-priv, non-shell account for this purpose
MESSENGER_USER = "csf"
# This is the maximum concurrent connections allowed to each service server
MESSENGER_CHILDREN = "10"
# Set this to the port that will receive the HTML message. You should configure
# this port to be >1023 and different from the TEXT port. Do NOT enable access
# to this port in TCP_IN
MESSENGER_HTML = "8888"
# This comma separated list are the HTML ports that will be redirected for the
# blocked IP address. If you are using per application blocking (LF_TRIGGER)
# then only the relevant block port will be redirected to the messenger port
MESSENGER_HTML_IN = "80,2082,2095"
# Set this to the port that will receive the TEXT message. You should configure
# this port to be >1023 and different from the HTML port. Do NOT enable access
# to this port in TCP_IN
MESSENGER_TEXT = "8889"
# This comma separated list are the TEXT ports that will be redirected for the
# blocked IP address. If you are using per application blocking (LF_TRIGGER)
# then only the relevant block port will be redirected to the messenger port
MESSENGER_TEXT_IN = "21"
# These settings limit the rate at which connections can be made to the
# messenger service servers. Its intention is to provide protection from
# attacks or excessive connections to the servers. If the rate is exceeded then
# iptables will revert for the duration to the normal blocking actiity
#
# See the iptables man page for the correct --limit rate syntax
MESSENGER_RATE = "30/m"
MESSENGER_BURST = "5"
# Statistics
#
# These options will be expanded in the future.
#
# This option enabled statistical data gathering
ST_ENABLE = "1"
# This option determines how many iptables log lines to store for reports
ST_IPTABLES = "100"
# This option indicates whether rDNS and CC lookups are performed at the time
# the log line is recorded (this is not performed when viewing the reports)
#
# Warning: If DROP_IP_LOGGING is enabled and there are frequent iptables hits,
# then enabling this setting could cause serious performance problems
ST_LOOKUP = "0"
# If you find ever increasing numbers of zombie lfd processes you may need to
# revert to the old child reaper code by enabling this option
OLD_REAPER = "0"
# OS settings
IPTABLES = "/sbin/iptables"
MODPROBE = "/sbin/modprobe"
IFCONFIG = "/sbin/ifconfig"
SENDMAIL = "/usr/sbin/sendmail"
PS = "/bin/ps"
FUSER = "/sbin/fuser"
VMSTAT = "/usr/bin/vmstat"
LS = "/bin/ls"
MD5SUM = "/usr/bin/md5sum"
TAR = "/bin/tar"
CHATTR = "/usr/bin/chattr"
# Log files
HTACCESS_LOG = "/var/log/httpd/error_log"
MODSEC_LOG = "/var/log/httpd/error_log"
SSHD_LOG = "/var/log/secure"
SU_LOG = "/var/log/secure"
FTPD_LOG = "/var/log/messages"
SMTPAUTH_LOG = "/var/log/secure"
POP3D_LOG = "/var/log/maillog"
IMAPD_LOG = "/var/log/maillog"
IPTABLES_LOG = "/var/log/messages"
SUHOSIN_LOG = "/var/log/messages"
CUSTOM1_LOG = "/var/log/messages"
CUSTOM2_LOG = "/var/log/messages"
CUSTOM3_LOG = "/var/log/messages"
CUSTOM4_LOG = "/var/log/messages"
CUSTOM5_LOG = "/var/log/messages"
CUSTOM6_LOG = "/var/log/messages"
CUSTOM7_LOG = "/var/log/messages"
CUSTOM8_LOG = "/var/log/messages"
CUSTOM9_LOG = "/var/log/messages"
# This configuration is for use with generic Linux servers, do not change the
# following setting:
GENERIC = "1"
DIRECTADMIN = "1"
# For internal use only. You should not enable this option as it could cause
# instability in csf and lfd
DEBUG = "0"
View 5 Replies
View Related
Oct 20, 2008
I need some experience suggestions, are they good ?
View 5 Replies
View Related
