Oracle Cloud Infrastructure - General

Get Involved. Join the Conversation.

Topic

    david connell
    OCI - activate port 3000 / Node ExpressAnswered
    Topic posted June 21, 2019 by david connell, tagged Compute 
    23 Views, 4 Comments
    Title:
    OCI - activate port 3000 / Node Express
    Summary:
    Cannot access compute public IP via URL 129.***:3000
    Content:

    I have done the following -

    1.  VCN / default security list which has TCP port 3000 configured.

    2. sudo firewall-cmd --zone=public --permanent --add-port=3000/tcp

    sudo netstat -tulnp |grep httpd            tcp        0      0 0.0.0.0:80              0.0.0.0:*               LISTEN      4484/httpd

    I tried Apache on port 80 and works fine.  but have not had success w/ node.   Any feedback?

     

     

     

    Best Comment

    Robin Chatterjee

    to troubleshoot

    telnet to the port locally... does it work ?

    you did not send the output of grep 3000

    sudo netstat -apn |grep 3000

    1. temporarily turn off your system firewall if its working then the issue may be with the local firewall. if not then it's the security list...perhaps it needs more than just 3000 ?

    Comment

     

    • Robin Chatterjee

      to troubleshoot

      telnet to the port locally... does it work ?

      you did not send the output of grep 3000

      sudo netstat -apn |grep 3000

      1. temporarily turn off your system firewall if its working then the issue may be with the local firewall. if not then it's the security list...perhaps it needs more than just 3000 ?

      • Robin Chatterjee

        Is that why RDj says - i love you 3000 ? He's a node.js fan ?

      • david connell

        telnet to the port locally... does it work ?

        no.  tried via putty ssh and telnet w/ 3000

        you did not send the output of grep 3000

        sudo netstat -apn |grep 3000

        tcp6       0      0 :::3000                 :::*                    LISTEN      5359/node

         

        1. temporarily turn off your system firewall if its working then the issue may be with the local firewall. if not then it's the security list...perhaps it needs more than just 3000 ?

        access to node server via 3000 works fine on aws.  so no local firewall issue.   Security list setting seems to be setup correctly.   Not sure of other requirements.

        • david connell

          Node Express connect working.

          Lack of experience w/ OEL firewall.   No totally sure regarding how to best configure moving forward, but to connect to specific port - per your earlier comment -

          sudo systemctl stop firewalld