Thanks for the help, the mistake was all mine, the receiving address was wrong, and that is why the miner won't connect.

Quote from: jedixjarf on November 27, 2013, 09:30:22 PM

Quote from: bit on November 27, 2013, 02:25:51 PM
Hello all, I am trying to mine with ptsminer, under Debian 7 on 2 clouds (IaaS) now, and the two of them are saying
"connecting to 54.201.26.128:1337
no connection to the server, reconnecting in 10 seconds"

apparently 1337 port is closed, I tried adding a firewall rule, but that does not seem to fix the problem. The one cloud provider is running Open Stack:

here is how I added the firewall rule:
http://docs.openstack.org/user-guide/content/Launching_Instances_using_Dashboard.html#security_groups_add_rule

Can you help me?

While SSH'd into the server do this.

Code Select Expand

telnet 54.201.26.128 1337


That will tell you if you can hit the port or not.

I tried that and the screen goes blank, I think that I connects, but still when I run the miner, I says no Connection trying to reconnect. This is with ptsbeeer miner, the same goes for the pts coyote miner. Now I am trying to download the cpu miner of pts pool, to see if I will get a result.

Btw, the cloud instance that I am trying is Google Compute Engine, does anyone has experience with that?

Hello all, I am trying to mine with ptsminer, under Debian 7 on 2 clouds (IaaS) now, and the two of them are saying
"connecting to 54.201.26.128:1337
no connection to the server, reconnecting in 10 seconds"

apparently 1337 port is closed, I tried adding a firewall rule, but that does not seem to fix the problem. The one cloud provider is running Open Stack:

here is how I added the firewall rule:
http://docs.openstack.org/user-guide/content/Launching_Instances_using_Dashboard.html#security_groups_add_rule

Can you help me?