Home Forums Hortonworks Sandbox Cannot open Sandbox or Tutorial port

This topic contains 6 replies, has 4 voices, and was last updated by  Richard Clapp 8 months, 2 weeks ago.

  • Creator
    Topic
  • #19974

    The Sandbox introduction page at http://192.168.92.128 is displayed okay. However, when I press the Start button under Use the Sandbox, I get the following error:

    http://192.168.92.128:8000 is unavailable

    In Google Chrome the error message is:
    Error 138 (net::ERR_NETWORK_ACCESS_DENIED): Unable to access the network

    I get the same error when I press the Start button under tutorials which goes to the following address:

    http://192.168.92.128:8888/tutorials

    In FireFox the error displayed is:
    Firefox can’t establish a connection to the server at 192.168.92.128:8888

    I can ping the ip address 192.168.92.128

    Thank you for any help.

Viewing 6 replies - 1 through 6 (of 6 total)

You must be logged in to reply to this topic.

  • Author
    Replies
  • #49583

    Richard Clapp
    Participant

    In my case, the AMBARI site works fine, but the tutorial is flawed. Left side loads, right side (10.203.50.60:8000) does not. wget fails with unable to connect. Standard unaltered sandbox install on hyper-v. Any ideas where to start? I already grepped hue and it is active.

    Collapse
    #23040

    Resolved. Thanks Robert. read some of the earlier postings. I was using the incorrect IP. got the correct one from output of ifconfig.

    Collapse
    #23033

    Robert
    Participant

    Hi Ramana,
    You may want to start a new thread since you may have a different issue. Please provide the virtual application you are using. Can you check your network adapters and verify what their settings are?

    Regards,
    Robert

    Collapse
    #23012

    I cannot ping nor open in a browser. But it installed ok. I get the ip.

    Collapse
    #20456

    Robert
    Participant

    Hi Martin,
    What virtual machine are you using? If you have telnet, you can try telnetting to the port 8000 to verify the service is listening or you can log into the terminal and execute
    wget http://192.168.56.128:8000/beeswax/

    To verify the machine can fetch the webpage from itself. This should help isolate if the issue is the sandbox server versus your client browser.

    Regards,
    Robert

    Collapse
    #20005

    Sorry about this second empty message. I wanted to check the Notify me of follow-up replies via email

    Collapse
Viewing 6 replies - 1 through 6 (of 6 total)