Antigravity Complete Guide: Clean Node Setup and Google Login Configuration

Objective: Prepare a “clean” network exit node (IP/environment as unmarked by risk control as possible) and complete Antigravity’s Google login using a “clean” Google account. Includes verification methods and common troubleshooting at the end.

Note: Any operations involving accounts and network environments should comply with local laws and platform terms; do not use for bypassing compliance restrictions or conducting illegal automation.

1. What is a “Clean Node” and “Cleanliness” Verification

1.1 Common Dimensions for “Clean Node” Determination

What people commonly call “clean” mostly refers to the risk control profile of exit IP + runtime environment being “cleaner”:

• IP Dimensions

  • Whether identified as data center/machine room IP (DC IP)
  • Whether marked by various anti-cheat/blacklist systems (Spam/Fraud/Bot/Proxy/VPN)
  • Whether there’s a history of abuse (email spam, crawling, credential stuffing, etc.)

• Environment Dimensions

  • Whether browser fingerprint is abnormal (timezone, language, fonts, WebGL, Canvas combinations inconsistent)
  • Whether Cookie/LocalStorage/extensions are contaminated (old account remnants, script injection)
  • Frequent switching of countries/ASN/proxies in the same environment (high-risk characteristic)

1.2 Quick IP Cleanliness Testing (Tool You Provided)

Use: https://www.ping0.cc

Focus on this information during testing:

• IP type (residential/data center/proxy determination)
• Risk score/blacklist hits
• Geographic location and ASN (carrier) match expectations

Practical suggestion: Test more than once; test once after “just connecting to VPN, after clearing browser, before login” to ensure link stability and consistency.

2. Server Registration (Node Source)

Your provided registration link:

• https://www.voyracloud.com/?ref_code=HALC9FNM

Recommended basic requirements:

• Prioritize data centers near your target region (reduce latency, reduce frequent cross-region)
• New instances should be “new environment” (clean system, don’t reuse old images)
• Only open necessary ports (reduce risk of scanning/abuse)

3. VPN Setup (Server Side)

Your provided one-click script:

wget https://get.vpnsetup.net -O vpn.sh && sudo sh vpn.sh

3.1 Security and Controllability Recommendations (Strongly Recommended)

One-click scripts are convenient, but they mean you’re handing system changes to external scripts. It’s recommended to at least:

1. Download first, then audit

wget https://get.vpnsetup.net -O vpn.sh
less vpn.sh

2. Confirm what the script will install (common: IPsec/L2TP, WireGuard, OpenVPN, etc.), whether it will change firewall rules, whether it writes plaintext credentials.

3. Record after running:

• VPN protocol and ports
• Connection accounts/keys (save to secure password manager)
• Server firewall policies (only allow needed ports)

3.2 Self-check After Setup Completion

• Confirm service running status on server (different commands for different protocols)
• After connecting locally to VPN:
  1. Open ping0 to detect IP cleanliness
  2. Then visit any IP information site to confirm exit has switched (e.g., public IP shown in browser matches server)

4. Local Usage: Making the “Environment” as Clean as Possible

4.1 Browser Recommendations (Low-cost Approach)

• Use a brand new browser profile (Chrome/Edge both work)
• Don’t install extensions (especially ad injection, script types)
• Clear cache and site data (or just new profile)
• Keep these parameters as consistent as possible:
  • System timezone ≈ VPN exit region
  • Browser language ≈ common language in exit region (at least don’t conflict completely)
  • Don’t frequently jump between Japan and America

4.2 Node “Cleanliness” Verification Process (Recommended Order)

1. Connect to VPN
2. Open https://www.ping0.cc and test once
3. Close and reopen browser (or new profile)
4. Test again
5. Confirm stability before proceeding with Google registration/login

5. Need a “Clean Google Account”

“Clean account” usually means: newly registered, few associations, few abnormal behaviors.

5.1 Registration Recommendations (Reduce Triggering Risk Control)

• Use stable network (don’t frequently change IP during registration)
• Use clean browser environment (new profile)
• Fill information consistently (country/phone number/verification method should match exit region as much as possible)
• After registration, perform some normal behaviors first:
  • Complete security settings (backup email, 2FA)
  • Visit Gmail, Drive and other regular products
  • Don’t immediately perform high-frequency logins/batch operations

Note: If Google frequently requires verification codes, SMS verification, or directly blocks, it’s mostly because “IP or environment” risk is too high; go back to Chapter 4 to solve environment problems first.

6. Verify Google Account Region (Entry You Provided)

Your provided viewing entry:

• https://policies.google.com/terms

6.1 How to Use It to Determine “Region”

When opening this page, Google usually displays the current applicable country/region terms at the bottom or certain positions of the page (affected by access region, account settings, etc.). You can use it for a quick side verification:

• If the terms country doesn’t match expectations, it means:
  • Exit IP region doesn’t match expectations, or
  • Account/browser already has regional associations (history cookies, account settings, etc.)

6.2 More Stable Verification Methods (Additional Recommendations)

• After logging into Google account, view account’s country/region related settings (payment information, content region modules will be clearer)
• Key principle: Don’t repeatedly log in across multiple countries in a short time, otherwise both region judgment and risk control will become worse

7. Antigravity Download and Google Login Steps (Key Point)

Download address (you provided):

• https://antigravity.google

The following is the general “App/client → Google OAuth → default browser → callback” process, applicable to most Google login integrations.

7.1 Pre-login Preparation Checklist

• VPN connected and ping0 test passed
• Browser is clean profile
• Google account can log in normally (manually log in once in browser first, confirm no risk control blocking)

7.2 Antigravity Google Login Operation Steps

1. Open Antigravity client/web page
2. Select Continue with Google / Use Google to log in
3. System will jump to default browser for Google authentication
4. Select your target Google account in browser
5. Follow prompts to authorize (Allow / Permit)
6. After authorization completes:
   • Automatically return to Antigravity (mobile usually jumps back to App)
   • Or display “Logged in/can close page”, then manually switch back to Antigravity

7.3 Common Problem Troubleshooting

• Continuous login loop/callback failure

  • Confirm if default browser is restricted by system from callback
  • Try changing default browser to Chrome
  • Turn off “block third-party cookies/cross-site tracking” strict mode (temporarily allow only for this site)

• Google prompts risk, verification code, unable to log in

  • Stop troubleshooting first: don’t keep trying
  • Switch to more stable node/reduce risk environment (new profile, fewer extensions, consistent timezone and language)

• Authorization page won’t open

  • DNS/network link problem: first confirm you can open policies/accounts.google.com
  • VPN line unstable: change line or node region

8. Recommended “Standardized Process” (Can Follow Directly)

1. New server registration and initialization (clean system)
2. Set up VPN according to script (audit script first then execute)
3. Local connect to VPN → ping0 detect IP
4. New browser profile → ping0 detect again
5. Register/prepare Google account (stable, don’t frequently change IP)
6. Use policies/terms + account settings to side-confirm region consistency
7. Install/open Antigravity → Google login (default browser authentication callback)

9. Advanced Tips and Precautions

9.1 Long-term Maintenance Recommendations

• Regularly check IP cleanliness (recommended once a week)
• Avoid logging in many different accounts on the same node
• Maintain browser environment consistency, don’t frequently switch extensions and settings
• Backup important VPN configurations and account information

9.2 Multi-node Management

If you need nodes in multiple regions, it’s recommended to:

• Prepare independent servers for each region
• Use different browser profiles
• Establish clear node-account correspondence table
• Avoid frequently switching different region nodes in a short time

9.3 Security Best Practices

• Use strong passwords and two-factor authentication to protect all accounts
• Regularly update server systems and VPN software
• Monitor abnormal login activities and network traffic
• Comply with local laws and service terms

10. Summary and Follow-up Recommendations

Through the above steps, you should be able to:

1. Establish a relatively “clean” network environment
2. Successfully complete Antigravity’s Google login
3. Understand how to maintain and optimize your network configuration

Long-term recommendations:

• Continuously pay attention to changes in Google’s risk control strategies
• Regularly update your network configuration to adapt to new requirements
• Establish multiple backup solutions to handle emergencies
• Maintain communication with the community to get the latest tips and solutions

Remember, “clean” is a relative concept. The key is to maintain environment consistency and stability, avoiding triggering platform risk control mechanisms.