Documentation +

Fixie Replit

With Fixie static IP, your Replit apps can send any (HTTP, HTTPS, Database, TCP, and more) outbound requests from a fixed set of static IP addresses. Fixie for Replit is language- and framework-agnostic.

Replit assigns your app a fresh outbound IP address on every deploy and restart, which is a problem for any external service, an API, a database, a corporate firewall, that only accepts traffic from an allow-listed range. Fixie sits in front of your outbound traffic and gives you both HTTP and SOCKS V5 proxies, so requests leave from the same pair of IP addresses no matter how often Replit reassigns your container.

Replit Apps run as long-lived containers, so you can open a proxy connection once and reuse it for the life of the process, instead of re-establishing it on every invocation.

Fixie can be used with any backend language, including JavaScript, Ruby, Python, Java, Go, and PHP.

Getting Started

To get started, create a Fixie account, and create a new Proxy Application.

After the proxy is created, go to Proxy's Details page where you'll see a couple of important values:

  • Proxy URL: Your Fixie HTTP/S or SOCKS proxy URL that includes your username, password and proxy server load-balancer to use.
  • Outbound IPs: Your pair of Fixie IP-addresses. These will never change, so feel free to allow-list them with firewalls or services

Configure Your Application

Next, update your application to use your Fixie proxy server. We have documentation for many popular languages supported by Replit:

If you're on Node, see the step-by-step guide for Node.js on Replit for a full API allowlisting walkthrough.

Store your Fixie credentials in Replit's Secrets pane, which encrypts values and injects them as environment variables at runtime. To add a Secret:

  • Open your Repl and find Secrets in the Tools dock (or search for it).
  • Open the App Secrets tab.
  • Click New Secret.
  • Enter a Key (for example, FIXIE_URL) and paste your Fixie proxy URL as the Value.
  • Click Add Secret.

We recommend the following naming conventions for your Secrets so it's easier to follow along with our documentation:

  • FIXIE_URL for your Fixie HTTP/S proxy
  • FIXIE_SOCKS_HOST for your Fixie SOCKS proxy

Workspace Secrets don't automatically carry over to a published Deployment, so after adding a secret in the workspace, open your Deployment's settings and add it there too, or your live app won't see it even though it works in the development workspace. It's a good idea to create different Fixie proxies for different environments (for example, your development workspace and your published Deployment) to keep credentials and logs separate.

Local setup

Replit's own workspace acts as your development environment, so there's typically no separate local setup step. Add the same secret to the workspace's Secrets pane and it's available immediately, no restart required.

If you also run the app outside Replit (for example, on your own machine for testing), replicate the FIXIE_URL and/or FIXIE_SOCKS_HOST values in a local .env file.

Keep sensitive configuration values, like credentials, out of source control. Exclude the .env file in Git with: echo '.env' >> .gitignore.

Changing plans

Use the Fixie dashboard to change your plan. To change the plan, click Change Plan button and select an appropriate plan.

NOTE: Changing the plan won't affect your outbound IP address

Is this guide useful?

Having issues? Please reach out to our team here.