Google Cloud Setup

  • Go to and press “Get Started for free,” sign into your google account if you haven’t already.
  • Fill out the forms it asks you, and for account type choose “Individual.”
  • Detailed information about how to do billing and whatnot is left to your discretion. Privacy cards may work.
  • Once you’re to the console, go to “APIs & Services” then “Credentials” on the left side tab:

  • Then click “Create Credentials” then “Service Account Key” (seen below):

  • Choose “New Service Account”, name the account, for Role choose Project > Owner. Choose to download the key as JSON. Press create. Save the JSON file to somewhere you’ll remember. Personally I do C:/pdkeys. You can name the file or leave it’s name as is so long as you’ll remember where it is.
  • Next click this icon in the upper left and click Compute Engine -> VM instances. If your account is new, you’ll see this screen, in which case you should wait for it to finish getting compute engine ready:

(it may not refresh automatically)

Once it gives you the option to create a VM you’re good to go.

AWS Setup

  • Once you’re at the console, go to your username and then select “My Security Credentials”:
  • Go to the “Access Keys” dropdown and press “Create New Access Key”

  • A popup should then show the following, from which you should click “Download Key File”
  • Save the csv file to a location you’ll remember with either the default “rootkey” name or a name of your choosing

Once that file is downloaded you’re good to go!

Making Proxies

  • Go to the proxies tab and click on the folder icon. Choose the location of either the JSON file you downloaded (if using Gcloud) or the csv file (if using AWS). Don’t change those extensions since they are used to determine what provider you are using.
  • After you’ve loaded your credentials, wait a second and you should see the region and zone dropdowns become populated:

  • If they don’t, make sure you’ve followed all the setup steps carefully.
  • Once they are, you can choose a region and zone and press Spawn Proxy. Wait a second, and you should see a “Success” toast or an error message pop up.

Managing Proxies

  • Whenever you restart the bot or create a new proxy, you should set the credentials for all proxies by typing the username and password into these boxes:
  • The Start All button: will start any stopped proxies. 
  • The Stop All button: will stop any running proxies. 
  • The Delete All button: will delete all the proxies. 

On Google Cloud and AWS, you aren’t billed for Stopped or Deleted servers.

  • Pressing View All button: brings up a list of all your spawned proxies:

Proxy Status Meanings:

  • Running: proxy is ready to accept connections
  • Broken or Installing: server is “Running” but the proxy is not ready yet. If a server is stuck here it may need to be stopped and started again, or deleted if the issue persists.
  • Off / Booting: server is not running, most likely it is turned off or just starting.

Adding proxies to the proxy list:

  • Press the copy button on a proxy:
  • Press “Copy All”:
  • Or select a number of proxies by checking the checkbox and press “Copy Selected”:
  • This will copy the proxies to your clipboard.


My proxies aren’t creating: If an error shows, see if you can resolve it. Otherwise, make sure you’ve followed all the steps in the setup guide.

When I copy the proxies the username and password is “Error”: Try setting the username and password again

My proxies show “Running” but don’t work: First of all, try testing in an external proxy tester. If the issue still persists, try setting the authentication again.

This error with AWS:

Just wait and watch your email, you’ll get access to the zone shortly