Forum: Trial server

30. Problems with clients to connect to trial server on AWS

Hello, I deployed a trial server on Amazon AWS, setup the license, and followed all the 
steps in the setup instructions.  However, when I try to use the ProPTT2 Android application to login, the connection was timing out.  I've now got it working, but wanted to mention a couple things that I had to resolve on my own.

I went through the troubleshooting list, and did have to fix the IPv6 vs IPv4 issue.

When I was logging in with my Android clients (the play store version of the ProPTT2 apps), they would try to login, but would timeout after 60 seconds.  If I used an incorrect password they would fail immediately, so I knew this was some other problem.

I found two issues that I resolved in the server configuration.

Firstly, I saw many log messages in the service logs (PTT and others) about too many files open.  To fix this I used ulimit to increase the soft limit before starting the servers.  However, I don't know if this was a root cause, or an effect of the other problem (below).

I saw problems with the PTT server connecting to the LOC server on port 41372.  This port is not listed as part of the external ports listed in the firewall or in the telnet test section.  However, the PTT server was trying to connect to this port using the AWS "external" IP address.  This AWS EC2 server had a local IP address of 172.x.x.x, but an external IP address of 18.x.x.x.  When the PTT server tried to connect to 18.x.x.x:41372 it failed.

I resolved this by extending the public TCP port range to 41372.  I'm not sure if this is required, or if this server is supposed to be internal-only.  If the latter, then the other servers should not be using the NAT address for this connection.

I've got this working now, but I'd like your feedback if I've resolved this in the correct fashion.

thanks, Jason.

Jun 29 '18 at 23:20 (GMT0) created by Jason Reich

Hi Jason,
1. Right, linux has small value for file open.
Sometimes you need to extend it.
https://dev.proptt2.com/servers-common-faq.html
2. We are using AWS also. 
I think you need to set the 172.x.x.x as a internal IP in below url.
https://18.x.x.x:40443/admin/viewHost?id=2
ProPTT2

Jul 1 '18 at 01:51 (GMT0) created by ProPTT2 dev