0

I cant access jupyter lab on GCP Debian 10 machine (made from Google stock image).

I configured GCP firewall to allow 8888 and 8080 and GCP Connectivity Test shows they are reacheable.

Debian however doesnt seem to have firewalld or uwf installed.

Is it possible Google uses standard images without firewall installed?

Is there a way to check if a port blocked and by what process in Debian?

These are services that are enabled:

$ systemctl list-unit-files --type service -all | grep enabled
apparmor.service                       enabled        
autovt@.service                        enabled        
chrony.service                         enabled        
chronyd.service                        enabled        
containerd.service                     enabled        
cron.service                           enabled        
dbus-org.freedesktop.timesync1.service enabled        
docker.service                         enabled        
gce_instance_monitor.service           enabled        
gcs_sync.service                       enabled        
getty@.service                         enabled        
google-c2d-startup.service             enabled        
google-disk-expand.service             enabled        
google-guest-agent.service             enabled        
google-osconfig-agent.service          enabled        
google-shutdown-scripts.service        enabled        
google-startup-scripts.service         enabled        
haveged.service                        enabled        
jupyter.service                        enabled        
networking.service                     enabled        
nvidia-hibernate.service               enabled        
nvidia-resume.service                  enabled        
nvidia-suspend.service                 enabled        
rc-local.service                       enabled-runtime
rc.local.service                       enabled-runtime
rsync.service                          enabled        
rsyslog.service                        enabled        
ssh-session-cleanup.service            enabled        
ssh.service                            enabled        
sshd.service                           enabled        
syslog.service                         enabled        
systemd-fsck-root.service              enabled-runtime
systemd-timesyncd.service              enabled        
unattended-upgrades.service            enabled 
Boppity Bop
  • 2,663

1 Answers1

0

Apparently when you run Jupyter Lab like this:

jupyter-lab --no-browser

it binds to 127.0.0.1 and somehow not accessible from outside.

Once I changed it to:

jupyter-lab --no-browser --ip=0.0.0.0

it worked. I cannot explain it but it seems GCP somehow separates 127.0.0.1 from external interface.

Boppity Bop
  • 2,663