Unable to open Tensorboard in browser

Question

I am following google cloud machine learning tutorial and I am unable to Launch TensorBoard

I\'ve followed the steps in the above tutorial (also set up my environme

Answer 1

It looks like the port 8080 is not open on your machine.
You can check it with this command line tool: netstat -a.

To open a specific port on google cloud platform, see this answer from SO.

Answer 2

Had the same problem this morning. Solved it with

tensorboard --logdir=data/ --host localhost --port 8088

Navigated the browser to http://localhost:8088

Answer 3

If you are using Google Cloud Shell you have to click on icon placed in upper left of shell window.

Answer 4

I don't know if that's the case, but tensorboard has some visualization problems in several browsers. Try to connect to http://172.17.0.2:8080 with a different browser (for example, on my macbook, safari doesn't work very well with tensorboard and I use google Chrome).

Answer 5

There are 2 solutions(as far as i could check) to solve this problem:

1. Instead of using the http://name:port_number, use http://localhost:port_number. This is if you are using Chrome browser.

2. If you are using firefox(recommended as it's really convenient), then you can open the link(which has your PC name) directly, which is displayed after executing the "tensorboard --logdir=logs/" command in cmd, i.e; http://name:port_number will work here.

(name here refers to the PC or user name)

Answer 6

I faced the same problem when used Tensorboard inside a Docker container. The successful steps in my case were:

1. First of all, make sure the port you use for Tensorboard is opened to the outside world. To make this possible run your Docker container with an option -p <host_machine_port>:<tensorboard_port_inside_container>. For example:

docker run --name my_tensorboard_container -p 7777:8080 my_tensorboard_image bash

2. Then if you still cannot access the Tensorboard try to add --bind_all option like so:

tensorboard --bind_all --port 8080 --logdir ./logs

Hope, it works in your case as well.