Grrr... 1and1 'auto-block' has blocked my home IP address

Pages: << < (2/3) > >>

W3DRM:

Ken, they should hire us to write their specs. That would solve the whole problem :lol: \:D/

I agree, it's probably just a new algorithm or a perhaps new person that has caused the problem. I have always wondered why the support techs don't have direct access to the other groups who activated the block. Maybe they're in a different country...

saratogaWX:

I think they have 'internal firewalls' to prevent the 1st level responders from directly communicating with the server admins and or security admins except through passing data via internal trouble tickets.  I strongly suspect (based on the accents), the 1st level tech support is based offshore and the server admins/security admins are likely based at the actual datacenters (but don't respond except to internal trouble tickets).

Cienega32:

1&1 with ComCast ISP providing the data and I don't think I noticed anything "stalled" on my site in that time frame. I'm on the road but I usually check the data times on the site to see if I still have a presence. Didn't notice anything odd but I don't send as much data per day.

saratogaWX:

AFAIK, it was only my home IP address that was blocked.  I did get a (mostly nonspecific) reply from tech support saying Quote
--
Dear Ken True, (Customer ID: ********)
 
Thank you for contacting us.
 
We have verified that your IP address was blocked by our firewall.  This is due
to one or several reasons listed below.
 
1. Too many failed authentication attempts on the server.
 
2. Too many attempts to log in without providing the password information.
 
3. Too many connections to the server.
 
Please try to reconnect 4 hours after your last connection attempt. To prevent
this from reoccurring in the future, we strongly recommend to adjust your
settings to less than 5 concurrent connections.
 
If you have any further questions please do not hesitate to contact us.

--
Well, (1) and (2) were not caused from my home systems (since no change in FTP setup/credentials was done and they had been working fine).

I suspect (3) may have been the cause .. they've not said how many concurrent FTP connections you can have, but here are the programs with direct FTP usage:

Weather-Display (1 constant connection for clientrawrealtimeftp with 5 second uploads, 1 connection every 5 minutes for main FTP upload)
Cumulus (1 connection every 5 minutes for main FTP, 1 realtime.txt update every 10 seconds)
GRLevel3 (1 connection every 10 minutes)
WASP2   (1 connection every 5 minutes)
Fling (1 connection constantly - handles VWS, Meteohub, WeatherLink, WeatherCat, WeatherSnoop file uploads)

so I see how I could have 8 connections from weather software, and maybe one from me via Dreamweaver to update the site.  Doesn't sound to onerous on their FTP server.

I'm setting up a local FTP server to be the target for WASP2 uploads, then add the local folders to the Fling list of sites.  That would reduce concurrent connections by 2.  I tried it with GRLevel3, but it really slowed down the Fling processing, so best to let GRLevel3 handle the FTP upload directly.

Cienega32:

I thought I remember seeing 5 concurrent FTP connects but that may have been with my original basic Home plan. Or it may have been something I overheard in a dream about milkshakes - I really can't remember but it (5) sounds familiar from somewhere.

I sure hope you get it squared away without any major issues.

Pages: << < (2/3) > >>