5 Replies Latest reply on Sep 21, 2007 6:01 AM by jaikiran

    AS 4.2.1 - http://example.com:8080/ gives "Unable to connect

    konstandinos
    konstandinos Sep 21, 2007 3:23 AM

      hi

      i've recently upgraded from 4.0.5GA to 4.2.1.

      i downloaded the zip file for 4.2.1, unpacked it. i the created a system user called jboss, and chowned (recursively) the 4.2.1 folder. i've set java path and all that.

      i run.sh 4.2.1, and monitor the output - all looks ok; it loads up in 10 seconds with no complaints. but then i try access it in my browser, and i get this page: http://41.204.222.108:8080/ - firefox complains about being unable to connect etc.

      4.0.5 worked perfectly, although i had used the JEMS install for that so it may have preconfigured something that i've left out (like the port perhaps?) - but there's nothing in the installation docs besides "unpack zip file and run.sh"

      also if you go to http://41.204.222.108/ you'll notice that apache is working fine, so it's not the internet connection or my server or anything.

      any ideas?

      • 3756 Views
      • Tags:
        • 1. Re: AS 4.2.1 - http://example.com:8080/ gives
          jaikiran
          jaikiran Sep 21, 2007 3:26 AM (in response to konstandinos)

          Have a look at http://wiki.jboss.org/wiki/Wiki.jsp?page=JBoss42FAQ

            • Actions
          • 2. Re: AS 4.2.1 - http://example.com:8080/ gives
            konstandinos
            konstandinos Sep 21, 2007 3:39 AM (in response to konstandinos)

            firstly thanks for the speedy reply. i changed my startup script and it now works. it _is_ a development environment so no too concerned with security yet. having said that could you please clarify the following (quoted from the FAQ page you gave me):

            before 4.2.0.GA jboss always bound to the any address "0.0.0.0". You wouldn't believe how many people would put unprotected instances of JBoss on the internet, or even on their own local LAN. Now you have to explicitly choose to do that, so it takes some thinking about before you revert to the old default behaviour with the "-b' option of jboss.


            am i to understand the following sequence of events is best practise?

            1 - secure jboss (secure jmx-console, web-app console, remove invokers etc)
            2 - add "-b 0.0.0.0" to your startup script so that jboss actually works

            i guess im kinda confused because it says that using the -b option is the old way of doing it, and that i must still use -b, except i have to explicitly set it.

            thanks again for the fast help

              • Actions
            • 3. Re: AS 4.2.1 - http://example.com:8080/ gives
              dimitris
              dimitris Sep 21, 2007 5:49 AM (in response to konstandinos)

              For (2) you could bind to a specific NIC instead of all (0.0.0.)

                • Actions
              • 4. Re: AS 4.2.1 - http://example.com:8080/ gives
                jaikiran
                jaikiran Sep 21, 2007 5:52 AM (in response to konstandinos)

                 

                "konstandinos" wrote:


                am i to understand the following sequence of events is best practise?

                1 - secure jboss (secure jmx-console, web-app console, remove invokers etc)
                2 - add "-b 0.0.0.0" to your startup script so that jboss actually works

                i guess im kinda confused because it says that using the -b option is the old way of doing it, and that i must still use -b, except i have to explicitly set it.

                thanks again for the fast help


                Securing JBoss is the right thing to do. Once you have done that, instead of binding to 0.0.0.0, you can bind to specific IP.


                  • Actions
                • 5. Re: AS 4.2.1 - http://example.com:8080/ gives
                  jaikiran
                  jaikiran Sep 21, 2007 6:01 AM (in response to konstandinos)

                  Dimitris beat me to it :)

                    • Actions