I've got a few servers around many companies, yet never tried them(LSN). To me they are a bit fishy, by how cheap their servers are. Any experience with them(Good/Bad), please share it.
View 11 Replies
My Review / Experiances of Limestonenetworks
My Advise Avoid like the plauge
01-07-09 01:14 PM
I placed an order for a server
01-08-2009
Server is ready
Orginal Config
DotnetPanel
Windows Web 2008
I had problems from the start
IIS Not starting correctly
Dotnetpanel issues including adding websites.
So I fixed what I could and then employed someone to do the work.
Afterlooking around I found someone who looked proffessional and told me he could do the work.
He got back to me after a few hours and said their were problems with the server OS and DotnetPanel install.
It would take longer to fix but he would try
After A day or so, he sent me and email stating he was unable to get it to work correctly and said the entire OS needed to be reinstalled.
So I contacted LSN and told them about the problems I was having and decided to ditch the Windows 2008 Web server for a more roboust soloution.
I went for the classic Centos and Hypervm soloution.
LSN happy loaded my server with a fresh OS and I proceed to employ my normal guy to install and configure the server
AV went on
firewall went on
Lex went on
Hypervm went on
IP Address Binded to network adapters.
But all the VPS we setup only had the "local lan adapter IP" making them inaccessiable from the outside world.
After somemore looking at the matter I resorted to contact LSN and get them to remove /change the interfaces.
This gave the VPS the external IPS but were still not connectable from the outside world. so far I spent 65$ on the orinal comapny who looked at setting up the web 2008 server additioanl 45$ on a diffrent tech to confirm the fault and been billed for a second money at singlehop.
so I contacted "customer support" and all I wanted was a refund, even if it was parcial. I just wanted a refund. I lost out on to much money and to many hours sitting infront of the computer typing up support contacts.
Please read the transcript below I strongly advise you not to use LSN they are not a helpful company
You are now chatting with ryan
ryan: Hello, thank you for visiting Limestone Networks! How may I assist you today?
ibby@: Hello Ryan, I want to make a complaint.
ryan: Oh no! What appears to be the issue? ....
i have been with softlayer more than 3 yeres now iam looking to new data center and new server hosting any of this 2 company is good ?
View 14 Replies View Relatedi just ordered a new server in Limestonenetworks.
I'll post my experience here about they
I ordered the following server:
[url]
If everything goes all right i'll make sure to give they the best Review i can give to a company!
after reading the complete thread about Limestone's TOS and weighing their latest server offering, I took the plunge and just spent $160 on a monthly server.
My email from them is dated today at 6:44 pm.
Let's see how long it takes to get this server in my hands. Nothing special in the order, an extra hd for backup, that is it.
I'm a newbie here but not a newbie to unmanaged servers. If this one goes off without a hitch, I'll move a few sites from a box I currently have a ManageMyBox (no problems with them, at all, just looking for a datacenter closer to home and this seemed like a good deal).
Who is better limestonenetworks or BurstNet
I deal with the company BurstNet But the question now
Is limestonenetworks excellent company?
Is technical support fast?
I want enough information on the company limestonenetworks
I want to deal with them
Topic of discussion
I am very happy go give everyone a review of limestonenetworks.com
Here is My story!
I was in a bunch and needed a VPS server because My other one went down unexpectedly, so i needed a new server in under 5 hours. I looked all over, and came upon one very special company, Limestonenetworks.com. I placed the order, and selected to have HyperVM/OpenVZ installed. The server was setup in 3 Hours! This was the fastest setup time for a dedicated server I have ever seen. When I submit a support ticket, I have a response within 30 mins. This is truly one of the best datacenters ever! Their staff is very helpful! To be honest, I am so pleased with them, I just now ordered a second server from them! Yes, You do pay a bit more, but you definatly get what you pay for, and ill tell you what, this extra 2 cents is worth it all the way!
I would recommend Limestonenetworks.com to ANYONE!
[url]
Have you guys checked this out yet?
It is simply amazing!
Quote:
Intel Core2Quad Q9650
Yorkfield
8gb DDR2
1TB SATA2
10TB
100 MBPS
Cores 4 cores
Speed 3.0GHz
Core Name Yorkfield
L1 Cache 256KB
L2 Cache 12MB
HT Speed 1333MHz
All just for $159.99. ($40 off) That is just simply amazing.
I purchased one of those when it was for $179.99 and I am still using it. (Original is $199.99)
These servers are a BEAST!
Just wanted to say that LimeStoneNetworks dominates with the pricing + support and everything else related to Dedicated Server =P
My first ever post on WHT and I am happy its a positive one. These are a few words I have to say in favor of people at LimestoneNetworks.
I ordered a Intel Core2Quad Q6600 dedicated server with them with upgrading most of the resources to the topmost at about 6 AM CST this Friday. They recently included a Fraud Check in their TOS which I was not aware of but only became notified once I had signed up. It involved uploading the CC images and a Govt ID.
Btw: their new control panel Rockware actually Rocks !
I uploaded the docs promptly and since chat was offline I called them up and got connected with a Support rep. He told me that a Sales rep will check on it at 8 AM CST. At 8 AM, one of the sales rep promptly acknowledged the ticket for verification and it had the comments of a 24-hour turnaround, which scared me a little.
Wonder ! Wonder ! Since all my stuff was verifiable and without any issues... I got reply within 20 mins stating my server was being sent for provisioning.
Another wonder ! another 20 mins and my server was showing the server in my Rockware CP as being built. I was pressing F5 like crazy and everytime I saw something new in my CP regarding my server. Which is like the most rapid updates I have seen ever !
Overall, even after the verification delay, I got my server in 4 hours !
Subsequently I had to open some tickets to them for issues that were from my side and 100% (yes 100%) of the time, someone responded within 5 mins.
Hoping to post a similar (if not more) positive review after couple of months.
<<signature to be set up in your profile>>
current LSN customers (if possible) check what kind of hardware is their server?
I am looking @ Q9550 offer they have.
If somebody could check MB, RAM, HDD models.
Also, is there anyone on their 10TB plan?
Do they really allow customers to do this BW?
I have been with them for 3+ months now and the service has been amazing. I am pleased with the superb fast and knowledgeable customer support.
Going more into details...
I have submitted couple support tickets and all were answered on a timely manner, with proper guidance. Also their live-chat is very good, the rep. is knowledgeable and can provide technical support. The staff seems quite nice, and I am loving their new rockware panel, makes it easy for anyone to configure dns, pay invoice, check invoice, submit tickets, etc, etc. do anything you need to do regarding your server.
The overall service has been amazing, my site is quite server intensive and it loads very fast, my visitors are happy, and barely any downtime -- definitely a thumbs up from me
Where/How do I submit my domain to verify the review like I have seen in couple other threads?
Want to share my expirience after 2 weeks on limestone netwroks and psm.
For starters - i'm very happy with the service (~230$/m)
I started out with a webmin controled server without management and after 2 days of try and fail and new threads in wht i finally switched to cpanel with psm service, switch was really fast and limestone has a deal which gets you 5 bucks off psm's monthly fee.
limestone accually reinstalled my server and added cpanel and then contacted psm to get my software initialied (i even got my software configs set as my old server so i'll have a stable move).
software initiation took about 2 days with psm but that's due to special software requirment needed for my site to transfer.
responce times from psm and limestone are lightning fast and besides an overcharge of 39 bucks due to new software bug on limestone(got 40$ back yay), I can barely say something bad about this new system of running my dedi server with both limestone taking care of hardware and psm for all software issues - both do really well and fast on answering any kind of ticket.
ill give one example for this on the ticket i submited yesterday to psm, all my sent php mail() came out as spam on gmail.com, after contacting psm i got answered in less than 1 hour that my reverse dns aren't set correctly - then i got them setup with limestone and it took about 90 minutes to close this whole issue.
being moved from shared hosting to dedi servers I must say to all the new movers out there like I was that the combinitation of limestone + psm is great, you'll get fast and quallity support on all ends.
i've left out other info like uptime because this has been mentioned before and when combining the included psm monitoring with the great limestonenetworks uptime, downtime is a word i really forgot about.
I just want to preface this by saying I was on here reading up about hosting companies, their reviews and limestone networks after a phone call with Ryan A over there, was definitely going to be my provider.
However, I ordered my server about a week ago, and have some massive issues.
First and most concerning : Support.
There has been about 4 tickets from me, with no response for about 9+ hours, one ticket (when they incorrectly installed DotNetPanel, and I couldn't start hosting domains yet even) they didn't get back to me for almost 2 days. It looked like all hope was lost.
I guess (speaking with Kris there) they're working on tightening up the provisioning time, etc. With that said, they DID in fact fix my DotNetPanel installation, and all looked well.
Lastnight I figured I'd check my bandwidth, for kicks. I've been remote desktop connecting to my machine fairly frequently, maybe for about 10 minute sessions a piece, nothing major. I have nothing running on my box, I ran a couple of tests to check out pings, server loads so I figured I'd plop a quick and simple game server up there to test it. I checked my "bandwidth report" and this is what I found out:
[url]
Mind you, I have no mail server at all, nothing. in the span of 5 days I've used almost my entire quota, without running almost ANY serverside applications.
Currently my dedicated server remains shut down until this issue can be resolved. I entered yet another ticket lastnight, had one reply this morning, and it appears I'm back into the lost ticket desert.
Remember, just my experience. My point of view so far may change however, but at this rate it's been pretty horrible. 5 days on setting up a dedicated and have it all ready to go, I had to re-pay my old provider for another month due to Limestonenetwork's ability to not install DotNetPanel correctly, I'm pretty displeased at the moment.
Just wanted to take a minute and report that I am still extremely pleased with my LSN dedicated box. I have a 3ghz amd dual core with 4gig ram and 2x250gb hdd. No problems at all and staff is very helpful and knowledgeable. I don't want to go through the laundry list of things they have done for me and to my server (they are in other threads) but just wanted to say that they continue to impress.
View 5 Replies View RelatedI want to buy Dedicated Server...
What do you suggest me and why? plz also mention the reason..
leaseweb or Pacificrack or limestonenetworks
My company ordered server on 23/10/2009 from LimeStone, and they asked for verification hence i given them all the ID that they need. After that, they told me they couldn't accept AMEX and have to pay through PayPal, i have paid since and NOW again they asked for ID again.
Why i have to verify for second time since i have posted all my ID and utility bill for first time? I don't think i need to give so much verification since PayPal has already verified my account as i owned PayPal Verified Business Account, this kind of "repeating" or double verification never happen when i order from ThePlanet/EV1 where i am looking to migrate to Limestone Networks.
This is very unpleasant experience and I don't want to wait for more than a week to get a server.
I traced this sites:
Tracing route to vertualhost.com [69.162.111.77]
over a maximum of 30 hops:
1 1161 ms 797 ms 839 ms <hidden>
2 673 ms 876 ms 821 ms <hidden>
3 574 ms 839 ms 881 ms 10.137.4.81
4 743 ms 863 ms 857 ms 10.137.4.42
5 661 ms 899 ms 779 ms <hidden>
6 570 ms 875 ms 840 ms <hidden>
7 774 ms 462 ms 784 ms <hidden>
8 544 ms 401 ms 359 ms <hidden>
9 * * * Request timed out.
10 831 ms 562 ms 539 ms so-3-1.hsa1.LosAngeles1.Level3.net [4.78.205.157
]
11 578 ms 557 ms 562 ms vlan52.csw2.LosAngeles1.Level3.net [4.68.102.62]
12 469 ms 460 ms 457 ms ae-72-72.ebr2.LosAngeles1.Level3.net [4.69.137.2
1]
13 683 ms 682 ms 576 ms ae-3.ebr3.Dallas1.Level3.net [4.69.132.78]
14 609 ms 581 ms 580 ms ae-63-63.csw1.Dallas1.Level3.net [4.69.136.154]
15 567 ms 599 ms 557 ms ae-13-69.car3.Dallas1.Level3.net [4.68.19.5]
16 592 ms 599 ms 618 ms LIMESTONE-N.car3.Dallas1.Level3.net [4.71.120.66
]
17 573 ms 558 ms 580 ms 1-203-63-74.reverse.lstn.net [74.63.203.1]
18 676 ms 581 ms 580 ms 6-203-63-74.reverse.lstn.net [74.63.203.6]
19 510 ms 577 ms 580 ms 74-201-63-74.reverse.lstn.net [74.63.201.74]
20 663 ms 580 ms 581 ms vertualhost.com [69.162.111.77]
Trace complete.
AND:
Tracing route to yourservers.info [69.162.111.66]
over a maximum of 30 hops:
1 1414 ms 761 ms 664 ms <hidden>
2 1038 ms 1036 ms 680 ms 10.19.18.233
3 374 ms 1421 ms 376 ms 10.137.4.81
4 437 ms 1278 ms 1019 ms 10.137.4.42
5 1162 ms 783 ms 797 ms 10.145.176.130
6 525 ms 359 ms 377 ms 10.145.176.133
7 371 ms 378 ms 378 ms <hidden>
8 646 ms 420 ms 359 ms <hidden>
9 * * * Request timed out.
10 * * 4187 ms so-3-1.hsa1.LosAngeles1.Level3.net [
]
11 1618 ms 1499 ms 2183 ms vlan51.csw1.LosAngeles1.Level3.net [
12 658 ms 1522 ms 996 ms ae-62-62.ebr2.LosAngeles1.Level3.net
7]
13 2261 ms 1458 ms 3320 ms ae-3.ebr3.Dallas1.Level3.net [4.69.1
14 1655 ms 2463 ms 1435 ms ae-63-63.csw1.Dallas1.Level3.net [4.
15 1762 ms 1817 ms 2062 ms ae-13-69.car3.Dallas1.Level3.net [4.
16 1718 ms 1340 ms 2638 ms LIMESTONE-N.car3.Dallas1.Level3.net
]
17 2300 ms 455 ms 1739 ms 1-203-63-74.reverse.lstn.net [74.63.
18 1421 ms 420 ms 1978 ms 6-203-63-74.reverse.lstn.net [74.63.
19 461 ms 437 ms 599 ms 74-201-63-74.reverse.lstn.net [74.63
20 541 ms 576 ms 581 ms hostingwitch.com [69.162.111.66]
how can they sell UNLIMITED ALPHA MASTER RESELLER to others?
Is that true that they are your customer?
All I know is, You do not sell unlimited space at limestonenetworks.com.
Are those sites cheaters or are the illegal? I did not find a specific or complete postal address or person name on those sites.
i get a server from limestone networks after two days they send me mail bulk mailDescription: Bulk mail complaints- #1 and charged me $25 for this as a penalty, even i have not even hosted a domain on server or even not send any email from there, how they will charge i dont understand that. i take there server with the hels of this forum.
View 14 Replies View RelatedI joined Limestonenetworks back in 2008 when it was a small company. At the time they offered the best price on the server I was looking for, so I took the plunge. The first 2 months were great, I enjoyed the stable network, and responses from the support team were fairly quick (1-2 hours response time). From there on it was all downhill, my servers were constantly down, and the support team took longer to answer my tickets. I didn't think this was a big problem, so I stayed with Limestonenetworks even though it was having problems with their network. Near December an incident occurred that really pushed me over the edge. My servers had been down for hours, so I opened a support ticket, and one of the agents replied and told me that the downtime was due to an upgrade in their network.
Again, I came to conclude that it could be far worst, so I stayed, one of the reasons was that I didn't want to switch my game servers over. It's important to keep in mind when you are running game servers, IPs play an important part because that's where you get your traffic. Near January the network upgrade at Limestonenetworks was still taking place which caused my bandwidth meter to stop working. This really scared me because I didn't want to get charged for overages due to the fact that my servers were receiving DDOS attacks, and I wouldn't know when to close the ports.
This incident actually turned out to be positive for me because even though I went over my bandwidth quota they didn't charge me for overages. I was very happy because this was like a late Christmas present, so now I was even more happy to give my money to Limestonenetworks. Now you might ask the question, how is this going downhill? Even though they didn't charge me for the overages, I still lost many clients who were angry at the fact that their game server were down.
In the end this network upgrade actually cost me 3 clients who were paying ~$60 per month. I let this slide because at this point I already had two servers with Limestonenetworks and I really didn't want to switch over due to the fact I would lose my IPs. The next month, February, was no different, I had more issues with Limestonenetworks. Starting of this month I was getting large DDOS attacks, which kept pushing my bandwidth over the quota, and I ended up paying close to $200 dollars just for bandwidth overages.
At this point they started to nickel and dime me for every single penny they could get of me. I don't know if they were having financial problems, or if it was due to another reason. Again in March I went over the quota, but at this time they told me that I had to pay per gigabyte which would result in a $500+ charge in bandwidth, and after talking with multiple agents, I was finally able to reach an agreement. They had changed a policy all of the sudden due to the fact that they knew I was a good customer and would keep paying for the overages.
The problem I had here was that I didn't mind upgrading to plan after I knew how much bandwidth was going to be used, since they don't offer any sort of DDOS protection, and game servers result in large DDOS attacks occasionally. I understand that Limestonenetworks was not at fault, but by making me pay per gigabyte was a bit harsh, since I had never been late on a payment, and had multiple servers. Try to remember that I stayed with this company even though I lost multiple clients because of their network outages, but they didn't care about this, all the care about is nickling and diming customers.
From that point on I have been living on the edge because I don't want to pay for an upgrade before hand due to the fact I don't know how much bandwidth my server will be using. Even if I upgrade to a different package it does not offer an insurance due to the fact that if I receieve a large DDOS than I orignally predicted, I would still end up paying per gigabyte.
This company has turned from having potential to just making their customers run away. Now the other problems I had with Limestonenetwork is the support they offer, which has been declining since I joined. The associates are very rude and don't really care about the customer's experience. I didn't include every problem I had with Limestonenetwork because it would make it a very long read.
Network - 10/10
Downtime - 5/10
Customer Service - 2/10
Overall Experience - 4/10
Would I recommend this company? NO, I urge everyone to stay away, unless they like to deal with problems on a daily basis.
Also from reading other topics on this forum, I personally believe that Limestonenetwork is overselling and their network can not handle the load.
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 havent been so dissapointed for a long time..
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.
Do you have some experiences with Lunarpages.com ?
I purchased win host and I have some negative experiences with them at this time.
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 RelatedI 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......
View 5 Replies View RelatedCSF 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"
I need some experience suggestions, are they good ?
View 5 Replies View RelatedI'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...
