Google Colab Workarounds

Introduction

Google Colaboratory is one of the most known Free Cloud Services using Jupyter Notebooks, but it has some limitations that can be worked around.
Here are some Google Colaboratory Tips & Bypasses. This guide has been written mostly for Chrome, for some parts you might need to search the counter version for your browser.

Runtime disconnected due to inactivity

Happens when you remain AFK (Away From Keyboard, in most cases it’s for leaving the colab to Train or using a Web UI) for a long time.
There are 2 types of Warnings:

Captcha Verification


Some people might get Captchas, like in the image above, to check if they are AFK, especially for new Google accounts, in that case, the Idle Time Out Bypass won’t work, you will need to use either:

Idle Time Out


To prevent this to happen, you need to:

  1. Run the Colab code cells.
  2. When you want to go AFK, in Google Colaboratory open the Console Tab of the DevTools choosing one of the 2 ways specified for each platform:
  • Windows & Linux:
    • Ctrl + Shift + J
    • Click the 3 dots on the up right, Other Tools > Tools For Developers.
  • Mac:
    • Cmd + Option + J
    • Click the 3 dots on the up right, Other Tools > Tools For Developers.
  • Mobile:
    • Download Any Mobile Browser with Dev Tools like Brave, and search how to get the Dev Tools / How to Inspect Element.
    • Bookmark any site, by clicking the 3 dots on the up right and then the Star Symbol, a popup will appear that the site has been saved successfully, you need to click Edit on it, and change the name to DevTools, or anything you want, and then paste the following code in the URL field:
1
2
3
4
5
6
7
8
javascript:(function () { 
    var script =  document.createElement('script');
    script.src="//cdn.jsdelivr.net/npm/eruda"; 
    document.body.appendChild(script);
    script.onload = function () { 
        eruda.init() 
    } 
})();

Then go back on the Google Colab page, in the search bar write the name of your edited bookmark, click it, and a Gear Icon will appear on the screen, click it.

  1. ‎Go to the Console tab in the Inspect Element and paste the following:
1
2
3
4
5
function ClickConnect(){
console.log("Working");
document.querySelector("colab-toolbar-button#connect").click()
}
setInterval(ClickConnect,60000)
  1. It'll look something like this at the end:

Cannot connect to GPU backend


This happens when you run out of the Colab’s compute units (GPU).
The daily free gpu is ~4 hours usually, remember this varies from user to user and also on how much you use the service.

Solutions

  • Wait 12 - 24 hours for the daily GPU limit to reset.
  • Make/Use another Google Account.
  • Buy a Google Colab Subscription for more compute units (more & faster GPU).
  • Be careful to use a GPU Runtime only when it’s necessary, else for colabs that can work even on CPU correctly, it’s better you use that so you save up your daily gpu.
  • You can connect without a GPU, using a CPU instead, but remember it will be slower and for some Colabs a GPU is necessary.

Disallowed Code

It triggers when the Colab runs code that's restricted for free tier users. See them all in their FAQ.

There are 2 ways this warning appears:

Start Running


This appears at the start of when you run the code cell, it means the code contains keywords that are blacklisted from Google Colab for Free Tier Users.
Encryption is suggested to bypass this.

Middle Running


This happens while running the code cell, usually when using WEB UIs, this might happen while running notebooks that used an encryption method to not get detected at the start. It’s not 100% guaranteed that this warning shows though, for some users it could, for some not, could also depend on how much time they are running the colab. Also it has been found that if you run a file named like one of the banned words, even if the code of the file has nothing related to the program, it still gets detected this way, which a bypass could be renaming it using os.rename.
A full refactor of everything is suggested to bypass this.

Banned things/words on Google Colab:

There are some specific words that give a Start Running Disallowed Code Warn.
You can find those in https://ssl.gstatic.com/colaboratory-static/common/4b84b91f170e14cc9a912570b12fbf56/external_binary.js, or by just opening the Source Tab in Dev Tools and using Ctrl+Shift+F to search everywhere a known banned word like "facefusion"

  • RVC, specifically the word ‘Retrieval-based-Voice-Conversion-WebUI’
  • DeepFaceLab, specifically the word ‘DeepFaceLab/’
  • FaceFusion, specifically the word ‘facefusion’
  • /anticaptcha/
  • /nopecha
  • chrome-remote-desktop
  • Chrome Remote Desktop
  • https://remotedesktop.google.com
  • Start RDP
  • RDP Windows
  • apt install xrdp
  • apt-get install xrdp
  • /opt/TurboVNC/
  • VNC password
  • /turbovnc/releases/download
  • import remocolab
  • remocolab.setupVNC
  • Free VPS
  • https://code-server.dev/install.sh
  • pip install colabcode
  • pip install gpu-tpu-lab-server
  • colabtunnel
  • https://github.com/tmate-io
  • tmate-2.4.0-static-linux
  • pip install colab_ssh
  • linus-colab-ssh
  • linus_colab_ssh
  • setupSSHDMain
  • /usr/sbin/sshd
  • openssh-server
  • SSH Dropbear
  • DROPBEAR_PORT=
  • /DFL-Colab
  • github.com/deepfakes
  • /faceswap/
  • faceswap-generator
  • /roop-unleashed
  • based9based/roop
  • pip install hashcat
  • /hashcat
  • qbittorrent-nox
  • QBittorrent
  • transmission-cli
  • rTorrent
  • cloud-torrent
  • PygmalionAI
  • Shygmalion
  • Pygway
  • https://app.zoom.us/wc/
  • https://zoom.us/wc/
  • /EasyGUI
  • /EasierGUI
  • huggingface.co/nolanaatama/colab/resolve/main/microsoftexcel
  • nolanaatama/microsoftexcel
  • microsoftexcel-tunnels
  • a1111-microsoftexcel
  • guebui = base64.b64decode
  • guebui2 = base64.b64decode
  • Rejekts/project/resolve/main/project-main.zip
  • VoiceConversionWebUI
  • VoiceConversion{reeee}UI
  • Voice-Conversion-WebUI
  • github.com/777gt/EVC
  • Applio-RVC-Fork
  • MMVCServerSIO.py

Solutions

If your Colab disconnects shortly after starting, Google's system is likely flagging specific file or directory names (e.g., rvc, webui) within the repository. You can bypass this by "refactoring" your project to mask these keywords from Google's static analysis.

How to execute:

  1. Use an AI for Global Replacement: Manually refactoring is slow. Use an AI (like Gemini or ChatGPT) to perform a global search-and-replace across the entire repository.
  2. The Prompt: Upload your repository files to an AI and use the following prompt:

    "I need all variables, code, and filenames to NOT include the term '[TERM]'. You must remove or rename EVERYTHING containing this word within all files in the repository. Replace '[TERM]' with '[NEW_TERM]'. Analyze the entire repository, plan, and implement the changes."
    (Run this once for "rvc" to "voice", and repeat for "webui" to "interface")

  3. Important Warning: While renaming backend code is effective, be cautious with UI elements. As noted by the community, renaming generic UI tags (like "UVR5") is usually fine, but renaming specific tool-identifiers (like "CoverMaker") may cause the application to break. Always test your project after refactoring.
  4. Reference: You can view a successful example of this exact refactoring process here: GitHub Commit - Project Refactor

Basic Troubleshooting

  • Encryption: Use advanced encryption methods or obfuscation scripts to hide your code cells from initial scanning.
  • Refresh/Retry: Close and refresh the page, then retry running the Colab. Sometimes detection is triggered by temporary server-side load; a fresh start can sometimes bypass the warning.
  • Account Rotation: If one account consistently flags your project, try a different Google account. Detection sensitivity varies by account history.
Edit

Pub: 08 Mar 2026 16:11 UTC

Edit: 02 May 2026 19:04 UTC

Views: 394