For Information Freedom — Part 3 (2020)

Notes on maintaining access to Google for learning: a working v2ray+websocket+https setup and quick deployment tips.

Apr 4, 2020 · 1 min read · 149 Words · -Views -Comments · Digital Nomad
🇨🇳 阅读中文版
Read with AI

Choose an AI assistant

ChatGPT Open in a new tab with the article link and prompt
Claude Copy the prompt, then open Claude

Open Claude
Trouble reading the article?

If the prompt is missing, copy the full prompt below into your AI assistant. If the AI cannot read the article, paste the visible passage you want to discuss and add your question.

I recently tried to scale the Great Firewall again for a Udacity promotion. That didn’t work out, but I refined my Google-access setup, which made the effort worth it. Sharing the details for anyone still wondering how to reach Google.

Statement: Accessing Google is strictly for learning and constructive purposes.

A Method That Still Works

v2ray + WebSocket + HTTPS

Quick Deployment Steps

  1. Register a domain name.
  2. Rent a Vultr instance.
    • Billed hourly
    • Supports Alipay
    • Pick CentOS 7
    • I recommend the Japan region for lower latency
  3. Follow my README to deploy.

Once you get the hang of it, the whole process takes about 10 minutes.

Vultr Referral

Final Thoughts

  1. Without Google, it’s harder to learn—especially for engineers.
  2. What works today might break tomorrow (think whitelists and policy shifts). That’s just how it is.
  3. Solving this sharpens your grasp of HTTP, DNS, Docker, Shell, and more. Definitely time well spent.
Authors
Developer, digital product enthusiast, tinkerer, sharer, open source lover