Port not opening even after adding security group rules on Amazon EC2 instanceAmazon ec2 Public DNS not...

Can "semicircle" be used to refer to a part-circle that is not a exact half-circle?

If the Captain's screens are out, does he switch seats with the co-pilot?

Can the druid cantrip Thorn Whip really defeat a water weird this easily?

"However" used in a conditional clause?

Humans have energy, but not water. What happens?

How does Dispel Magic work against Stoneskin?

What wound would be of little consequence to a biped but terrible for a quadruped?

Prove that the total distance is minimised (when travelling across the longest path)

Counter-example to the existence of left Bousfield localization of combinatorial model category

When is a batch class instantiated when you schedule it?

Single word request: Harming the benefactor

How could a female member of a species produce eggs unto death?

What happens with multiple copies of Humility and Glorious Anthem on the battlefield?

Straight line with arrows and dots

Make a transparent 448*448 image

Force user to remove USB token

Replacing Windows 7 security updates with anti-virus?

Word for a person who has no opinion about whether god exists

Silly Sally's Movie

Best approach to update all entries in a list that is paginated?

Do items de-spawn in Diablo?

Is having access to past exams cheating and, if yes, could it be proven just by a good grade?

Is it ok to include an epilogue dedicated to colleagues who passed away in the end of the manuscript?

Is going from continuous data to categorical always wrong?



Port not opening even after adding security group rules on Amazon EC2 instance


Amazon ec2 Public DNS not workingAmazon EC2 - No SSH After Reboot, Connection Refusedtcp port 12202 not opening on ubuntu EC2 instanceHow to list EC2 security group *rules* from within instance?EC2 instance not working with Amazon route 53 domain namePrivate communications between AWS EC2 instancesAmazon EC2 Security Group inbound rule with a dynamic IPAWS instance has port open in security group, ufw rule, but nmap says it's closedAmazon EC2 Nodejs port issuePort not opening













0















I have an Amazon EC2 Linux instance. I recently installed SmartFoxServer in my instance. For that I needed to open 9933 port. So I just created inbound rules on Amazon EC2 Manager console website.



My rule is




Custom - TCP Rule - TCP - 9933 - 0.0.0.0/0




But still my port is remain closed. Am unable to connect. Anything else I need to do after adding rules on security groups?



http://www.yougetsignal.com/tools/open-ports/
here in above url I checked whether my port is opened or not. Its closed










share|improve this question














bumped to the homepage by Community 15 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
















  • That site isn't a good test. I've just verified through testing that it reports everything not "open" (accepting connections) as "closed" and those are not the only possibilities, nor is it enough information. What happens if you try to connect with nc or telnet? (telnet x.x.x.x 9933)

    – Michael - sqlbot
    Feb 20 '15 at 2:42
















0















I have an Amazon EC2 Linux instance. I recently installed SmartFoxServer in my instance. For that I needed to open 9933 port. So I just created inbound rules on Amazon EC2 Manager console website.



My rule is




Custom - TCP Rule - TCP - 9933 - 0.0.0.0/0




But still my port is remain closed. Am unable to connect. Anything else I need to do after adding rules on security groups?



http://www.yougetsignal.com/tools/open-ports/
here in above url I checked whether my port is opened or not. Its closed










share|improve this question














bumped to the homepage by Community 15 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
















  • That site isn't a good test. I've just verified through testing that it reports everything not "open" (accepting connections) as "closed" and those are not the only possibilities, nor is it enough information. What happens if you try to connect with nc or telnet? (telnet x.x.x.x 9933)

    – Michael - sqlbot
    Feb 20 '15 at 2:42














0












0








0








I have an Amazon EC2 Linux instance. I recently installed SmartFoxServer in my instance. For that I needed to open 9933 port. So I just created inbound rules on Amazon EC2 Manager console website.



My rule is




Custom - TCP Rule - TCP - 9933 - 0.0.0.0/0




But still my port is remain closed. Am unable to connect. Anything else I need to do after adding rules on security groups?



http://www.yougetsignal.com/tools/open-ports/
here in above url I checked whether my port is opened or not. Its closed










share|improve this question














I have an Amazon EC2 Linux instance. I recently installed SmartFoxServer in my instance. For that I needed to open 9933 port. So I just created inbound rules on Amazon EC2 Manager console website.



My rule is




Custom - TCP Rule - TCP - 9933 - 0.0.0.0/0




But still my port is remain closed. Am unable to connect. Anything else I need to do after adding rules on security groups?



http://www.yougetsignal.com/tools/open-ports/
here in above url I checked whether my port is opened or not. Its closed







linux amazon-ec2 port groups






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Feb 11 '15 at 10:22









Vinoth KannanVinoth Kannan

11




11





bumped to the homepage by Community 15 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.







bumped to the homepage by Community 15 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.















  • That site isn't a good test. I've just verified through testing that it reports everything not "open" (accepting connections) as "closed" and those are not the only possibilities, nor is it enough information. What happens if you try to connect with nc or telnet? (telnet x.x.x.x 9933)

    – Michael - sqlbot
    Feb 20 '15 at 2:42



















  • That site isn't a good test. I've just verified through testing that it reports everything not "open" (accepting connections) as "closed" and those are not the only possibilities, nor is it enough information. What happens if you try to connect with nc or telnet? (telnet x.x.x.x 9933)

    – Michael - sqlbot
    Feb 20 '15 at 2:42

















That site isn't a good test. I've just verified through testing that it reports everything not "open" (accepting connections) as "closed" and those are not the only possibilities, nor is it enough information. What happens if you try to connect with nc or telnet? (telnet x.x.x.x 9933)

– Michael - sqlbot
Feb 20 '15 at 2:42





That site isn't a good test. I've just verified through testing that it reports everything not "open" (accepting connections) as "closed" and those are not the only possibilities, nor is it enough information. What happens if you try to connect with nc or telnet? (telnet x.x.x.x 9933)

– Michael - sqlbot
Feb 20 '15 at 2:42










1 Answer
1






active

oldest

votes


















0














I had the same problem but with wildfly server instead of SmartFox server so assuming you did try telnet and/or nc and still failed to reach the server at desired port, below is the fix that might work for you as well:



Wildfly instance (in your case Smartfox), according to configration file, was binding ports (in your case, 9933) with the network inrerface lo (loopback) and not with eth0 whereas all the rules in security groups apply to the interface facing the VPC i.e. eth0.



When I tweaked my wildfly configuration file to bind the ports with right interface, everything worked as expected whereas previously I was not able to telnet/nc to destination:port






share|improve this answer























    Your Answer








    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "2"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f666718%2fport-not-opening-even-after-adding-security-group-rules-on-amazon-ec2-instance%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    0














    I had the same problem but with wildfly server instead of SmartFox server so assuming you did try telnet and/or nc and still failed to reach the server at desired port, below is the fix that might work for you as well:



    Wildfly instance (in your case Smartfox), according to configration file, was binding ports (in your case, 9933) with the network inrerface lo (loopback) and not with eth0 whereas all the rules in security groups apply to the interface facing the VPC i.e. eth0.



    When I tweaked my wildfly configuration file to bind the ports with right interface, everything worked as expected whereas previously I was not able to telnet/nc to destination:port






    share|improve this answer




























      0














      I had the same problem but with wildfly server instead of SmartFox server so assuming you did try telnet and/or nc and still failed to reach the server at desired port, below is the fix that might work for you as well:



      Wildfly instance (in your case Smartfox), according to configration file, was binding ports (in your case, 9933) with the network inrerface lo (loopback) and not with eth0 whereas all the rules in security groups apply to the interface facing the VPC i.e. eth0.



      When I tweaked my wildfly configuration file to bind the ports with right interface, everything worked as expected whereas previously I was not able to telnet/nc to destination:port






      share|improve this answer


























        0












        0








        0







        I had the same problem but with wildfly server instead of SmartFox server so assuming you did try telnet and/or nc and still failed to reach the server at desired port, below is the fix that might work for you as well:



        Wildfly instance (in your case Smartfox), according to configration file, was binding ports (in your case, 9933) with the network inrerface lo (loopback) and not with eth0 whereas all the rules in security groups apply to the interface facing the VPC i.e. eth0.



        When I tweaked my wildfly configuration file to bind the ports with right interface, everything worked as expected whereas previously I was not able to telnet/nc to destination:port






        share|improve this answer













        I had the same problem but with wildfly server instead of SmartFox server so assuming you did try telnet and/or nc and still failed to reach the server at desired port, below is the fix that might work for you as well:



        Wildfly instance (in your case Smartfox), according to configration file, was binding ports (in your case, 9933) with the network inrerface lo (loopback) and not with eth0 whereas all the rules in security groups apply to the interface facing the VPC i.e. eth0.



        When I tweaked my wildfly configuration file to bind the ports with right interface, everything worked as expected whereas previously I was not able to telnet/nc to destination:port







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Dec 22 '15 at 12:31









        Krishna GuptaKrishna Gupta

        1114




        1114






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Server Fault!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f666718%2fport-not-opening-even-after-adding-security-group-rules-on-amazon-ec2-instance%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            As a Security Precaution, the user account has been locked The Next CEO of Stack OverflowMS...

            Список ссавців Італії Природоохоронні статуси | Список |...

            Українські прізвища Зміст Історичні відомості |...