Until recently everything was working well, but suddenly I can't get anybody to sync. I'm not sure if it's the code, my configuration, or just the Armory being its usual flaky self. I just did a fresh install of the [372], but things are still funky.

Is anybody else having trouble?

Roster Warning line 1026: UrlGrabber Error [CURL]: connect() timed out!
lib/functions.lib.php Roster Warning line 1026: UrlGrabber Error [CURL]: couldn't connect to host
lib/functions.lib.php Roster Warning line 1026: UrlGrabber Error [CURL]: couldn't connect to host

Having the same issues from multiple locations, 155mbit server's located in multiple places each server is using different software however they are all GNU products,

Apache 1.3
Litehttpd

and mainly Apache 2.2.8

All cURL and Curl Wrappers are installed on these boxes' however the sync fails.

I'm pretty sure AT&T's new bandwidth uplinks may have something to do with this, such as packet filtering massive connections from the same IP/14 block to prevent potential ddos attacks.

-2cents

I don't know what the issue is, or what information to report to help, but my sync'ing starts out fine... gets done 10-15 or so characters, then all failures. During the failures I can see access the WoW Armory just fine.

Well, this seems to be new ddos filter at blizzard. No idea yet how to handle this.

poetter wrote:Well, this seems to be new ddos filter at blizzard. No idea yet how to handle this.

Ahh, that makes sense.

well this answers my question >_<

I've noticed a couple posts on the official forums from other people asking about this, so it's not just us who are having the problem.

Here's hoping they work something out. I'd hate to have to go back to pestering my guildies to update their profiles again.

i hope not but we know blizzard. they would rather the players be using their stuff than some 3rd party work. >_<

Very true unfortunately, despite the fact that their stuff is slow, impossible to depend on, lacks 90% of the features and things the community likes to use. They can't even keep up their own fora on a stabile basis.

Oh well, here's to hoping Vivendi some day gets crushed and replaced by actual Blizzard people.

Can I suggest that Sync process has a configurable timer between downloads?

This means that perhaps we can set a character retrieval delay to fox the DDoS security.

Also, perhaps setiings like a "linear' or "round robin" on grabbing the infor could be good. Linear would be from the top down, Round Robin would be a progressive download feature.

Just a couple of thoughts.

poetter wrote:Well, this seems to be new ddos filter at blizzard. No idea yet how to handle this.

Just add a timer, very simple with php to allow users to set the time per character and reduce your ddos like flood of connections to blizzard.

My personal fix was to deploy multiple ips at once but not all users own multiple C class's.

moofa wrote:

poetter wrote:Well, this seems to be new ddos filter at blizzard. No idea yet how to handle this.

Just add a timer, very simple with php to allow users to set the time per character and reduce your ddos like flood of connections to blizzard.

My personal fix was to deploy multiple ips at once but not all users own multiple C class's.

Just to add aswell, you should make it send a user agent like this, allowing it to pass through the filter quicker.

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.7) Gecko/20080214 Firefox/3.0.0

That will solve more problems then you would think...

moofa wrote:

moofa wrote:

poetter wrote:Well, this seems to be new ddos filter at blizzard. No idea yet how to handle this.

Just add a timer, very simple with php to allow users to set the time per character and reduce your ddos like flood of connections to blizzard.

My personal fix was to deploy multiple ips at once but not all users own multiple C class's.

Just to add aswell, you should make it send a user agent like this, allowing it to pass through the filter quicker.

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.7) Gecko/20080214 Firefox/3.0.0

That will solve more problems then you would think...

Very very good suggestion.

Looking forward to the next release!

moofa wrote:

moofa wrote:

poetter wrote:Well, this seems to be new ddos filter at blizzard. No idea yet how to handle this.

Just add a timer, very simple with php to allow users to set the time per character and reduce your ddos like flood of connections to blizzard.

My personal fix was to deploy multiple ips at once but not all users own multiple C class's.

Just to add aswell, you should make it send a user agent like this, allowing it to pass through the filter quicker.

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.7) Gecko/20080214 Firefox/3.0.0

That will solve more problems then you would think...

Code: Select all

    function _setUserAgent( $armory ) {
      global $roster;

      $userAgent = 'Mozilla/5.0 (Windows; U; Windows NT 5.1; ';
      switch ( $roster->config['locale'] ) {
         case 'enUS': $userAgent .= 'en-US';
            break;

         case 'deDE': $userAgent .= 'de-DE';
            break;

         case 'frFR': $userAgent .= 'fr-FR';
            break;

         case 'esES': $userAgent .= 'es-ES';
            break;
      }

      $userAgent .= '; rv:1.8.1.1) Gecko/20061204 Firefox/2.0.0.1';
      $armory->setUserAgent($userAgent);

   }

The ddos firewall is reading the user agent right here.

I have circumvented this problem using 12 ips to go at once and using $rand() to choose other agents per request(ip)

Simple fix, plus who use's firefox 2.0.0.1 That browser has XSS expliots, and blizzards firewall does indeed filter it after 4 connections.

Just to add, the user agent alone does not fix this on a single ip server.

However a cache can be created by syncing over a long period of time.

Interval has to be very high, 4-8 minutes per 1 or your getting locked out while socketing to the server, Ironically if you lynx wowarmory.com with the same locked out IP address you will connect with no issues.

The problem lays in the method currently being used to grab information, Async- is like a SYN flood to the server then ATT&T's firewall kicks in and ploop you get filtered data, and if you debug the data, the information is actually there however, you get malformed reply headers to c**k block the armory call's.

Blizzard is cheap and out bound bandwidth from ATTENS is expensive ( very ) We use it

@poetter if you need any help or a clean workspace just PM me.