Free tools Windows power users keep installed
One-click scans. No signup required.
The dependable pattern is a single Linux VPS running Rancher, with your Node.js application and MongoDB deployed as separate services on a private network. Persist Rancher at /var/lib/rancher, mount a durable volume at MongoDB’s data directory, publish only the application through HTTPS, and keep credentials out of Git. The result is a repeatable deployment that survives container replacement and supports controlled web-service updates.
Antihost offers Linux VPS plans with full root access, unlimited traffic on a 1 Gbps port and a 14-day free trial.
What you are building
There are four distinct layers:
- VPS host: A supported Linux distribution, Docker, firewall, DNS, patching and backups.
- Rancher: Installed with the supported single-node Docker method. Rancher’s Docker installation uses an embedded local Kubernetes cluster and requires
--privilegedfor features that run containers within containers. - Application workloads: A Node.js web service and a MongoDB service deployed through Rancher as services or their Kubernetes workload equivalents.
- Public edge: An ingress controller or reverse proxy terminates TLS and forwards requests to Node.js. MongoDB remains reachable only on the internal service network.
Do not run the application by connecting to localhost for MongoDB. Inside a container, localhost means that same container. Use the database service name, such as mongo, as the hostname.
As an Amazon Associate I earn from qualifying purchases.
Recommended Free Tools
Prerequisites and decisions
Host and account requirements
- A Linux VPS using a distribution supported by the current Rancher single-node Docker documentation.
- A Docker release supported by that Rancher version.
- An administrative account that uses
sudorather than routine root login. - A DNS A and, if you use IPv6, AAAA record pointing your application hostname at the VPS.
- Host storage for Rancher state, MongoDB data, logs and backups. Size the machine from measured application memory, CPU and MongoDB working-set requirements rather than an assumed benchmark.
Choose names before deploying
Use separate hostnames when practical. For example, reserve one hostname for the Rancher console and another for the application. This makes certificate and access-control rules easier to reason about. If the same public listener handles both, route by hostname and never create a public route to the MongoDB service.
Understand the single-host trade-off
A one-VPS design is simple and economical, but the VPS is a single failure domain. A disk failure, host outage or destructive operator error can take out Rancher, the application and MongoDB together. Off-host backups and a tested restore are therefore part of the deployment, not an optional enhancement.
#1 Best Overall
- BLUE LIGHT BLOCKING GLASSES: Our blue light glasses for women boast UV400 protection, blocking harmful blue rays from computer screens. With these bluelight glasses women, you can enjoy gaming, reading, or watching TV with no worries of eye strain.
- EYE RELIEF: Our blue light glasses are engineered to reduce blurry vision or strain caused by prolonged screen time. These womens blue light glasses aid in better sleep by preventing blue light from disrupting your natural sleep cycle, helping you fall asleep faster and enjoy a more restful night's sleep, making them the perfect christmas present.
- COMFORTABLE: Crafted from durable material, our trendy blue light glasses for woman or blue light glasses men ensure long-lasting comfort. The high-transmittance lenses accessories, gamer gifts for men, help keep your eyes relaxed. Perfect stocking stuffers, gifts for gamers men, christmas gifts for men, halloween costumes.
- LIGHTWEIGHT: These clear blue light glasses feature a lightweight frame, meaning they’ll stay comfy for long-term wear. Perfect as blue blockers glasses for women or mens blue light glasses, these non-prescription fake glasses for men can be worn throughout the day. The blue light blocking glasses women feature polycarbonate HD lenses, which are anti-reflective and restore true color.
- WORRY-FREE PURCHASE: If you experience any issues, our support team is ready to assist you quickly. These are the perfect costume glasses for cosplay dressing up.
1. Provision and harden the VPS
- Create a non-root administrator. Add an account, install its SSH key and grant only the administrative privileges needed to manage Docker and the host. Disable password authentication and direct root SSH access if your provider and recovery process support it.
- Patch the operating system. Apply security updates before installing Rancher or application images. Reboot when the kernel or other system components require it, then confirm Docker starts normally.
- Install a supported Docker release. Follow the Docker installation method for the selected Linux distribution and verify the daemon is running. Do not assume the distribution’s oldest repository package is compatible with your Rancher release.
- Configure the firewall. Allow SSH only from the administration networks you actually use. Allow web traffic on TCP ports 80 and 443 when those ports are needed for HTTP redirection, ACME validation or HTTPS. Do not allow MongoDB’s database port from the internet.
- Point DNS to the VPS. Create the A/AAAA records and wait for them to resolve from an external network. A certificate request and ingress rule will fail if the hostname still points elsewhere.
- Prepare protected storage. Create a host directory for Rancher state and separate storage for MongoDB data. Apply ownership and permissions deliberately; do not place either directory inside a disposable build workspace.
Keep a record of the VPS provider’s recovery console and snapshot procedure. You need an out-of-band path if a firewall change blocks SSH.
2. Install Rancher with persistent state and SSL
Rancher documentation states that SSL is required for secure communication, including login and cluster interaction. For a public installation, use a certificate from a recognized certificate authority or the documented Let’s Encrypt flow. Decide who terminates TLS before you publish the console: Rancher itself, an upstream reverse proxy, or an ingress layer.
Persist Rancher’s state
Bind-mount a durable host path to /var/lib/rancher. Rancher stores management data there; if the container is replaced without that mount, the management state can disappear with the container.
sudo mkdir -p /srv/rancher
sudo chmod 700 /srv/rancher
sudo docker pull rancher/rancher
sudo docker run -d
--name rancher
--privileged
--restart=unless-stopped
-p 80:80
-p 443:443
-v /srv/rancher:/var/lib/rancher
rancher/rancherFor production, use a currently supported Rancher release and pin the image tag or digest after checking the compatibility requirements for your Docker and Linux versions. The untagged image in the example illustrates the mount and runtime flags; it is not a release-management policy.
Complete the first login safely
- Open the Rancher hostname over HTTPS and complete the initial administrator setup.
- Confirm the browser shows a trusted certificate. A self-signed certificate may be acceptable for an isolated test, but it creates trust and automation problems for a public service.
- Record the bootstrap and administrator recovery information in a password manager. Do not put it in the application repository or an unencrypted note on the VPS.
- Check Rancher’s events and container logs before creating workloads. A certificate, permission or disk problem is easier to fix before the application depends on the installation.
3. Build a production Node.js image
Build the application as an immutable image. Pin a Node image tag appropriate for the project, install only production dependencies in the runtime image, copy the application, set NODE_ENV=production, and make the process listen on all interfaces rather than only 127.0.0.1.
Rank #2
- WINDEX GAMING WIPES: effortlessly clean all your gaming gear and gaming electronics in one easy step with our new Windex Gaming Wipes
- AMMONIA FREE: our ammonia-free formula is safe to use on all of your favorite gaming equipment like consoles, headsets, controllers, screens, keyboards, and more
- PRE-MOISTENED WIPES: each wipe instantly removes dust, dirt, and stubborn smudges and fingerprints leaving a streak-free shine
- ANTI-STATIC: great for cleaning and wiping down your gaming gear and electronics leaving behind no visible residue
- COMPACT RESEALABLE PACKAGE: store your pack of Windex Gaming Wipes anywhere in your home for whenever a quick and easy wipedown is needed
FROM node:22-bookworm-slim
WORKDIR /app
ENV NODE_ENV=production
COPY package*.json ./
RUN npm ci --omit=dev
COPY . .
EXPOSE 3000
USER node
CMD ["node", "server.js"]The exact Node major version must match your application’s supported runtime. If the project uses a build step, use a multi-stage Dockerfile: compile in a builder stage and copy only the compiled output and production dependencies into the final stage. Add a .dockerignore that excludes node_modules, local environment files, logs and source-control metadata.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Make health checks meaningful
Expose a lightweight endpoint such as /healthz that returns success only when the process is ready to serve requests. A liveness check should not fail merely because MongoDB is briefly unavailable; use a separate readiness check when your orchestrator supports it. During deployment, test both the endpoint and a real database read/write operation.
4. Define the Node.js and MongoDB services
Whether you enter the definition as Compose-compatible configuration or Kubernetes workloads in Rancher, preserve the same properties: one private network, a service named web, a service named mongo, no public MongoDB port, and a durable MongoDB volume.
Compose-style reference
services:
web:
build: .
image: your-registry/your-node-app:release
restart: unless-stopped
env_file:
- ./production.env
environment:
NODE_ENV: production
MONGODB_URI: mongodb://appuser:replace-this-secret@mongo:27017/appdb?authSource=appdb
depends_on:
- mongo
networks:
- app_private
ports:
- "3000:3000"
mongo:
image: mongo:8
restart: unless-stopped
environment:
MONGO_INITDB_DATABASE: appdb
MONGO_INITDB_ROOT_USERNAME: root
MONGO_INITDB_ROOT_PASSWORD: replace-this-secret
volumes:
- mongo_data:/data/db
networks:
- app_private
networks:
app_private:
driver: bridge
volumes:
mongo_data:The image tags and credentials in this example must be replaced with values selected for your release; never commit the file with real passwords. In a Rancher-managed Kubernetes deployment, create a namespace, a MongoDB workload with a persistent volume claim, a ClusterIP service named mongo, and a web workload with a service that the ingress can target. The internal DNS name remains the service name, not localhost or the VPS hostname.
Authentication details
MongoDB’s initialization variables apply when the database is first initialized. Changing them later does not automatically change an existing user’s password. Create an application user with only the permissions it needs and use its database-specific connection string. Keep the root account for administration rather than normal application traffic.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Rank #3
- Ergonomic & Adjustable Design: Fight "text neck" and improve your posture. Designed for comfort, it offers an adjustable height (7.1in-8.5in) (1.4in adjustable range) and angle (5°-85°) Please note: cell phone stand is only 9 inches tall—the length of a standard pencil
- Without blocking subtitles Perfect for office desk Tiktok Face Time Zoom video—this is the ultimate kitchen desk essential for phones! Perfect viewing experience while reducing neck back strain, A must-have for gamers streamers desk, and anyone who values both style and support!
- Sleek & Stable Design fits Otterbox Case: Say goodbye to bent cables, tangles, and tip-overs! LISEN’s stylish adjustable desk phone holder features a built-in charging hole and smart cable management, keeping your phone secure and your workspace clutter-free cool gadgets for men
- ANTI-SLIP DESIGN free hands: The under 10.00 items easy gadgets back and the bottom of this kitchen essentials for women are fully covered by anti-skid silicone, which LISEN stand up desk decor can provide maximum protection device from any scratches and slides
- Your Perfect Viewing Companion:If your product arrives damaged or breaks within 365 days, reach out to LISEN for a quick and hassle-free solution. Struggling with assembly, like tightening the screw? We’ve got your back! Your experience matters to us. (Product including: phone Holder stand*1, screw*1, hexagon screwdriver*1, specification*1)
Startup ordering is not readiness
depends_on or an equivalent workload ordering starts MongoDB before Node.js, but it does not prove that MongoDB is accepting authenticated connections. Make the application retry with bounded backoff during startup, and add a MongoDB health check or readiness probe where your Rancher workload type supports it.
5. Keep MongoDB data after restarts
Mount a named volume or host-backed volume at MongoDB’s data directory, normally /data/db for the official image. Docker volumes are managed independently of an individual container, so deleting and recreating the MongoDB container does not delete the volume unless an operator explicitly removes it.
- Use dedicated storage rather than the container’s writable layer.
- Monitor free space; a full filesystem can stop writes and prevent clean shutdown.
- Back up the database off the VPS. A local volume and a local snapshot do not protect against host loss or accidental deletion of the host.
- Test restoration into a separate MongoDB instance. A backup that has never been restored is an assumption, not a recovery plan.
- Back up Rancher’s
/var/lib/rancherstate separately from MongoDB. Restoring one without the other can leave management metadata and application data out of sync.
Safe container replacement test
- Insert a known test document through the application.
- Record its identifier and verify it can be read back.
- Recreate only the MongoDB container or workload without deleting its volume.
- Wait for the readiness check, then read the document again.
- Remove the test document and record the result.
Do this in a non-production environment first. Never use a volume-removal command as part of a routine update.
6. Handle credentials without leaking them
Do not commit MongoDB passwords, application secrets or TLS private keys to Git. Docker’s environment documentation warns against using ordinary environment variables for sensitive passwords and recommends secrets instead.
For Compose-style deployments
- Keep a production environment file outside the repository, restrict it to the deployment administrator, and verify its permissions before starting the stack.
- Use Compose secrets where the selected Docker and Rancher integration supports them. Mount the secret into the container and have the application read the file rather than printing the value in a process listing or log.
- Do not echo the environment file in CI logs. Mask secret values in the build and deployment system.
For Rancher-managed Kubernetes workloads
Create Kubernetes Secret objects for the connection string and credentials, grant access only to the application namespace, and reference them from the web workload. Keep the MongoDB root credential separate from the application credential. Rotate both on a schedule and immediately after suspected exposure; update the application secret and database user in a coordinated change so the service does not lose access.
Rank #4
- Easy Installation: Our gaming lights have been designed to enhance your entertainment experience. Simply position the led light bar next to your TV or game console to create a game room environment with ease. They come with USB power and a 60 inch cord for direct mounting and mobility
- Audio Syncing & Extensive Mode: The built-in high-sensitivity music sensor allows you to sync the TV led lights to your favorite music. Lights react and move to the beat of music, film and game audio, creating an incredible immersive sound and light experience – and all without the need for an additional hub. You can choose from 64+ patterns, including strobe, illusion, jump, energy, gradient, running, chasing, fluttering mode etc. Each mode can be applied to different scenes
- 64+ Chasing IC+RGB & W Effect: The independent control design of IC+RGB and white all-in-one multifunctional rgbw led bar lights monitor backlight allows you to easily switch the led lights for desk between IC+RGB and white to enjoy a variety of lighting effects, you can choose white lighting mode with high brightness for better illumination when working, etc. Choose IC+RGB lighting mode when you need to create an entertaining atmosphere for the light show, 16 million colours of Color changing rgb light bar let you dance to the beat and create a dynamic party atmosphere
- Dynamic and Dimmable Lights: 1%-full brightness free brightness adjustment gives you the flexibility to adjust dimmable led light bar for room decorations or a variety of occasions
- USB Powered: USB light bars for room can be powered by powernank, usb charger, TV, Monitor, laptop PC mainframe, making behind TV led lighting bar easy to install in any location.TV led lights are powered by the TV usb interface / PC mainframe, can be turned on/off synchronously with TV / PC
7. Put the application behind HTTPS
Expose only the web service. Route the public hostname to an ingress controller or NGINX layer that terminates TLS, then proxy to the Node.js service on its private service port. Rancher’s external access uses ports 80 and 443, and its documentation describes recognized-certificate-authority and Let’s Encrypt choices.
- Create the DNS record for the application hostname and verify it resolves to the VPS.
- Configure the certificate issuer and obtain a certificate for that hostname. Keep the private key in the ingress or secret store, not in the application image.
- Create an ingress rule that maps the hostname and HTTPS path to the
webservice. - Redirect HTTP to HTTPS unless you specifically need plain HTTP for certificate validation.
- Forward the original host and protocol headers so the Node application can generate correct secure URLs and enforce secure cookies.
- Confirm that the firewall exposes only the ports required by SSH and the web edge. There should be no DNS record, firewall rule or ingress route for MongoDB.
If Rancher’s own console and the application share a VPS, use distinct hostnames and routing rules. Verify both certificates independently after every ingress change.
8. Deploy and verify the stack
Initial deployment sequence
- Build the web image in a controlled environment and push it to a registry accessible to the VPS, or build it on the VPS if that is your chosen release process.
- In Rancher, select the target cluster and namespace or project. Deploy MongoDB first with its persistent storage and secret references.
- Wait for MongoDB to pass its health or readiness check.
- Deploy the web workload with the MongoDB service name in
MONGODB_URI. - Create the ingress rule and certificate, then wait for the web workload to become ready.
- Open the public HTTPS hostname and exercise the health endpoint.
- Create, read, update and delete a test record through the application. Check that the operation appears in the application logs without exposing credentials.
- Inspect Rancher events, workload status and logs. Resolve image-pull, permission, readiness and mount errors before calling the deployment complete.
What to verify before handing over the URL
- The browser receives a trusted certificate and redirects to HTTPS.
- The application can resolve
mongoand authenticate with its application user. - MongoDB has no published host port and is reachable only from the private network.
- The MongoDB volume is mounted at the intended data directory.
- Restart policies are enabled for both services.
- Logs, disk usage and backup jobs are visible to the operator.
9. Update the Node.js service without touching MongoDB
Build a new, uniquely tagged web image for each release. Avoid reusing a mutable tag that makes it impossible to identify what is running.
docker compose build web
docker compose up --no-deps -d webThis is Docker’s documented production Compose update pattern: rebuild the selected service and recreate it without restarting its dependencies. In Rancher, apply the new image tag to the web workload and let Rancher perform the rollout. Do not recreate MongoDB for an application-only change.
Release checklist
- Run tests and database migration checks before building the image.
- Confirm the new image contains no development secrets or local files.
- Deploy the image with a readiness probe so traffic moves only to a ready instance.
- Call the health endpoint and perform a safe database read after rollout.
- Watch logs and events for connection failures, elevated error rates or repeated restarts.
- If the release fails, roll the web workload back to the previous known-good image. Leave MongoDB untouched unless the release included a deliberately planned, reversible schema change.
For schema changes, use backward-compatible migrations: deploy code that can work with both schemas, migrate data, then remove old fields in a later release. A container rollback cannot undo a destructive database migration.
Best Value
- Compatible with Wide Screens - To ensure compatibility with the dual monitor mount, your each monitor must meet three conditions at the same time: First, computer screens size range: 13 to 32 inches. Second, screen weight range: 4.4 to 19.8 lbs. Third, the back of the monitor screen must have VESA mounting holes with a pitch of 75x75mm or 100x100mm.
- Regarding the compatibility with desks - Your desk must meet three conditions at the same time: First, desk material: Only wooden desks are recommended, plastic or glass desks cannot be used. Second, desk thickness range: 0.59" - 3.54". Third, the bottom of the desk should not have any cross beams or panels, as this will interfere with installation. We recommend carefully checking that your desk and monitors meets all above conditions before purchasing.
- Dual C-Clamp Hold - Worried your dual monitors might wobble or slip? Our upgraded base uses a larger platform plus a dual C-clamp structure to lock the dual monitor arm firmly to your desk. Each arm safely keeps your screens steady while you type, click and game—no shaking, no sliding, just a clean and secure setup you can trust every day. It also provides Grommet Mounting installation choice, both options ensure stable and secure fixation for your 0.59" - 3.54" desk.
- Full-Motion Adjustment For Comfortable View - Pull the screen closer when you’re deep in a spreadsheet, push it back to watch videos, or rotate to portrait for coding — moving everything smoothly with just one hand. The monitor stand offers +85°/-50° tilt, ±90° swivel and 360° rotation. Raise your monitor up to 15.75″ to support a healthy sitting posture. Whether you’re working from home, gaming through the night, or switching between video calls and documents, getting the screens to your natural line of sight helps relieve neck, shoulder and back strain so you can stay focused longer with less fatigue.
- Keep Your Desk Organized: By lifting both screens off the desktop, this dual monitor stand opens up valuable space for your keyboard, notebook, docking station or a simple, clutter-free work area. Built-in cable management guides wires along the arms, keeping cords out of sight and out of the way. Enjoy a tidy, modern workstation that looks as good as it feels to use.
10. Operate the VPS after launch
Backups and recovery
- Schedule MongoDB logical or filesystem-consistent backups according to the value of the data.
- Copy backups off-host and encrypt them at rest and in transit.
- Retain multiple points in time so a bad deployment or accidental deletion is recoverable.
- Back up Rancher’s
/var/lib/rancherdirectory and document the matching Rancher release and Docker environment needed to restore it. - Perform a restoration exercise and measure how long it takes to return the application to service.
Monitoring and maintenance
- Alert on MongoDB health failures, repeated web restarts, filesystem exhaustion and backup failures.
- Retain enough application and ingress logs to diagnose a failed release, while applying a retention limit so logs cannot fill the disk.
- Patch the host, Docker, Rancher and application base images on a planned schedule. Read release notes for compatibility changes before upgrading.
- Review firewall rules and unused images, volumes and accounts periodically.
- Use production-specific Compose overrides or equivalent Rancher configuration for ports, environment, restart policy and other deployment changes rather than altering development files ad hoc.
Rancher on one VPS versus larger architectures
| Architecture | Operational simplicity | Failure and recovery model | Scaling path | TLS and ingress | Database topology |
|---|---|---|---|---|---|
| Rancher with Node.js and MongoDB on one VPS | Lowest operational overhead; one host and one control surface | Single-host failure domain; requires off-host backups and tested restore | Limited by the VPS; later migration is required for additional failure domains | One ingress or reverse proxy can terminate HTTPS for the app and route by hostname | Single MongoDB instance unless you design replication separately |
| Multi-node Kubernetes managed through Rancher | More networking, storage and upgrade work | Can tolerate selected node failures when replicas and storage are designed correctly | Supports workload and node growth beyond one machine | Ingress and certificate management become cluster-wide concerns | Requires a deliberate replica, backup and failover design |
| External or managed MongoDB with the app on a VPS | Less database administration on the VPS, but adds a provider dependency | Database resilience may improve; application host remains a separate failure domain | Database capacity can scale independently of the web process | Only the application ingress is public; database access uses private or restricted connectivity | Provider topology, backup retention and recovery objectives must be verified separately |
The single-node arrangement is appropriate when simplicity and cost control outweigh high availability. Move to multiple nodes or an external database when the application’s recovery objective, traffic pattern or data durability requirements exceed what one VPS can provide. The cited Rancher and Docker documentation explains the single-node mechanics, not a universal price or service-level comparison.
Troubleshooting the common failures
Node.js reports a connection-refused or DNS error for MongoDB
Check that both workloads share the same private network or namespace, that the database service is actually named mongo, and that the URI does not use localhost. Confirm MongoDB readiness and credentials from the web container’s configuration without printing the password.
Data disappears after a MongoDB restart
Inspect the workload definition and confirm a volume is mounted at /data/db. Determine whether an operator removed the volume while recreating the container. Restore a known backup if the original volume was deleted; restarting a container cannot recover a removed volume.
Rancher loses its configuration after replacement
Verify that the host path or durable volume is mounted at /var/lib/rancher and that the Docker daemon can read and write it. A container recreated without that mount starts with new state.
The HTTPS certificate cannot be issued
Check DNS resolution, firewall access to the required web ports, hostname spelling and any existing proxy or ingress rule. Make sure the certificate method you selected is supported by the current Rancher or ingress configuration.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitchesThe web workload loops during startup
Read the workload events and application logs. Common causes are a missing secret, a wrong image architecture, a database that is not ready, a Node runtime mismatch or an application bound only to loopback. Add bounded connection retries and a readiness probe rather than relying solely on startup order.
The VPS fills its disk
Check MongoDB data, Docker images, container logs, Rancher state and backup staging directories separately. Prune only unused images and stopped containers after confirming they are not needed for rollback. Expand storage or move durable data before the filesystem reaches a critical level.
Quick Recap
Final deployment checklist
- Supported Linux, Docker and Rancher versions are recorded.
- SSH is restricted, the firewall exposes only required services, and DNS is correct.
- Rancher runs with
--privileged, restart policy and a durable/var/lib/ranchermount. - The Node image uses a compatible pinned runtime and production dependencies.
- Node.js connects to MongoDB by service name on a private network.
- MongoDB has a durable
/data/dbvolume and no public port. - Secrets are stored outside Git and protected with restrictive permissions or secret objects.
- HTTPS terminates at ingress or a reverse proxy, with a trusted certificate.
- Health, read/write, restart and backup-restore tests have passed.
- Web-only releases use a new image and do not recreate MongoDB.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
