0

We got the problem, that our web server provider blocks our static IP address automatically, when we reach 200 simultaneous connections in the time window of 300 seconds. I'm running an Ubuntu server with an eBox on it, which could work as a gateway for limiting the connections. Which is the easiest solution? Ty.

Edit: A queue would be the best solution for all connections>200.

Erhard
  • 1
  • 1
  • Sorry, what is blocking things? – Zoredache Mar 15 '11 at 21:47
  • 4
    Uhh get a new hosting provider that doesn't throttle your connections? – Zypher Mar 15 '11 at 21:48
  • There's a few possibilities available, depending upon what behaviour you want. If I'm the 201st connection in any given 300 seconds, what do you expect me to see? An error, a timeout, a long pause, or something else? – nickgrim Mar 15 '11 at 21:59
  • A queue would be the best solution. – Erhard Mar 15 '11 at 22:17
  • 200 connections is a fair bit to one server, can your provider not whitelist your IP? whats generating so many connections? – anthonysomerset Mar 15 '11 at 22:42
  • I'm with @Zypher on this one. I've never heard of a crazy limit like that on any business grade connection. If you're on a residential connection, you're barking up the wrong tree. – Chris S Mar 15 '11 at 22:54
  • @anthonysomerset: 200 connections is trivial on any decently popular web server. I'd run far, far away from a host that started blocking connections after 200. – devicenull Mar 15 '11 at 23:47
  • the provider doesn't offer whitelisting (we would have to upgrade). we are not on a residential connection (foreign country). – Erhard Mar 16 '11 at 16:12

2 Answers2

0

If you have SSH access to your web server then run a SSH tunnel between your site and the remote site and connect through that. An example on how to do this can be found here

Everything then 'appears' as 1 connection (except for your web-server, although the connection limiting is likely not done on your web-server itself and even if it is localhost (which is where the connection will appear to be from) is normally whitelisted)

syserr0r
  • 500
  • 3
  • 10
0

Obvious thing to do here:

Call your provider, explain the problem and ask them to whitelist your IP

The other suggestion that explains tunneling all traffic trough ssh would work... But the machine that is doing the tunneling must have a really good connection in your network and be somewhat powerfull since it will be encrypting! every single thing that goes trough...

(Assuming here that these 200 connections are coming from the employees? inside the office)

HTDutchy
  • 445
  • 1
  • 4
  • 15
  • Thank you for your answers. Our provider offers a whitelisting service but only for an upgrade. The thing with the power of the "tunneler" is a good point. Yes, the 200 connections are coming from the employers (which are maybe 20 which is strange anyway). – Erhard Mar 18 '11 at 18:29