I had decided to transfer 1 server into Hivelocity. It was a low $200s server with Hivelocities Platinum magagement plan. I was attracted to the pricing and the options available to configure my server how I wanted. I also liked the fact that they are somewhat local to where I live.
I had placed the server order with Drew. The server was delivered to me in 4 days, I was not in any rush so I did not mind. We started the migration process and went with out a problem until we went live. According to the tech the hard drive cable was bad and was replaced within 2 hours. These things happen and I still was not upset.
I was thinking to take advantage of the annual pricing offered and bring over the other servers until one morning I get flooded with phone calls chats and emails. I immediately try to log in the server to no avail so I contact Hivelocity. I was then told to contact the abuse department, well the abuse department does not take phone calls so then I was to told to log in a ticket.
What had happened was 1 of the hundreds of accounts hosted on the server recieved a copywright complaint and the server would not go back online until deleted and a ticket respond. I always comply with any complaint however I would appreciate at least a few hours to resolve, rather them an immediate disconnection. When you sell shared hosting you will always have a few accounts that are bad. No hosting company is immune to this. The server went back online 2 hours later.
Similar scenarios happened 2 more times with excessive down time in the first month that I was with them. Needless to say after talking several times with the GM Steve, I learned that he promises you one thing and either does another thing or does nothing as promised. For ex: will call you or will give a few hours to resolve any future complaints.
To compile further worries I learned that Hivelocity was terminating servers with out allowing transfer, including one host that was in business over 10 years. I do not know the non-bias details of those scenarios but I do know those things do not happent at the Planet, Softlayer or any other major datacenter, otherwise it would have been posted all over the net as was with Hivelocity.
In closing, my impression of the place was that their servers are ok, the bandwith is a bit spotty, the techs are ok, albeit one being a smart ass, the GM is a great speaker and the abuse guy is trigger happy. I do love the Hivelocity banners though.
It's too bad as I thought I had found a company that can save me alot of money however it ended costing me much more with loosing good clients.
We bought a VU200 VPS two days ago since we want to have a server in a stable environment mainly for our web site and email. We run a small Information Security consulting firm in the Silicon Valley.
Our experience with Zone.net has been a total disaster!
Zone.net installed a very bare CentOS 4; when we tried to use yum to install Dovecot IMAP we got a series of errors due to some missing libraries! Not a good sign. We contacted customer support and after they complained that this is an unmanaged server (like it is our fault they don't know how to install a stable system) they eventually agreed to install imap for us. If they installed a solid system in the first place we wouldn't have this problem . After we received an email from them saying that imap was installed, we login into the system and sure enough imap was not intalled! What a joke.
We then decided to reinstall the VPS from the Virtuozzo panel, since we figured out that these people at Zone.net are incompetents. The new installed system was even more bare: no yum , no imap, nothing. We called support again and ask to have access to the CentOS distribution via NFS for example. We don't want necessarily to install yum or other packages using rpmfinder, which would not be very clean; nor we want to have to upload a ton of rpm packages to the server, which would be a huge waste of our time. We talked to Jeffrey about it and he came up with a bunch of excuses why this is not possible, and why it is the way it is since this is a an unmanaged system. It was clear from the conversation that this yahoo is incompetent and he is just a button pusher. Furthermore he was unwilling to help whatsoever.
We have taken this matter to our credit card company and have them reverse the charges that Zone.net posted on our account and barred them to post any future charge on our account.
I recently transferred to Knownhost after my previous host ask me to leave their server because my websites eats 35% of their system, not the bandwidth and not the diskspace but the CPU. I have several clients running SMF forums with less than a hundred users at the same time.
After days of searching through the pages of WHT and through the suggestions of other members for me to get a VPS, I signed up with Knownhost.com. That is after asking them a lot of question regarding VPS and their packages, AUP and TOS. Pre-sale is fast, chat support answered all my questions with precise information and the same goes with their sales when I emailed them.
Since I don't know anything about VPS, I asked a lot of question ranging from stupid to more stupid question. Should I delete incremental backup or full backup ? what is Apache backup ? Can I delete Apache archive ? Can my client run mod-rewrite ? What is wrong with their .htaccess ? What DNS entry should I change for wildcard? What should I do to fix system resource problem as it reached 35.92% ? As you will see, all this questions and the other questions that I throwed to them were answered in a very professional and precise manner. I must admit that I am really impressed on how they handled my problems and how they explain everything that I need to know. This may seem small issues to others, but for a newbie on VPS like me it is a great help. They are not just simply efficient, but also very effective in delivering the solution. All the help that I need was given to me to run the VPS from scratch, me having no knowledge about it. Honestly, at first I thought they were trained to be polite, but it seems the support are really polite in nature. Not like other support I encountered from other host that were trained to be polite yet their evil nature goes out when you asked something unusual and off their manual and they can't solve it. It's been more than a week now, but everything is running smoothly. I may have had a few downtime but loss is immaterial for everything is being resolved in reasonable time. Reasonable in a way that minor problem are resolved instantly while major problems are carefully evaluated to give not just work around but rather a solution to the cause of the problem. I experienced this when they fixed the problem of my PHP configuration that conflicts with the memory requirement of SMF and also regarding the wildcard DNS that my client need.
I can't tell how long Knownhost.com support will be like this, but as long as I got the same quality of service from them, then I will stay.
I saw more than 35% usage from virtouzzo panel and it is indeed a spike.
In the event that the quality of support change, I'll look for this thread and post it here.
I went there for the low prices to startup my Shoutcast station. At $3 a month, it sounded too good to be true. I got my service, and the owner, seemed like a nice guy. He was very helpful, and was eager to help me get started. This was back in March. The first half of my stent there was great, however, in the last half, downtimes and even a data loss was getting on my nerves. I saw some really personal issues and arguments in the IRC server about the owner and staff, and even some back talk and really personal stuff that I wish I never had heard.
Because of the downtime, the owner did provide me with some free service and features. In these times, I was itching to leave, but the owner lured me back in with something better.
In this time, the service was 'okay', no real big complaints, I was even promoted to an IRCop, on the server.
Four things happened.
1) There was an incident in the chatroom with a regular joke we have done may times was taken really the wrong way. (I did not use my IRCop powers when this happened)
2) After a long outage (last night from 'this' post date), I was the only human on the irc server. In order for me to ask the owner what happened, I silenced a eggdrop bot by banning it from the main room. This was so I can get a new message notification when a real person enters the room. The bot posted every 2min, and it was at 2am in the morning.
3) I actually found a pretty big security hole in the control panel, the owner thanked me yesterday, and was furious the next.
4) because of the top three things, the owner basically got extremely mad and took away my IRCops.
Those 4 things basically were the last pieces of trash I could take. Yes, I forgot to unban the bot I mentioned in #2, but is that a good reason to get me out? Tonight, after a somewhat heated discussion with the owner, my account was instantly closed, all http/ftp pipes closed. I am very lucky I saw the owner start to fall into this cycle he seems to do, I had a full backup of the space I had.
In a nut shell, I would highly advise people NOT to use Maximum-Hosting. If you want low prices, frequent downtime, and the possibility your data could be gone in an instant, this is the host for you!
I can only hope no one else falls into the nightmare I have had to put up with for cheap hosting.
Although the domain was registered in 4/15/08, I could find next to nothing on WHT or the Ďnet in general in the way of reviews on FiveBean. Saw a lot of specials and things they have been running off and on at different venues and boards, but couldnít find a review to save my life. I did search pretty thoroughly. No web cache on web.archive.org either.
So, Iíll be the first to post one (that I know of), with a special they are offering, itís very affordable, if the service turns out to be good enough, then I have another node at a great price J. The more, the merrier. Win / Win 4 all. (FiveBean also offers shared hosting, so not exclusively a VPS provider.)
Hardware nodes Ė From their site: ďVPS Nodes are built with Intel Core2 Quad Processors, Premium SATA Disks and RAID Protection powered by CentOS 5.x and MoxieVM. Each VPS server is backed up daily and we provide 2 full backups to our customers.Ē
Although I never rely on providerís backups, itís good to see them offered as standard. Could come in handy.
They offer 5 plans; I ordered the middle-of-the road ďStarterĒ. All VPSs appear to be OpenVZ based.
Ordered Plan - 512M / 1G burst 40G HDD 450G BW 1 IP CentOS 5 for initial load
Initial order, small issue - Placed order at about midnight, got my welcome email at 7:40 AM. One issue was, I did not receive any emails from their ordering system, other than the PayPal-originating receipt. The emails were listed under the Client Area, so I still had access to read. Since I own and admin my own mail servers, I checked logs - Emails from ordering system were sent from a non-FQDN domain. From SMTP logfile: RECEIVED: MAIL FROM:<fivebean@kona> SIZE=3560 Mail server rejected because of the incomplete domain. This appeared to be an issue with the sign-up process only. All support ticket replies came from a FQDN. I described this problem in a support ticket, curios to see if they really do look @ and fix. Maybe on my second order? Everything initially ordered during the process was delivered, with no follow-ups required to correct anything. That's a little rare, from my experiences.
They offer online chat support, but have not caught it online as of yet, although I havenít checked before 9PM on any given day, so not a fair eval on that aspect. FWIW.
- On to the goodies -
Control panel - Apparently, FiveBean previously used HyperVM, but has since disabled and rolled out their own self-spun VM manager, "moxieVM". It's a simple, yet effective, web interface that allows me to do everything I need to, and everything works. That's always a good plus! moxieVM control panel contains the following: VPS list facility / user profile control / pass reset VPS Controls -- Reboot / Start / Stop / Rebuild OS / Set Reverse DNS Report (simple) shows -- OS currently installed / Monthly BW Usage total / Current Memory Usage / Action Log of previous control commands
Noteworthy - when you select "reboot / start / stop" there is no confirmation, action is queued and executed immediately. Good info to know.
Rebuilds - FiveBean offers 13 OS rebuild option w/ 6 Flavors - Ubuntu / Suse / Slackware / Fedora / Debian / CentOS, 32/64bit in most. Reload of OS (From CentOS 5 to Fedora 10) took about 4 minutes. Note - keep your original root login password! On OS reload, the pass is reset to the original you receive in your VPS welcome email, NOT whatever you have currently changed it to. I can see this being an issue if itís been a while since you have reloaded and end up digging out the old email. A little different than HyperVM.
Network - Ping times are consistently 15-16ms from/to Austin, 21ms from/to Atlanta, 12-18ms from/to Kansas City, MO. Traceroute to node (188.8.131.52) puts them behind Limestone Networks in Dallas, Tx. One thing I can report, their network seems to be very peppy. I've had a hard time hitting anything from / to the VPS with more than 20ms. I haven't seen a 30ms yet. From anywhere. An I have VPSs from coast to coast.
VPS / Initial Order- Hostname was set properly right off the bat, both initially and on OS reloads. Reverse DNS PTR self-set worked without having to put in a ticket, a first for sure! I just entered the rDNS PTR I required, waited about an hour, and it was set and propagated, ready to go. No muss, no fuss. Although I haven't put any load on the system, the CLI is responding very fast, and pings / traces / nslookups are very quick (as stated above). The only issue at all so far was the aforementioned order response email non-FQDN flurb. But, stuff happens. Small beans (pun intended).
AUP No porn, excessive violence, hate, deception, illegal IRC that causes no disturbances is allowed. I really prefer non-IRC networks, but they have a long lecture about it in the AUP, so it appears they watch activity pretty close.
Nuts n Bolts -
Benchmark (benchmark is on newly loaded system, minimal install FC 10, no load) ------------------ INDEX VALUES TEST BASELINE RESULT INDEX
-------------------------------------------------------------------------------------------- Conclusions Ė so far, so good. Iím actually pretty impressed with everything Iíve seen up to this point. Iím planning on putting the server under load as a backend node of a busy websiteís load balancer. Iíll post follow ups as we go along.
I've been with Blurstorm for 2+ years and I can say alot of good thing about the company and support. I even gave them a 5 out of 5 of webhostingjury and went as far as to say I would give them 10 out of 5, so you can imagine how happy I WAS with their service until this past week.
I has been an absolute hell. First the server kept blocking my ip and locking my session, when I would try and upload files with filezilla. They suggested to try a different ftp software which I did and it worked. At first I thought it was my computer/isp/router, so I tried it from my friend computer, same thing. And by the way, I never had this problem before. So I didn't make a big deal out of it, even though I prefer filezilla.
Now a couple of days ago, seems every time I would browse the pages or try and use the admin section the site would go down, or at least that's what I thought. After sending 8 hours going back and forth with support(Robert) through their support ticket system, because there is not live chat, Robert tells me there is nothing else they can do because they dont see any errors happening and I would have to pay a 3rd party monitoring service to find out what the problem is.
I mean I completely understand that if they cant find the problem but the site was working couple of days ago and I havent done anything different, so something must of happened on their end. Also I uploaded the site onto a friends server with a different hosting company and the site works perfectly with no problems.
Now being left high and dry with no help from Blurstorm, I did a couple of more test and found out that the site was not down but was blocking my ip and locking my sessions and the only way around it was for to renew my ip and to try again, but that would only help me for a couple of mins before it locked it again. Again, I also tried it from my friends computer and same thing. So I know for a Fact that it has to be from Blurstorm's end. I told that the server was blocking my ip and locking my session and haven't heard from them for over 16 hours, which is horrible customer service compared to the way they were before.
The main reason I stayed with blurstorm was for their support and quick response and I've referred them a boat load of business, and this was not the first time i've had problems with the server and support but I didnt make a big deal out of it and from now on no more referrals.
Well there is my review, sorry it's a little lengthy but just wanted to give an indepth review.
Second part - need suggestions for new hosting
From what I've gathers from searching that are reliable
precision effect jaguarpc innohosting
which would you recommend from those or any others?
And my site is based on joomla 1.5 + virtuemart so it should work with it.
I used Burstnet dedicated service for more than 2 months & would like to post a review here:
Initially I ordered a server before two months from Burstnet, Burstnet (Nocster) took more than a week to setup. After waiting for a week I got the server. Never received remote reboot port , though they billed me for it every month.
Initially it was working fine. After 7 days approx , my server was inaccessible , I added a support ticket to reboots & got reply that my server was suspended due to lack of reply of the abuse warnings they sent me , while I had got an abuse alert before a day informing me about spam mails somebody sent from a vps, I had already replied to the alert that I suspended the vps of spam mail user & had also got email from Burst saying: " Thank you for taking the time to contact the BurstNET Abuse Dept. BurstNET in no way condones any spam related........"
it was confirmed that they had received my reply for abuse alert. I informed them this in ticket, they replied they did not receive any reply from me. I provided them email headers & it was clearly showing that the mail was delivered to burst, later they said that the mail was delivered but was not reached to their support desk & they reactivated my server. There was 5 - 6 hrs down time , while there was no fault from me.
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.
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.
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.
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 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.
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.
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?
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......
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: email@example.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 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 = "firstname.lastname@example.org"
# 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 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"
I'm basically just going to copy/paste the message I posted on their forums that will likely never see the light of day... But before I do, I would like to say the following...
We have been clients of FDCservers for over 2 years and have had nothing but good experiences with them up until...
"Ok, I'll try to remain as cool and collect as I possibly can, but I have to air my concerns here since our issues are NOT being resolved via support tickets...
We currently leased a new server 2 months ago in August, replacing our old server. Ever since we've gotten this new server we have had nothing but problems.
The problems are the same each and every time, and yet nothing is getting done to actually resolve them...
In a nuttshell, merely days after leasing this new server, we had an HDD fail. It was replaced a day or so later. Then a few days later, another HDD fails. Replaced 2 days later or so.
Then again, HDD failure. Now not only do we have to wait another 2 days for it to be replaced (seems you guys don't keep an on location stock?), but we also have to reload the OS due to the failure.
Finally get the server back online, losing a small amount of data in the process (so far); and AGAIN we have an HDD failure. And again, and again, and again...
I have been very patient with your support staff up until this point, but the amount of money we have lost over the last 2 months is making me look for a different provider.
The issues we are having point to hardware related issues, more than likely a bad onboard disk controller. But the solution has always been to simply replace the failed HDD with a new one, oh and one time you swapped the sata cable to another port.
Now, I'm fully aware that you do not offer an SLA, which is fine.. but we are still paying for a service and yet we are not getting what we're paying for at this point, which is really saddening because we've had nothing but good things to say about your company for 2 years now. But this latest run of events is quickly changing my opinion, and simply because your tech support doesn't seem to actually want to resolve problems the right way.
And now I'm told my server has been completely replaced, but not after a claim that one of my disks started "smoldering", one of them is corrupt and one is lost (as in physically misplaced). Not only that but this "new" server had a whole 2 hours of uptime before it crashed. I have to ask what the hell happened to you guys? You were the first company I recommended when someone asked about a good dedi server company, yet now I'm sitting here with ALL my data seemingly gone (we're talking several hundred GB's of data btw, not something that can be easily replaced by backups) and a "new" server that is already having stability issues!
I really hate to say this, but you guys do not hesitate to turn off a server if a payment is 3 days or so late, so why do you hesitate so much to give us a server that actually works properly?
Or server is ID# ####. Please address our issues once and for all (You can see the ticket history) so we can go back to being happy customers like we have been for the last 2 years..."
So my question is... what in the hell happened to these guys? I remember the one time we had a hardware issue (dead mobo on our old server), it was replaced and we were back online in under an hour. But now I dunno wtf is going on except that we are constantly losing money thanks to this newfound incompetence...