I'm running a GCM service on one EC2 server (with Elastic IP) for a while
now. When moving the service to a different server (that doesn't have EIP),
i get connection refused from GCM. I'm mentioning EIP because I'm
suspecting it at the moment.
I'm using the browser key (simple auth) because it gives me the best
flexibility, and it seems that at the first days of GCM the server key
refused to work.
I'm also not limiting any referrers or IPs at the key's side.
Anyone knows why might that be? is GCM "learning" the IPs I usually use? or
is there a global block on AWS EC2 IPs other than Elastic IPs?