Google Cloud Platform: External IP Address isn't Accessible from Outside
up vote
0
down vote
favorite
I have recently started working with "Google Cloud Platform". I basically want to use it for my data science project. I have successfully setup Project, VM Instance, Firewall Rules etc.
I have installed Jupyter Notebook which is running on port 8888 and I have installed Apache tomcat server. Now, I want to access these via static external IP address of my VM but these aren't accessible when I mention static external IP address.
I have verified external path,, project HTTP(s) traffic enabled, firewall rules for Apache tomcat and Jupyter Notebook added and Ping to that external IP address is also working. In the image below, all the firewall rules for jupyter notebook and tomcat can be seen:
I tried to access by the following ways:
- https://static-external-ip/
- https://static-external-ip:8080/
- https://static-external-ip:888/
Any help in this regard will be a great favor. Happy Learning!
Update: November 10th, 2018
I can access the servers using the following URLs:
https://8080-dot-4783318-dot-devshell.appspot.com/ (Apache Tomcat)
https://8888-dot-4783318-dot-devshell.appspot.com/ (Jupyter Notebook)
First these aren't accessible publicly (externally) and secondly issue while accessing the servers with static external IPs is still there.
tomcat
google-cloud-platform jupyter-notebook 
google-compute-engine vpc asked Nov 9 at 21:29
Bilal Ahmed Yaseen
5231422
add a comment |
up vote
0
down vote
favorite
I have recently started working with "Google Cloud Platform". I basically want to use it for my data science project. I have successfully setup Project, VM Instance, Firewall Rules etc.
I have installed Jupyter Notebook which is running on port 8888 and I have installed Apache tomcat server. Now, I want to access these via static external IP address of my VM but these aren't accessible when I mention static external IP address.
I have verified external path,, project HTTP(s) traffic enabled, firewall rules for Apache tomcat and Jupyter Notebook added and Ping to that external IP address is also working. In the image below, all the firewall rules for jupyter notebook and tomcat can be seen:
I tried to access by the following ways:
- https://static-external-ip/
- https://static-external-ip:8080/
- https://static-external-ip:888/
Any help in this regard will be a great favor. Happy Learning!
Update: November 10th, 2018
I can access the servers using the following URLs:
https://8080-dot-4783318-dot-devshell.appspot.com/ (Apache Tomcat)
https://8888-dot-4783318-dot-devshell.appspot.com/ (Jupyter Notebook)
First these aren't accessible publicly (externally) and secondly issue while accessing the servers with static external IPs is still there.
tomcat
google-cloud-platform jupyter-notebook google-compute-engine vpc asked Nov 9 at 21:29
Bilal Ahmed Yaseen
5231422
Did you open port 8888 in your firewall rules explicitly? HTTP(s) and Tomcat / Jupyter are all HTTP servers and so probably all run on port 80 (or 443 for HTTP(s)) by default, so using custom port 8888 is probably your problem. You could either open up that port and access it athttp://static-external-ip:8888, or you could restart the notebook on port 80 and then access it athttp://static-external-ip.
– Dan
Nov 9 at 23:36
@Dan thanks for your reply. Yes, as I mentioned in my question, I have already configured firewall rules and I have added picture as well in the actual question for you reference. And major issue is that tomcat server is also not accessible which is already running on the default port.
– Bilal Ahmed Yaseen
Nov 10 at 7:26
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I have recently started working with "Google Cloud Platform". I basically want to use it for my data science project. I have successfully setup Project, VM Instance, Firewall Rules etc.
I have installed Jupyter Notebook which is running on port 8888 and I have installed Apache tomcat server. Now, I want to access these via static external IP address of my VM but these aren't accessible when I mention static external IP address.
I have verified external path,, project HTTP(s) traffic enabled, firewall rules for Apache tomcat and Jupyter Notebook added and Ping to that external IP address is also working. In the image below, all the firewall rules for jupyter notebook and tomcat can be seen:
I tried to access by the following ways:
- https://static-external-ip/
- https://static-external-ip:8080/
- https://static-external-ip:888/
Any help in this regard will be a great favor. Happy Learning!
Update: November 10th, 2018
I can access the servers using the following URLs:
https://8080-dot-4783318-dot-devshell.appspot.com/ (Apache Tomcat)
https://8888-dot-4783318-dot-devshell.appspot.com/ (Jupyter Notebook)
First these aren't accessible publicly (externally) and secondly issue while accessing the servers with static external IPs is still there.
tomcat
google-cloud-platform jupyter-notebook google-compute-engine vpc asked Nov 9 at 21:29
Bilal Ahmed Yaseen
5231422
I have recently started working with "Google Cloud Platform". I basically want to use it for my data science project. I have successfully setup Project, VM Instance, Firewall Rules etc.
I have installed Jupyter Notebook which is running on port 8888 and I have installed Apache tomcat server. Now, I want to access these via static external IP address of my VM but these aren't accessible when I mention static external IP address.
I have verified external path,, project HTTP(s) traffic enabled, firewall rules for Apache tomcat and Jupyter Notebook added and Ping to that external IP address is also working. In the image below, all the firewall rules for jupyter notebook and tomcat can be seen:
I tried to access by the following ways:
- https://static-external-ip/
- https://static-external-ip:8080/
- https://static-external-ip:888/
Any help in this regard will be a great favor. Happy Learning!
Update: November 10th, 2018
I can access the servers using the following URLs:
https://8080-dot-4783318-dot-devshell.appspot.com/ (Apache Tomcat)
https://8888-dot-4783318-dot-devshell.appspot.com/ (Jupyter Notebook)
First these aren't accessible publicly (externally) and secondly issue while accessing the servers with static external IPs is still there.
tomcat
google-cloud-platform jupyter-notebook google-compute-engine vpc tomcat
google-cloud-platform jupyter-notebook google-compute-engine vpc asked Nov 9 at 21:29
Bilal Ahmed Yaseen
5231422
asked Nov 9 at 21:29
Bilal Ahmed Yaseen
5231422
edited Nov 10 at 9:32
asked Nov 9 at 21:29
Bilal Ahmed Yaseen
5231422
asked Nov 9 at 21:29
Bilal Ahmed Yaseen
5231422
asked Nov 9 at 21:29
Bilal Ahmed Yaseen
5231422
5231422
Did you open port 8888 in your firewall rules explicitly? HTTP(s) and Tomcat / Jupyter are all HTTP servers and so probably all run on port 80 (or 443 for HTTP(s)) by default, so using custom port 8888 is probably your problem. You could either open up that port and access it athttp://static-external-ip:8888, or you could restart the notebook on port 80 and then access it athttp://static-external-ip.
– Dan
Nov 9 at 23:36
@Dan thanks for your reply. Yes, as I mentioned in my question, I have already configured firewall rules and I have added picture as well in the actual question for you reference. And major issue is that tomcat server is also not accessible which is already running on the default port.
– Bilal Ahmed Yaseen
Nov 10 at 7:26
add a comment |
Did you open port 8888 in your firewall rules explicitly? HTTP(s) and Tomcat / Jupyter are all HTTP servers and so probably all run on port 80 (or 443 for HTTP(s)) by default, so using custom port 8888 is probably your problem. You could either open up that port and access it athttp://static-external-ip:8888, or you could restart the notebook on port 80 and then access it athttp://static-external-ip.
– Dan
Nov 9 at 23:36
@Dan thanks for your reply. Yes, as I mentioned in my question, I have already configured firewall rules and I have added picture as well in the actual question for you reference. And major issue is that tomcat server is also not accessible which is already running on the default port.
– Bilal Ahmed Yaseen
Nov 10 at 7:26
Did you open port 8888 in your firewall rules explicitly? HTTP(s) and Tomcat / Jupyter are all HTTP servers and so probably all run on port 80 (or 443 for HTTP(s)) by default, so using custom port 8888 is probably your problem. You could either open up that port and access it at
http://static-external-ip:8888, or you could restart the notebook on port 80 and then access it at http://static-external-ip.– Dan
Nov 9 at 23:36
Did you open port 8888 in your firewall rules explicitly? HTTP(s) and Tomcat / Jupyter are all HTTP servers and so probably all run on port 80 (or 443 for HTTP(s)) by default, so using custom port 8888 is probably your problem. You could either open up that port and access it at
http://static-external-ip:8888, or you could restart the notebook on port 80 and then access it at http://static-external-ip.– Dan
Nov 9 at 23:36
@Dan thanks for your reply. Yes, as I mentioned in my question, I have already configured firewall rules and I have added picture as well in the actual question for you reference. And major issue is that tomcat server is also not accessible which is already running on the default port.
– Bilal Ahmed Yaseen
Nov 10 at 7:26
@Dan thanks for your reply. Yes, as I mentioned in my question, I have already configured firewall rules and I have added picture as well in the actual question for you reference. And major issue is that tomcat server is also not accessible which is already running on the default port.
– Bilal Ahmed Yaseen
Nov 10 at 7:26
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
You seem to have done all steps for exposing a service to the outside, except I am guessing for one thing - Is Jupyter listening on loopback interface? Per Jupyter's documentation -
By default, a notebook server runs locally at 127.0.0.1:8888 and is accessible only from localhost. You may access the notebook server from the browser using http://127.0.0.1:8888.
The documentation provides information on how to make it accessible to the outside world. In short, to access the service has to bind to on all interfaces (ips).
answered Nov 10 at 13:51
Daniel t.
588612
Thanks @Daniel-t for your response. But I already added these option while configuring it. I added these two lines regarding this: 1) Notebook.ip = "/*" and 2) notebook.allow_origin = "/*". P.S: added slash intentionally as alone esterik symbol was being disappeared.
– Bilal Ahmed Yaseen
Nov 10 at 14:01
So, I don't think that issue is with these configurations as I mentioned in my question as well that I tried same with simple Apache tomcat server as well and observed the same error. So, not being able to understand that what got missed :) I'm really screwing my head on this...
– Bilal Ahmed Yaseen
Nov 10 at 14:02
Can you post the output of this command -netstat -tan |grep 8888?
– Daniel t.
Nov 10 at 14:17
I don't get any output after running this command. Neither error nor any response.
– Bilal Ahmed Yaseen
Nov 10 at 14:19
1
After reading the chat session it appears that you were running your installation in Cloud Shell. As such your connection test to the VM were not successful. I would recommend posting this type of questions in ServerFault as StackOverflow is for Q&A for professional and enthusiast programmers.
– Mohibul Mahmud
Nov 16 at 1:34
|
show 5 more comments
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
You seem to have done all steps for exposing a service to the outside, except I am guessing for one thing - Is Jupyter listening on loopback interface? Per Jupyter's documentation -
By default, a notebook server runs locally at 127.0.0.1:8888 and is accessible only from localhost. You may access the notebook server from the browser using http://127.0.0.1:8888.
The documentation provides information on how to make it accessible to the outside world. In short, to access the service has to bind to on all interfaces (ips).
answered Nov 10 at 13:51
Daniel t.
588612
Thanks @Daniel-t for your response. But I already added these option while configuring it. I added these two lines regarding this: 1) Notebook.ip = "/*" and 2) notebook.allow_origin = "/*". P.S: added slash intentionally as alone esterik symbol was being disappeared.
– Bilal Ahmed Yaseen
Nov 10 at 14:01
So, I don't think that issue is with these configurations as I mentioned in my question as well that I tried same with simple Apache tomcat server as well and observed the same error. So, not being able to understand that what got missed :) I'm really screwing my head on this...
– Bilal Ahmed Yaseen
Nov 10 at 14:02
Can you post the output of this command -netstat -tan |grep 8888?
– Daniel t.
Nov 10 at 14:17
I don't get any output after running this command. Neither error nor any response.
– Bilal Ahmed Yaseen
Nov 10 at 14:19
1
After reading the chat session it appears that you were running your installation in Cloud Shell. As such your connection test to the VM were not successful. I would recommend posting this type of questions in ServerFault as StackOverflow is for Q&A for professional and enthusiast programmers.
– Mohibul Mahmud
Nov 16 at 1:34
|
show 5 more comments
up vote
0
down vote
You seem to have done all steps for exposing a service to the outside, except I am guessing for one thing - Is Jupyter listening on loopback interface? Per Jupyter's documentation -
By default, a notebook server runs locally at 127.0.0.1:8888 and is accessible only from localhost. You may access the notebook server from the browser using http://127.0.0.1:8888.
The documentation provides information on how to make it accessible to the outside world. In short, to access the service has to bind to on all interfaces (ips).
answered Nov 10 at 13:51
Daniel t.
588612
Thanks @Daniel-t for your response. But I already added these option while configuring it. I added these two lines regarding this: 1) Notebook.ip = "/*" and 2) notebook.allow_origin = "/*". P.S: added slash intentionally as alone esterik symbol was being disappeared.
– Bilal Ahmed Yaseen
Nov 10 at 14:01
So, I don't think that issue is with these configurations as I mentioned in my question as well that I tried same with simple Apache tomcat server as well and observed the same error. So, not being able to understand that what got missed :) I'm really screwing my head on this...
– Bilal Ahmed Yaseen
Nov 10 at 14:02
Can you post the output of this command -netstat -tan |grep 8888?
– Daniel t.
Nov 10 at 14:17
I don't get any output after running this command. Neither error nor any response.
– Bilal Ahmed Yaseen
Nov 10 at 14:19
1
After reading the chat session it appears that you were running your installation in Cloud Shell. As such your connection test to the VM were not successful. I would recommend posting this type of questions in ServerFault as StackOverflow is for Q&A for professional and enthusiast programmers.
– Mohibul Mahmud
Nov 16 at 1:34
|
show 5 more comments
up vote
0
down vote
up vote
0
down vote
You seem to have done all steps for exposing a service to the outside, except I am guessing for one thing - Is Jupyter listening on loopback interface? Per Jupyter's documentation -
By default, a notebook server runs locally at 127.0.0.1:8888 and is accessible only from localhost. You may access the notebook server from the browser using http://127.0.0.1:8888.
The documentation provides information on how to make it accessible to the outside world. In short, to access the service has to bind to on all interfaces (ips).
answered Nov 10 at 13:51
Daniel t.
588612
You seem to have done all steps for exposing a service to the outside, except I am guessing for one thing - Is Jupyter listening on loopback interface? Per Jupyter's documentation -
By default, a notebook server runs locally at 127.0.0.1:8888 and is accessible only from localhost. You may access the notebook server from the browser using http://127.0.0.1:8888.
The documentation provides information on how to make it accessible to the outside world. In short, to access the service has to bind to on all interfaces (ips).
answered Nov 10 at 13:51
Daniel t.
588612
answered Nov 10 at 13:51
Daniel t.
588612
answered Nov 10 at 13:51
Daniel t.
588612
answered Nov 10 at 13:51
Daniel t.
588612
588612
Thanks @Daniel-t for your response. But I already added these option while configuring it. I added these two lines regarding this: 1) Notebook.ip = "/*" and 2) notebook.allow_origin = "/*". P.S: added slash intentionally as alone esterik symbol was being disappeared.
– Bilal Ahmed Yaseen
Nov 10 at 14:01
So, I don't think that issue is with these configurations as I mentioned in my question as well that I tried same with simple Apache tomcat server as well and observed the same error. So, not being able to understand that what got missed :) I'm really screwing my head on this...
– Bilal Ahmed Yaseen
Nov 10 at 14:02
Can you post the output of this command -netstat -tan |grep 8888?
– Daniel t.
Nov 10 at 14:17
I don't get any output after running this command. Neither error nor any response.
– Bilal Ahmed Yaseen
Nov 10 at 14:19
1
After reading the chat session it appears that you were running your installation in Cloud Shell. As such your connection test to the VM were not successful. I would recommend posting this type of questions in ServerFault as StackOverflow is for Q&A for professional and enthusiast programmers.
– Mohibul Mahmud
Nov 16 at 1:34
|
show 5 more comments
Thanks @Daniel-t for your response. But I already added these option while configuring it. I added these two lines regarding this: 1) Notebook.ip = "/*" and 2) notebook.allow_origin = "/*". P.S: added slash intentionally as alone esterik symbol was being disappeared.
– Bilal Ahmed Yaseen
Nov 10 at 14:01
So, I don't think that issue is with these configurations as I mentioned in my question as well that I tried same with simple Apache tomcat server as well and observed the same error. So, not being able to understand that what got missed :) I'm really screwing my head on this...
– Bilal Ahmed Yaseen
Nov 10 at 14:02
Can you post the output of this command -netstat -tan |grep 8888?
– Daniel t.
Nov 10 at 14:17
I don't get any output after running this command. Neither error nor any response.
– Bilal Ahmed Yaseen
Nov 10 at 14:19
1
After reading the chat session it appears that you were running your installation in Cloud Shell. As such your connection test to the VM were not successful. I would recommend posting this type of questions in ServerFault as StackOverflow is for Q&A for professional and enthusiast programmers.
– Mohibul Mahmud
Nov 16 at 1:34
Thanks @Daniel-t for your response. But I already added these option while configuring it. I added these two lines regarding this: 1) Notebook.ip = "/*" and 2) notebook.allow_origin = "/*". P.S: added slash intentionally as alone esterik symbol was being disappeared.
– Bilal Ahmed Yaseen
Nov 10 at 14:01
Thanks @Daniel-t for your response. But I already added these option while configuring it. I added these two lines regarding this: 1) Notebook.ip = "/*" and 2) notebook.allow_origin = "/*". P.S: added slash intentionally as alone esterik symbol was being disappeared.
– Bilal Ahmed Yaseen
Nov 10 at 14:01
So, I don't think that issue is with these configurations as I mentioned in my question as well that I tried same with simple Apache tomcat server as well and observed the same error. So, not being able to understand that what got missed :) I'm really screwing my head on this...
– Bilal Ahmed Yaseen
Nov 10 at 14:02
So, I don't think that issue is with these configurations as I mentioned in my question as well that I tried same with simple Apache tomcat server as well and observed the same error. So, not being able to understand that what got missed :) I'm really screwing my head on this...
– Bilal Ahmed Yaseen
Nov 10 at 14:02
Can you post the output of this command -
netstat -tan |grep 8888 ?– Daniel t.
Nov 10 at 14:17
Can you post the output of this command -
netstat -tan |grep 8888 ?– Daniel t.
Nov 10 at 14:17
I don't get any output after running this command. Neither error nor any response.
– Bilal Ahmed Yaseen
Nov 10 at 14:19
I don't get any output after running this command. Neither error nor any response.
– Bilal Ahmed Yaseen
Nov 10 at 14:19
1
1
After reading the chat session it appears that you were running your installation in Cloud Shell. As such your connection test to the VM were not successful. I would recommend posting this type of questions in ServerFault as StackOverflow is for Q&A for professional and enthusiast programmers.
– Mohibul Mahmud
Nov 16 at 1:34
After reading the chat session it appears that you were running your installation in Cloud Shell. As such your connection test to the VM were not successful. I would recommend posting this type of questions in ServerFault as StackOverflow is for Q&A for professional and enthusiast programmers.
– Mohibul Mahmud
Nov 16 at 1:34
|
show 5 more comments
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53233495%2fgoogle-cloud-platform-external-ip-address-isnt-accessible-from-outside%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
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
Did you open port 8888 in your firewall rules explicitly? HTTP(s) and Tomcat / Jupyter are all HTTP servers and so probably all run on port 80 (or 443 for HTTP(s)) by default, so using custom port 8888 is probably your problem. You could either open up that port and access it at
http://static-external-ip:8888, or you could restart the notebook on port 80 and then access it athttp://static-external-ip.– Dan
Nov 9 at 23:36
@Dan thanks for your reply. Yes, as I mentioned in my question, I have already configured firewall rules and I have added picture as well in the actual question for you reference. And major issue is that tomcat server is also not accessible which is already running on the default port.
– Bilal Ahmed Yaseen
Nov 10 at 7:26