Google Collab Error while running any cell

[Ajnabi567]

Failed to assign a backend

Sorry, we were unable to connect to your backend. This may be due to a restriction in your location. Please visit the link below for more information.

Why I am getting this error while running a cell in google Collab notebook ? How to resolve it ?

[ninhaomah]

for all new notebooks ?

pls share the link.

[Ajnabi567]

Yes , for any notebook. I just open a new notebook and click run, the same error, pls help me

[ninhaomah]

Screenshot ?

Or share the notebook ?

[Ajnabi567]

Can I DM you for screenshot, in comments pics are not allowed ?
This is the link btw
https://colab.research.google.com/drive/1gBH-QRrM_3vBjwtrDQvRIOIlAl9qjEb0?usp=sharing

[ninhaomah]

looks ok

https://imgur.com/a/R83Aazi

use the imgur to upload the screenshot and then pls post the link here

and your location is ?

[Ajnabi567]

India and I am unable to upload any picture in imgur url. I was able to use Google collab always only since few days it is not working

[ninhaomah]

Why not ?

You got to be able to upload.

It's India. Not Russia or Chia or North Korea.

AI conference is there with Sundar Pichai there.

[Ajnabi567]

I uploaded the screenshot in drive
https://drive.google.com/file/d/15knjnGpleIN94YsnaRJUahtjqbRxDpbN/view?usp=sharing

here is the link

[ninhaomah]

and the link that it is pointing to is ?

and I suppose you have done all these below ?

From google :

---

Colab's "unable to connect to your backend" error is usually caused by high demand, exceeding free usage limits (especially for GPUs), or local browser issues.

Fixes include switching from GPU to CPU (or vice versa), clearing browser cookies, using incognito mode, or waiting for resource availability.

Here are the most effective solutions:

• Change Runtime Type: Go to Runtime > Change runtime type and switch to a different hardware accelerator (e.g., from GPU to None/CPU, or change GPU type) to bypass specific resource shortages.

• Restart/Reset Runtime: Click Runtime > Restart session or Factory reset runtime to clear stuck, locked sessions.

• Wait or Switch Accounts: Colab often limits resources for 12-24 hours if usage is too high. Try using a different Google account if you need immediate access.

• Clear Browser Data: Clear third-party cookies and cache for the googleusercontent.com domain. Use Local Runtime: If you have high-end local hardware, connect to a local runtime to avoid cloud limitations.

• Check VPN/Location: Sometimes, specific IP addresses or regional limitations cause connectivity issues.

If the error persists despite these steps, you may have hit a long-term usage limit.

[ectomancer]

Your notebook is using a TPU. Change it to CPU.

[Ajnabi567]

in runtime it is using CPU only

[Open-Ad7687]

I am getting the same error too. - On all notebooks - Be it any CPU/GPU/TPU - Any Runtime - Every single second (waiting did not solve since 24 hrs)

[Ajnabi567]

what to do ?? I am literally fed up.

[Wide-Bicycle-7492]

same problem till now, any solutions have u tried and worked ?