Correct. Try opening that and seeing if it works, I bet it does!Do I have to open port 9999 on my local server? That would mean on my home-router I should open port 9999 for incoming traffic? I did not do that, you are correct with this.
Port 0 would probably still work. I just want to verify this is why 0 is appearing.I thought only the remote machine needs port 9999 open
the elastic ip is your public static ip, and it starts with 54, the one that starts with 172 or such, is a private ip for inside the amazon intranetfirewall should be OK, i removed firewall filters and i checked the port with netcat (and also with nmap). its open from outside. I also followed chaeplins guide very carefully and I know what I am doing.
edit: only thing I did not fully understand is "elastic ip", but I activated it and it shows the same ip than the "public ip" shown there. The dns I use for ssh is also the "public ip", but if I execute "ifconfig" on the amazon server I get a different ip.
But with digital ocean I get the same problem, so it should not be amazon specific