Bravo List
Register
Go Back   > Bravo List > P2P > Forum > Community Cafe
Reply
  #1  
Old 29th March 2020, 15:31
Napon's Avatar
Napon Napon is offline
Senior Member
 
Join Date: Feb 2016
P2P
Posts: 521
Thumbs down LeaseWeb Netherlands B.V Dossing server
headup about LeaseWeb Netherlands B.V Dossing server


Today a very good mate asked me to set him a site up on new domain with in 20min LeaseWeb starting to Doss hes site here in the info for all to ban there ip and all hope this help one and all out..ive done my reading up on this too LeaseWebare quite good at this to try and sell there servers by Dossing server new sites


https://www.ip-adress.com/ip-address/ipv4/5.79.98.223
PTR Resource Record hosted-by.seedhost.eu
2020-03-29 13:30:07 Error 5.79.98.223 548#0: *132 connect() failed (111: Connection refused) while connecting to upstream nginx error
2020-03-29 13:30:08 Error 5.79.98.223 548#0: *134 connect() failed (111: Connection refused) while connecting to upstream nginx error
2020-03-29 13:30:08 Error 5.79.98.223 548#0: *135 connect() failed (111: Connection refused) while connecting to upstream nginx error
2020-03-29 13:30:09 Error 5.79.98.223 548#0: *138 connect() failed (111: Connection refused) while connecting to upstream nginx error
2020-03-29 13:30:11 Error 5.79.98.223 548#0: *140 connect() failed (111: Connection refused) while connecting to upstream nginx error
2020-03-29 13:30:11 Error 5.79.98.223 548#0: *141 connect() failed (111: Connection refused) while connecting to upstream nginx error
2020-03-29 13:30:12 Error 5.79.98.223 548#0: *144 connect() failed (111: Connection refused) while connecting to upstream nginx error
2020-03-29 13:30:13 Error 5.79.98.223 548#0: *146 connect() failed (111: Connection refused) while connecting to upstream nginx error
2020-03-29 13:30:17 Error 5.79.98.223 548#0: *148 connect() failed (111: Connection refused) while connecting to upstream nginx error
2020-03-29 13:30:17 Error 5.79.98.223 548#0: *149 connect() failed (111: Connection refused) while connecting to upstream nginx error
2020-03-29 13:30:18 Error 5.79.98.223 548#0: *152 connect() failed (111: Connection refused) while connecting to upstream nginx error
2020-03-29 13:30:21 Error 5.79.98.223 548#0: *154 connect() failed (111: Connection refused) while connecting to upstream nginx error
2020-03-29 13:30:24 Error 5.79.98.223 548#0: *156 connect() failed (111: Connection refused) while connecting to upstream nginx error
2020-03-29 13:30:25 Error 5.79.98.223 548#0: *158 connect() failed (111: Connection refused) while connecting to upstream nginx error
2020-03-29 13:30:25 Error 5.79.98.223 548#0: *159 connect() failed (111: Connection refused) while connecting to upstream nginx error
2020-03-29 13:30:34 Error 5.79.98.223 548#0: *162 connect() failed (111: Connection refused) while connecting to upstream nginx error
2020-03-29 13:30:34 Error 5.79.98.223 548#0: *163 connect() failed (111: Connection refused) while connecting to upstream nginx error
2020-03-29 13:31:13 Error 5.79.98.223 548#0: *166 connect() failed (111: Connection refused) while connecting to upstream nginx error
2020-03-29 13:31:17 Error 5.79.98.223 548#0: *168 connect() failed (111: Connection refused) while connecting to upstream nginx error
2020-03-29 13:31:42 Error 5.79.98.223 548#0: *172 connect() failed (111: Connection refused) while connecting to upstream nginx error
2020-03-29 13:31:42 Error 5.79.98.223 548#0: *173 connect() failed (111: Connection refused) while connecting to upstream nginx error
2020-03-29 13:31:42 Error 5.79.98.223 548#0: *176 connect() failed (111: Connection refused) while connecting to upstream nginx error
2020-03-29 13:31:42 Error 5.79.98.223 548#0: *177 connect() failed (111: Connection refused) while connecting to upstream nginx error
2020-03-29 13:31:42 Error 5.79.98.223 548#0: *175 connect() failed (111: Connection refused) while connecting to upstream nginx error
2020-03-29 13:31:42 Error 5.79.98.223 548#0: *174 connect() failed (111: Connection refused) while connecting to upstream nginx error
2020-03-29 13:31:44 Error 5.79.98.223 548#0: *184 connect() failed (111: Connection refused) while connecting to upstream nginx error
2020-03-29 13:31:45 Error 5.79.98.223 548#0: *186 connect() failed (111: Connection refused) while connecting to upstream nginx error
2020-03-29 13:31:46 Error 5.79.98.223 548#0: *188 connect() failed (111: Connection refused) while connecting to upstream nginx error
2020-03-29 13:31:48 Error 5.79.98.223 548#0: *190 connect() failed (111: Connection refused) while connecting to upstream nginx error
2020-03-29 13:31:49 Error 5.79.98.223 548#0: *192 connect() failed (111: Connection refused) while connecting to upstream nginx error
2020-03-29 13:31:50 Error 5.79.98.223 548#0: *195 connect() failed (111: Connection refused) while connecting to upstream nginx error
2020-03-29 13:31:50 Error 5.79.98.223 548#0: *194 connect() failed (111: Connection refused) while connecting to upstream nginx error
2020-03-29 13:31:50 Error 5.79.98.223 548#0: *196 connect() failed (111: Connection refused) while connecting to upstream nginx error
2020-03-29 13:31:53 Error 5.79.98.223 548#0: *200 connect() failed (111: Connection refused) while connecting to upstream nginx error
2020-03-29 13:31:53 Error 5.79.98.223 548#0: *201 connect() failed (111: Connection refused) while connecting to upstream nginx error
2020-03-29 13:31:58 Error 5.79.98.223 548#0: *204 connect() failed (111: Connection refused) while connecting to upstream nginx error
2020-03-29 13:31:58 Error 5.79.98.223 548#0: *205 connect() failed (111: Connection refused) while connecting to upstream nginx error
2020-03-29 13:31:58 Error 5.79.98.223 548#0: *206 connect() failed (111: Connection refused) while connecting to upstream nginx error
2020-03-29 13:31:59 Error 5.79.98.223 548#0: *210 connect() failed (111: Connection refused) while connecting to upstream nginx error
2020-03-29 13:32:04 Error 5.79.98.223 548#0: *212 connect() failed (111: Connection refused) while connecting to upstream nginx error
2020-03-29 13:32:22 Error 5.79.98.223 548#0: *218 connect() failed (111: Connection refused) while connecting to upstream nginx error
2020-03-29 13:32:22 Error 5.79.98.223 548#0: *219 connect() failed (111: Connection refused) while connecting to upstream nginx error
2020-03-29 13:32:23 Error 5.79.98.223 548#0: *222 connect() failed (111: Connection refused) while connecting to upstream nginx error
2020-03-29 13:32:24 Error 5.79.98.223 548#0: *224 connect() failed (111: Connection refused) while connecting to upstream nginx error
2020-03-29 13:32:25 Error 5.79.98.223 548#0: *226 connect() failed (111: Connection refused) while connecting to upstream nginx error
2020-03-29 13:32:25 Error 5.79.98.223 548#0: *227 connect() failed (111: Connection refused) while connecting to upstream nginx error
2020-03-29 13:32:25 Error 5.79.98.223 548#0: *228 connect() failed (111: Connection refused) while connecting to upstream nginx error
2020-03-29 13:32:25 Error 5.79.98.223 548#0: *229 connect() failed (111: Connection refused) while connecting to upstream nginx error
2020-03-29 13:32:26 Error 5.79.98.223 548#0: *234 connect() failed (111: Connection refused) while connecting to upstream nginx error
2020-03-29 13:32:27 Error 5.79.98.223 548#0: *236 connect() failed (111: Connection refused) while connecting to upstream nginx error
2020-03-29 13:32:29 Error 5.79.98.223 548#0: *238 connect() failed (111: Connection refused) while connecting to upstream nginx error
2020-03-29 13:32:29 Error 5.79.98.223 548#0: *239 connect() failed (111: Connection refused) while connecting to upstream nginx error
2020-03-29 13:32:30 Error 5.79.98.223 548#0: *244 connect() failed (111: Connection refused) while connecting to upstream nginx error
2020-03-29 13:32:31 Error 5.79.98.223 548#0: *246 connect() failed (111: Connection refused) while connecting to upstream nginx error
2020-03-29 13:32:32 Error 5.79.98.223 548#0: *248 connect() failed (111: Connection refused) while connecting to upstream nginx error
2020-03-29 13:32:38 Error 5.79.98.223 548#0: *250 connect() failed (111: Connection refused) while connecting to upstream nginx error
2020-03-29 13:32:39 Error 5.79.98.223 548#0: *252 connect() failed (111: Connection refused) while connecting to upstream nginx error
2020-03-29 13:32:41 Error 5.79.98.223 548#0: *254 connect() failed (111: Connection refused) while connecting to upstream nginx error
2020-03-29 13:32:46 Error 5.79.98.223 548#0: *256 connect() failed (111: Connection refused) while connecting to upstream nginx error
2020-03-29 13:32:53 Error 5.79.98.223 548#0: *258 connect() failed (111: Connection refused) while connecting to upstream nginx error
2020-03-29 13:32:55 Error 5.79.98.223 548#0: *260 connect() failed (111: Connection refused) while connecting to upstream nginx error
2020-03-29 13:33:01 Error 5.79.98.223 548#0: *262 connect() failed (111: Connection refused) while connecting to upstream nginx error
2020-03-29 13:35:27 Error 5.79.98.223 548#0: *264 connect() failed (111: Connection refused) while connecting to upstream nginx error
2020-03-29 13:35:28 Error 5.79.98.223 548#0: *266 connect() failed (111: Connection refused) while connecting to upstream nginx error
2020-03-29 13:35:28 Error 5.79.98.223 548#0: *267 connect() failed (111: Connection refused) while connecting to upstream nginx error
2020-03-29 13:35:29 Error 5.79.98.223 548#0: *270 connect() failed (111: Connection refused) while connecting to upstream nginx error
2020-03-29 13:35:31 Error 5.79.98.223 548#0: *272 connect() failed (111: Connection refused) while connecting to upstream nginx error
2020-03-29 13:35:31 Error 5.79.98.223 548#0: *273 connect() failed (111: Connection refused) while connecting to upstream nginx error
2020-03-29 13:35:32 Error 5.79.98.223 548#0: *276 connect() failed (111: Connection refused) while connecting to upstream nginx error
2020-03-29 13:35:33 Error 5.79.98.223 548#0: *278 connect() failed (111: Connection refused) while connecting to upstream nginx error
2020-03-29 13:35:37 Error 5.79.98.223 548#0: *281 connect() failed (111: Connection refused) while connecting to upstream nginx error
2020-03-29 13:35:37 Error 5.79.98.223 548#0: *280 connect() failed (111: Connection refused) while connecting to upstream nginx error
2020-03-29 13:35:38 Error 5.79.98.223 548#0: *284 connect() failed (111: Connection refused) while connecting to upstream nginx error
2020-03-29 13:35:41 Error 5.79.98.223 548#0: *286 connect() failed (111: Connection refused) while connecting to upstream nginx error
2020-03-29 13:35:44 Error 5.79.98.223 548#0: *288 connect() failed (111: Connection refused) while connecting to upstream nginx error
2020-03-29 13:35:45 Error 5.79.98.223 548#0: *290 connect() failed (111: Connection refused) while connecting to upstream nginx error
2020-03-29 13:35:45 Error 5.79.98.223 548#0: *291 connect() failed (111: Connection refused) while connecting to upstream nginx error
2020-03-29 13:35:54 Error 5.79.98.223 548#0: *295 connect() failed (111: Connection refused) while connecting to upstream nginx error
2020-03-29 13:35:54 Error 5.79.98.223 548#0: *294 connect() failed (111: Connection refused) while connecting to upstream nginx error
2020-03-29 13:36:33 Error 5.79.98.223 19433#0: *306 connect() failed (111: Connection refused) while connecting to upstream nginx error
2020-03-29 13:36:37 Error 5.79.98.223 19433#0: *308 connect() failed (111: Connection refused) while connecting to upstream nginx error
__________________

Last edited by Napon; 29th March 2020 at 16:09.
Reply With Quote
  #2  
Old 29th March 2020, 18:13
rio's Avatar
rio rio is offline
Senior Member
 
Join Date: May 2019
P2P
Posts: 36
Default
that's strange I have used lb in the pass and they are quite reliable and there network is one of the best in Europe its hard to believe that they would do something like this.
__________________
Live Free... Share Free...
Reply With Quote
  #3  
Old 29th March 2020, 18:46
Napon's Avatar
Napon Napon is offline
Senior Member
 
Join Date: Feb 2016
P2P
Posts: 521
Default
Well the Evidence is there what they do
Just heads up with it yes they been doing this just over this 18 months now
__________________
Reply With Quote
  #4  
Old 29th March 2020, 19:01
rio's Avatar
rio rio is offline
Senior Member
 
Join Date: May 2019
P2P
Posts: 36
Default
It's Also depends on the server if it's a used one or a new one with used servers it's very normal
__________________
Live Free... Share Free...
Reply With Quote
  #5  
Old 29th March 2020, 19:05
Napon's Avatar
Napon Napon is offline
Senior Member
 
Join Date: Feb 2016
P2P
Posts: 521
Default
no doing it to very new servers ddosing them also old servers too to put a top on it they should not be ddoding server full stop

my mate as no server with them at all very new
__________________
Reply With Quote
  #6  
Old 29th March 2020, 19:10
rio's Avatar
rio rio is offline
Senior Member
 
Join Date: May 2019
P2P
Posts: 36
Default
That is very odd
__________________
Live Free... Share Free...
Reply With Quote
  #7  
Old 29th March 2020, 21:51
thartley55's Avatar
thartley55 thartley55 is offline
Senior Member
 
Join Date: Mar 2012
P2P
Posts: 108
Default
Just to throw something out there...
It is a LeaseWeb IP, granted.
But, does that mean that "LeaseWeb" is doing the ddos-ing? Are "they" responsible, or is an individual, renting a LeaseWeb server actually guilty of the ddos-ing?
Just playing devil's-advocate here.
Reply With Quote
  #8  
Old 29th March 2020, 23:56
Napon's Avatar
Napon Napon is offline
Senior Member
 
Join Date: Feb 2016
P2P
Posts: 521
Default
this true ive got on to LeaseWeb and the ddose as stoped as ive told then ive reported them so yes it was LeaseWeb also the mate i did the site for is now working but on a side note ive installed him a shell App to stop all ddose
Brute Force attacks by anyone for free for him that should cost money but there you what you do for a mate
__________________
Reply With Quote
The Following User Says Thank You to Napon For This Useful Post:
thartley55 (29th March 2020)
  #9  
Old 30th March 2020, 02:59
MasterMan's Avatar
MasterMan MasterMan is offline
Senior Member
 
Join Date: Jan 2012
P2P
Posts: 86
Default
i believe LW can do this coz i had sour experience with them in the past years back in 2003 when xam just released his free 1.3 his non-free TS 3.1 script ...



for the start, they broke my dedicated HD a couple of times and i had to redo my site a couple of times .. then, they raised the server price i used with them for 2 years to more then 30% of what i originally paid for 2 years in advance :(


at the time, i decide to quite their service and it was the right decision coz i moved on to much better once i'm with since 2005 until now :)


my 2 cents tip in this subject
Reply With Quote
  #10  
Old 30th March 2020, 08:36
Napon's Avatar
Napon Napon is offline
Senior Member
 
Join Date: Feb 2016
P2P
Posts: 521
Default
Yes im now getting a few owners now wanting my help why LeaseWeb dosseing there server too so ive got some work on today also they do not have server with them i can see this is going to get bad with
LeaseWeb dossing servers over the next few months...Also looked on there servers LeaseWeb is banned from server end from there Plesk pan so yes this is true or Plesk would not add LeaseWeb ips to there platform why LeaseWeb are known for dossing servers ......what they are doing is a Brute Force attacks
__________________

Last edited by Napon; 30th March 2020 at 08:47.
Reply With Quote
Reply

Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump



All times are GMT +2. The time now is 17:24. vBulletin skin by ForumMonkeys. Powered by vBulletin® Version 3.8.11 Beta 3
Copyright ©2000 - 2020, vBulletin Solutions Inc.