Agent doesn't connect

aviramsh

Hello,

I've been trying to use CloudSMS product.
My server is an EC2 server. I have used wget to download the agent, and then installed it, as explained in site.

I got the following message:

Uncompressing StillSecure Agent.......
OK to execute: ./installer-linux.sh ? [Y/n] y

################# Please note ####################
# Once the Cloud Security Agent is installed, #
# all incoming network traffic to this cloud #
# server will be blocked. After completing the #
# installation, log in to the StillSecure #
# Network Security Portal, attach this cloud #
# server, and create firewall rules for outside #
# services which need to communicate with this #
# server. #
##################################################

I noticed that the incoming connections are blocked (which means that agent is working). But, on the dashboard, i see agent status "no connection".
Hope you can help,

Thanks,
Aviram

ss_steve

Aviram,
Thanks for trying the Cloud Security Management Service!

The most likely cause of this is that your Cloud server is not accessible via the public internet. In order to manage your Cloud security settings we need to be able to access the server and specifically the service port: 4407.

If our server does not have access to your Cloud server that will keep us from connecting. If you have any intervening firewalls or NAT routers between your server and the Public internet we may not connect to your server.

If you are sure that's not the problem, please let us know what OS version your Cloud server is running so that we might help you more specifically.
--
StillSecure_Steve
Sr. Engineer

For more information about Cloud SMS, please visit us at:
http://www.stillsecure.com/cloud-sms

aviramsh

Hello Steve,

My cloud server is an Amazon EC2 server, running Red Hat 6.1 64bit.
Server is accessible through the internet. When i use netstat, i see that 4407 is open and SSCloudSecAgen is listening.
Its ip is 122.248.200.189. I still see "no connection".
Please advice,
Thanks,
Aviram

ss_steve

Aviram,
Thanks for the reply.

Is it possible that port 4407 is being blocked by the Amazon Security Process? I know they have most non-standard ports locked down by default, although you should be able to manage those yourself.
--
StillSecure_Steve
Sr. Engineer

For more information about Cloud SMS, please visit us at:
http://www.stillsecure.com/cloud-sms

aviramsh

Hi,
On the bottom line, port 4407 is enabled in iptables. Hence, communication is enabled.
Do you have other idea? I must say that the printing that the installation outputs are not informative at all. As a user, i couldn't tell whether installation continues, finished successfully, failed etc.
Thanks for your assistance,
Aviram

ss_steve

Aviram,
So we looked at this from our side and discovered that we still cannot access your server port 4407 from our server. So something is blocking it.

Here is our recommendation:

Please open all ports in the Amazon Security Group configuration for the cloud instance in question by:
a. Click the Amazon EC2 tab at the top of the screen
b. Click “Security Groups” on the left side of the screen
c. Select the security group of which the EC2 instance is a member (you can see this by clicking Instances on the left hand side of the screen, and looking at the “Security Groups” column for the instance in question).
d. Click the “Inbound” tab in the lower left pane
e. Allow all ports inbound (1-65535) for source 0.0.0.0/0 on TCP, UDP
f. Allow all ICMP inbound
--
StillSecure_Steve
Sr. Engineer

For more information about Cloud SMS, please visit us at:
http://www.stillsecure.com/cloud-sms

Howdy, Stranger!

Categories