ПЕРЕСТАНЬ бояться БАНОВ Claude Code | Без VPN и блокировок НАВСЕГДА

Summary

The presenter demonstrates how to run Claude Code on a rented VPS and use it through VS Code, so authorization and coding sessions take place on the server rather than on the user’s computer. He presents this as a way to reduce exposure to account blocks, but it is not a guarantee against blocking.

Account and payment advice

• Avoid buying pre-made accounts with subscriptions; the presenter says the payment method and account history may be unclear.
• He recommends paying with a personal virtual card and keeping the IP country consistent with the card’s country, especially when subscribing or renewing.
• For new accounts, he suggests starting with free usage, moving to a lower-tier plan, and waiting before upgrading. He also recommends building account history.
• These are the presenter’s recommendations and anecdotes, not assurances from Anthropic. He says account age may have helped an acquaintance avoid blocks despite frequent IP changes.

VPS setup tutorial

1. Choose a server: The presenter compares Hostinger and Hostkey. He says a VPS with roughly 2 CPU cores and 8 GB RAM is sufficient for Claude Code and projects. He considers very cheap, low-powered servers inadequate for running code directly.
2. Install and secure it: On Ubuntu, run the supplied installer from Windows PowerShell or macOS Terminal. It configures the VPS, creates a non-root user, sets up SSH keys, disables password access, and installs Claude Code and a remote desktop. The presenter says Ubuntu 24.04 and 26.04 are supported and setup can take 10–20 minutes.
3. Authorize Claude Code: Open the server’s desktop in a browser and sign in there, keeping authorization on the VPS.
4. Connect with VS Code: Install the Remote SSH extension, connect to the server, open a project folder, and install the Claude Code extension in the remote VS Code environment. The presenter also demonstrates using Claude Code from the server terminal.
5. Preview web projects: If a development site does not open automatically, forward its port in VS Code—for example, port 5173—and refresh the browser.
6. Keep work running: Use tmux to start a persistent session, detach from it, and later reattach. The presenter demonstrates this with a simple counting task and provides basic session commands in the guide.
7. Reopen authorization if needed: The guide includes a command for opening an SSH tunnel to the server desktop, where the user can relaunch the browser and sign in again.

The presenter’s example uses a server in Kuala Lumpur, Malaysia, despite having said that the card’s country should match the server IP’s country. He notes that his card is from Singapore, says the locations are about 310 km apart, and describes this as his personal experience and a risk—not as the recommended approach.

Additional guide

The video mentions a fuller, paid guide that goes beyond the public tutorial. It covers setting up a shared folder between the local computer and VPS, and allowing Claude Code on the server to run terminal commands on the local device.

Main speakers and sources

• Main source: The channel presenter, demonstrating the setup and sharing personal experience.
• Additional anecdote: The presenter’s editor/cameraman, whose account history is cited as an example.
• Referenced materials and products: The presenter’s PDF guide and installer source repository; Hostinger and Hostkey VPS services; Pay by World virtual-card service; VS Code Remote SSH, Claude Code, and tmux.