We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
Not exactly the question you had in mind?
Sign up for an EE membership and get your own personalized solution. With an EE membership, you can ask unlimited troubleshooting, research, or opinion questions.
Hi Anthony - I am using standalone.bat to start the server
so I updated the standalone.xml as below
<interfaces>
<interface name="management">
<inet-address value="${jboss.bind.address.management:0.0.0.0}"/>
</interface>
<interface name="public">
<inet-address value="${jboss.bind.address:0.0.0.0}"/>
</interface>
<interface name="unsecure">
<inet-address value="${jboss.bind.address.unsecure:0.0.0.0}"/>
</interface>
</interfaces>
removed all 127.0.0.1 to 0.0.0.0
coming to EC2 I edited scurity group as below
Type = All traffic
Protocol: All
port: All
source: 0.0.0.0/0
Thanks
This is the best money I have ever spent. I cannot not tell you how many times these folks have saved my bacon. I learn so much from the contributors.
so I updated the standalone.xml as below
<interfaces>
<interface name="management">
<inet-address value="${jboss.bind.addres
</interface>
<interface name="public">
<inet-address value="${jboss.bind.addres
</interface>
<interface name="unsecure">
<inet-address value="${jboss.bind.addres
</interface>
</interfaces>
removed all 127.0.0.1 to 0.0.0.0
coming to EC2 I edited scurity group as below
Type = All traffic
Protocol: All
port: All
source: 0.0.0.0/0
Thanks