Setting up PostreSQL with QuotaGuard Static IP’s

We suggest you go with the SOCKS proxy using our QGTunnel software. Here are the setup instructions to get you started.

Download QGTunnel into the root of your project

curl | tar xz

Log in to our dashboard and set up the tunnel

Direct, Azure, AWS, and Render users can visit to sign in to their account.

Heroku Users can use Heroku CLI to log into our dashboard with the following command:

heroku addons:open quotaguardstatic

Other option is to log in from the Heroku dashboard by clicking on QuotaGuard Static on the resources tab of your application.

Once you are logged into our dashboard, in the top-right menu, go to Setup. On the left, click Tunnel, then Create Tunnel.

Remote Destination: tcp://
Local Port: 5432
Transparent: true
Encrypted: false

This setup assumes that the remote PostgreSQL server is located at and is listening on port 5432. This is usually the default port.

The Local Port is the port number that QGTunnel will listen on. In this example, we set it to 5432, but if you have another process using 5432, you may have to change it (ie: 5433).

Transparent mode allows QGTunnel to override the DNS for to, which redirects traffic to the QGTunnel software. This means you can connect to either or to connect through the tunnel.

Encrypted mode can be used to encrypt data end-to-end, but if your protocol is already encrypted then you don’t need to spend time setting it up.  In most instances, PostgreSQL is already encrypted but you should always double-check.

Change your code to connect through the tunnel

With transparent mode and matching Local and Remote ports you should not need to change your code. You can also connect to

Without transparent mode, you will want to connect to

Change your startup code

Change the code that starts up your application. In many platforms, including Heroku, this is done with a Procfile. Basically, you just need to prepend your startup code with “bin/qgtunnel”.

So for a Procfile that was previously:

web: your-application your arguments

you would now want:

web: bin/qgtunnel your-application your arguments

Heroku Users: You have a procfile even if it’s not explicitly in your code base. To find it, log into the Heroku dashboard, click on the Resources tab, and you will see a list of your dyno processes. The text you see (like web npm start) next to each one acts as your Procfile if you do not have one explicitly in your code base.

Setup the environment variable

Setup the environment variable QUOTAGUARDSTATIC_URL to be equal to your Connection URL in the Setup page of our dashboard.

If you added us from a cloud provider (Azure, CloudFoundry, Heroku, Render, IBM Cloud, Pivotal, etc) then this is usually done for you.

Please note that QGTunnel handles converting the HTTP URL and port to the SOCKS5 URL and port. So either of the connection URLs is fine.

Commit and push your code

Be sure that the file bin/qgtunnel is added to your repository.

If you are using transparent mode, be sure that vendor/nss_wrapper/ is also added to your repository.

If you have problems

Enable the environment variable QGTUNNEL_DEBUG=true and then restart your application while watching the logs. Send QuotaGuard Support any information in the logs.

Please redact any sensitive information, including your QuotaGuard connection URL.


After you get everything working, we suggest you download your QGTunnel configuration from our dashboard as a .qgtunnel file and put that in the root of your project.

This keeps your project from not relying on our website during startup. Our website might be down for maintenance and your application would fail because it can not find your configuration file.