@Abhishek,
In your AWS account add a LoadBalancer in front of your ec2 instance.
Also allow TCP traffic on ports 5222 and 5223 to flow through and forward
to ec2 instance.
Configure your ec2 security group to allow incoming traffic only from your
load balancer.
Regards
Vaibhav
On Fri, Apr
Thank you for the reply Vaibhav.
I actually just solved the issue.
The problem was that in the AWS server instance -> security groups
I just needed to add support for xmpp messages to flow. I just allowed the
traffic to flow and All protocols to be used(as there isn't any option for XMPP
Are the ports exposed and are you using the correct url to connect to your
xmpp server?
Regards
Vaibhav
On Fri, Apr 21, 2017 at 4:20 PM, Abhishek Ranjan
wrote:
> Hi,
>
> I am a xmpp noob. I have installed ejabberd over a linux instance in AWS
> server. I wanted to
Hi,
I am a xmpp noob. I have installed ejabberd over a linux instance in AWS
server. I wanted to connect to this server using a client named Pidgin. I have
created a new user on ejabberd on the AWS server. But when I am using this user
to connect to the ejabberd on AWS server I am not able to