minicube/kubernetes and other google cloud storage 403 issues

Google Cloud Cloud Foundations & Onboarding
1

Whenever I try to download some file hosted on a google cloud storage I receive 403.

Following a guide on many start up guide like minicube and more that use google cloud storage to distribute binary releases.

I tested from Digital Ocean, Linode and my local lab workstations I can download/access those files/registries.

But, from another server I have it blocks everytime. I got two instances running there, and the second instance haven’t even signed to any Google service to say it’s blocked or something. But I am very careful not to abuse any service. The firewall is off on that new machine, the dns settings are correct.

I can ping/dig/traceroute any google api services and it’s working fine. I can fetch google.com for a test and receive 200, but once I try google api service it blocks me with 403, just from that servers I have.

To reproduce:

curl -LO https://storage.googleapis.com/minikube/releases/latest/minikube-linux-amd64

Response:

<?xml version='1.0' encoding='UTF-8'?><Error><Code>AccessDenied</Code><Message>Access denied.</Message><Details>We're sorry, but this service is not available in your location</Details></Error>

Doing

minicube start

I get:

❗  The image 'gcr.io/google_containers/etcd:3.5.9-0' was not found; unable to add it to cache. 
❗  The image 'gcr.io/google_containers/k8s-minikube/storage-provisioner:v5' was not found; unable to add it to cache. 
❗  The image 'gcr.io/google_containers/coredns/coredns:v1.10.1' was not found; unable to add it to cache. 
❗  The image 'gcr.io/google_containers/kube-controller-manager:v1.28.3' was not found; unable to add it to cache. 
❗  Updating the running docker "minikube" container ... 
❗  The image 'gcr.io/google_containers/pause:3.9' was not found; unable to add it to cache. 
❗  The image 'gcr.io/google_containers/kube-apiserver:v1.28.3' was not found; unable to add it to cache. 
❗  The image 'gcr.io/google_containers/kube-proxy:v1.28.3' was not found; unable to add it to cache. 
❗  The image 'gcr.io/google_containers/kube-scheduler:v1.28.3' was not found; unable to add it to cache.

Meaning even the registry access is blocked.

2

Hi @damjand ,

Welcome to the Google CLoud Community!

The issue seems to arise from Google Cloud’s geolocation system occasionally misclassifying traffic from certain IPv6 prefixes as originating from regions where access to many *.googleapis.com services is typically restricted.

Where is your server located? If your server is not located in these locations - Countries or regions where Google Workspace is available, you can report that this is a mistake here: https://support.google.com/websearch/contact/ip

Note that there is no definite time when it will get fixed, you may also contact Google Cloud Support to further look into your case. Thanks.

3

I am not their direct customer for this issue, I am simply trying to access a public storage bucket for minikube or other storage urls accessed from their respective IPV6 URL’s, in that case how to do I get support from Google that some of my servers is not able to access a content?

Is it ok to use the ..websearch/contact thingy or?

P.S this forum is not good, it took me 10 attempts to make a reply. All failed.