-
Notifications
You must be signed in to change notification settings - Fork 444
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error 403 on pulling image #57
Comments
Hello i have been facing the same problem : |
The same problem here. There's any solution? |
Hello, same problem here. Is there any workaround? |
Having the same issue. I exported a full copy of an existing image on my another machine as a workaround. It did work well but of course it is not sustainable. I suspected I had a banned IP but I noticed the image URL was unreachable when tried over web browser. It redirected me an unknown page. That is a side note about my issue. It is likely that the problem is based on IPs. I successfully pulled the required images on a DigitalOcean machine. I think some countries are restricted to perform this action. |
I am getting the same error with a different message as next: Failed to pull image "docker.whatsapp.biz/web:v2.35.2": rpc error: code = Unknown desc = failed to pull and unpack image "docker.whatsapp.biz/web:v2.35.2": failed to copy: httpReaderSeeker: failed open: unexpected status code https://docker.whatsapp.biz/v2/web/blobs/sha256:fb6b73cdf53fd33f267f453876cd8e9daf2ce96a89630833a7c29ba7a1b2a797: 403 Forbidden Any idea why I am getting that? |
Same issue. |
Guys I solved this problem by upgrading my docker version! |
It doesn't. I'm on 20.10.7 too and getting the same error. |
I installed the whole thing about 15days ago and everything worked (both coreapp and webapp images got pulled). Now I am trying to setup Instance Monitoring and getting the Forbidden error.
Tried to pull the webapp image and now it gives the same error as well. My docker version is 20.10.7 |
It does not work because BinTray only allows paid users until July 4th. All other users get a |
i dont get 403 error but i cant pull image too Pulling wacore (docker.whatsapp.biz/coreapp:v2.35.4)... |
Yesterday was the last day that BinTray could be used. WhatsApp should now move the image to another system so that we could download it again. |
I asked someone if he could forward this issue to a Facebook/WhatsApp guy he knows. Hopefully I get a response soon. |
Does nobody read or something? 🤨 |
This issue is happening with every version: the registry docker.whatsapp.biz is no longer accesible. |
It seems to be waiting until a new repository is available for download. My first setup hahaha very unlucky. |
Has anyone opened a ticket on Facebook support? If not, I'll open it in one of our Wabas... |
Had the same Issue. Checked with WhatsApp and was told that this is an intermittent issue. Resolved after a while without doing anything. |
Hello everyone, Sorry again for the inconvenience caused, feedback to improve our support process is welcome. :) |
Duplicate of #38 - merging this thread with a previous one, closing this one. |
it's similar with #23 when running docker-compose from indonesia
docker-compose up -d
Pulling wacore (docker.whatsapp.biz/coreapp:v2.33.3)...
v2.33.3: Pulling from coreapp
83ee3a23efb7: Pulling fs layer
db98fc6f11f0: Pulling fs layer
f611acd52c6c: Pulling fs layer
f85e9fda1e76: Waiting
8031e26de4a5: Waiting
d75c233db377: Waiting
eb6a89aa8799: Waiting
dea8a3ecac8b: Waiting
ea976d199fd6: Waiting
ERROR: error pulling image configuration: error parsing HTTP 403 response body: invalid character 'F' looking for beginning of value: "Forbidden!"
I'm using ubuntu 16.04 i've tried using 2 different block IP from my provider but seems both was blocked.
The text was updated successfully, but these errors were encountered: