---
title: "Deploy Firefox | (Just Updated) Remote Browser, Real Login & Profile Survives Redeploys"
description: "Remote Firefox desktop with real login; profile survives every redeploy"
category: "Other"
url: https://railway.com/deploy/firefox-or-just-updated-remote-browser-r
---

# Deploy Firefox | (Just Updated) Remote Browser, Real Login & Profile Survives Redeploys

Remote Firefox desktop with real login; profile survives every redeploy

**[Deploy Firefox | (Just Updated) Remote Browser, Real Login & Profile Survives Redeploys on Railway](https://railway.com/template/firefox-or-just-updated-remote-browser-r)**

Machine-readable deploy manifest (JSON, validated by TemplateCI): https://railway.com/deploy/firefox-or-just-updated-remote-browser-r/manifest.json

- **Creator:** SuperSlowSloth
- **Category:** Other

## Template content

### Firefox

- **Image:** ghcr.io/bon5co/firefox-railway:151.0.3
- **Public domain:** Yes

## Documentation

# Deploy and Host Firefox Remote Browser on Railway

A full **Firefox** desktop in your browser, one click, no local install. It is the
[jlesage/firefox](https://github.com/jlesage/docker-firefox) web desktop wrapped so
it fits Railway: real login gates the whole session, the browser profile lives on a
Railway volume — so your bookmarks, saved logins, cookies, history and extensions
survive a redeploy instead of vanishing with the container — and the service honours
the port Railway assigns, so its healthcheck actually passes.

## About Hosting Firefox Remote Browser

The service runs a single container: a pinned Firefox web desktop served over noVNC.
Every request is gated by real HTTP-layer authentication, not just a raw VNC
password, and both the web login and the VNC channel get a random password per
deploy — the container refuses to start without one, so the desktop is never exposed
with empty or shared credentials. The profile directory is mounted on a volume at the
path Firefox actually uses, and CJK fonts are enabled so Japanese, Chinese and Korean
pages render instead of showing empty boxes. TLS is terminated at Railway's edge, so
the container speaks plain HTTP behind it.

## Why Deploy Firefox Remote Browser on Railway?

Railway gives the container a public HTTPS URL, a managed volume and one-click
redeploys — exactly what a persistent remote browser needs. You get a real Firefox
reachable from any device: a clean, logged-in browsing session that keeps its state,
a residential-free egress point for testing, or a throwaway desktop for opening links
you would rather not touch on your own machine — without running a VM, a VNC server or
a TLS certificate yourself. The password is generated for you and the profile is kept
across deploys.

## Common Use Cases

- A persistent, logged-in browser reachable by URL from any device.
- A disposable desktop for opening untrusted links away from your own machine.
- A shared testing or demo browser with a known, private login.

## Dependencies for Firefox Remote Browser

- Firefox 151.0.3 on the jlesage web-desktop stack, pinned by digest in the wrapper
  image.

### Deployment Dependencies

- None beyond the container itself. The image is self-contained; no database, cache
  or external service is required.


## Similar templates

- [Rocky Linux](https://railway.com/deploy/rocky-linux) — Hosted Rocky Linux 9 workspace with SSH and persistent storage. 🚀
- [Foundry Virtual Tabletop](https://railway.com/deploy/X5tR6G) — A Self-Hosted & Modern Roleplaying Platform
- [Letta Code Remote](https://railway.com/deploy/letta-code-remote) — Run a Letta Code agent 24/7. No inbound ports, just deploy.

Open this page in a browser: https://railway.com/deploy/firefox-or-just-updated-remote-browser-r