Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Antihost offers VPS plans with one-click n8n, NVMe storage and a 14-day free trial.
Yes, you can replace an n8n Docker container without losing workflows. Your workflows, credentials, execution data, and user settings survive only when the persistent database and /home/node/.n8n data are retained, the encryption-key configuration is unchanged, and you have a tested backup. For a normal Docker Compose installation, the controlled update is:
docker compose pull
docker compose down
docker compose up -dThat sequence removes the old containers and network, not a named data volume, unless you explicitly ask Compose to remove volumes. The safe process is to review release notes, record the current image tag, back up the data, verify the mount, pull a reviewed image, monitor migrations, and test important workflows before declaring the upgrade complete.
Free tools Windows power users keep installed
One-click scans. No signup required.
What actually protects your n8n data
A Docker container is replaceable. The data that n8n writes must live outside that container in a persistent volume, bind mount, or external database. If you start a new container with an empty data location, n8n has no way to see the old installation and will present what looks like a fresh setup.
n8n’s Docker documentation specifically warns that Even when using a different database, it is still important to persist the
That directory and your database are the two things to protect before changing an image./home/node/.n8n folder, which also contains essential n8n user data including the encryption key.
#1 Best Overall
- Powerful Turbo Fan:CAGIWIRU Electric Air Duster have reached speed up to 130000RPM,Can efficient remove dust and debris.With LED light and Three Adjustable Speed to meet with different cleaning tasks.
- With Attached USB C Fasting Charging cable.Charing 3 hours,Enjoy up to 240 minutes of use on the lowest setting, For third speed can use for 25mins.with four charging options to meet with your needs.
- Wide Application:Upgraded attached 5 different nozzles,making it suitable for a variety of scenes, such as car,pet, pc, keyboards, and other electronic devices. It also serves for office and home clean duster.
- Handy Design & Portable:Cordless air duster electric nozzle is Light weight and small size, design and comfortable to hold and space saving, convenient to carry around. You can put it in your room or inside the car without taking up space.
- Warranty & Support: Our Electric air duster comes with 5 years warranty and 24/7 customer service. During this period, if you have any questions,pls kindly feel free to contact us.
SQLite installations
The default single-container deployment uses SQLite. The database file, credentials metadata, user information, and other instance state are stored beneath /home/node/.n8n. A named volume such as n8n_data:/home/node/.n8n keeps that directory when the container is recreated. A bind mount pointing to a host directory provides the same persistence.
If the mount is accidentally removed, renamed, or changed to a new empty volume, the replacement container cannot see the old SQLite database. The workflows have not been deleted from the old volume, but they are invisible to the new container until the original mount is restored.
Recommended Free Tools
Postgres installations
With Postgres, workflow and execution data live in the Postgres database, while /home/node/.n8n still contains important local state, including the credentials encryption key and configuration-related files. Back up the Postgres database and retain the n8n data mount. An n8n image update is not the same operation as a Postgres major-version migration; handle a database-engine migration as a separately planned change.
The encryption key is non-negotiable
n8n encrypts stored credentials. The key used to decrypt them must remain the same after the upgrade. Preserve every existing environment variable and secret, including an N8N_ENCRYPTION_KEY setting when your deployment defines one. If the key is missing or different, workflows may still appear while their credentials fail to decrypt, producing errors when nodes try to authenticate.
Before changing the image
Do the preparation while the current instance is healthy. It gives you a known-good rollback point and prevents an avoidable outage caused by a forgotten setting.
Read release notes and breaking changes
Check the n8n release notes and the upgrade guidance for the version you intend to run. The official Docker guidance says: Before you upgrade to the latest version make sure to check here if there are any breaking changes which may affect you.
Pay particular attention to changes affecting node behavior, authentication, database support, queue mode, or environment variables.
Write down the image tag currently running and the tag you plan to install. A pinned tag such as docker.n8n.io/n8nio/n8n:1.XX.YY makes the change reproducible and gives you a precise rollback target. The exact version number should be the version you reviewed; do not copy the example tag literally.
Rank #2
- Screen Cleaner is Your Screen’s New Bestfriend! - EVEO is proud to present a screen cleaner that’s perfectly suited for your TV. Meet your new screen cleaner, computer screen cleaner, laptop cleaner, iPad cleaner, Macbook,tv cleaner or any other electronic device. Our screen cleaner spray and wipe along with the included plush microfiber cloth, easily removes dust, fingerprints & other smudges on the screen’s surface. Clean effectively for a streak-free screen
- Gentle on your Screens - Our screen cleaner spray and wipes is compatible to be used even for the most sensitive LCD, LED, CRT, and OLED screens in proper use. Be at ease knowing that this product is compatible with all the major brands: LG, SONY, Samsung, Sharp, iPad, iPhone, Android screens, Kindle, PC monitors - we’ve got you covered! Can be used as LCD screen cleaner, tv cleaner, smart tv screen cleaner, and more
- Premium Super Soft Plush Microfiber Cloth - Included in this efficient screen cleaning kit. This screen cleaner spray and wipe has our signature plush microfiber cloth specially designed to comply with screens and monitors and leave them streak-free. Has been shown to effectively absorbs stubborn stains, zero streaks, and no fiber shedding. Always use this together with our screen cleaner for the best results
- Easy-to-Use Screen Cleaner Kit + microfiber cleaning cloth - The EVEO Screen Cleaning Kit will easily be your new favorite tool when it comes to taking care of the things you love most, quick and easy solution for a streak-free screen. Simply screw on the sprayer gun on the screen cleaner bottle. Spray the cleaning liquid onto the microfiber cloth, then wipe the screen until desired cleanliness & shine is achieved.
- Quality Screen Care Kit Worth Purchasing - Enjoy a convenient Screen Cleaner anytime, anywhere you need it. Your satisfaction is our top priority. We stand behind the quality of our products and that’s why, you shouldn’t be worrying at all. We manufacture the Best Screen Cleaner. and can be used for laptop cleaning kit, laptop screen cleaner, tv screen cleaner for smart tv. MacBook screen cleaner, monitor cleaner or screen cleaner spray for electronic devices with microfiber cleaning cloth
Record the current configuration
Save a copy of the Compose file and note the effective configuration before editing it. Confirm the service’s image, volume declarations, database connection variables, encryption-key setting, public URL settings, webhook configuration, and any queue or worker settings. Running docker compose config renders the merged Compose configuration and is useful for spotting an override file that changes a mount or environment variable.
Also record the container’s current version from the n8n user interface or startup log. Keep this information with the backup so you know which image and database state belong together.
Choose a maintenance window
Stopping the main n8n container pauses webhook handling, scheduled triggers, and manual executions. Make the change when missed triggers can be reviewed and downstream systems can tolerate a short interruption. Do not terminate a process while n8n is running a database migration.
Back up the persistent data
Stop n8n before copying a SQLite volume so the database is not changing during the backup. For Postgres, create a consistent database backup using the backup method already used for that server, and also preserve the n8n data directory.
Back up a named SQLite volume
If your Compose file uses the documented volume name n8n_data, stop the service and archive the volume from a temporary container:
docker compose stop n8n
docker run --rm -v n8n_data:/source -v "$PWD":/backup alpine sh -c 'tar czf /backup/n8n_data-pre-upgrade.tgz -C /source .'The archive is written to the directory from which you run the command. Store it outside the Docker host as well; a copy on the same disk does not protect against disk failure. If your volume has a different name, use that name after confirming it with docker volume ls and the Compose file.
Back up a bind mount
For a bind mount, identify the host directory mapped to /home/node/.n8n, stop n8n, and create a filesystem snapshot or archive of that directory. Do not copy only a single workflow export: exports do not include all instance settings, execution history, or the credentials encryption key.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallCrashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteRank #3
- 【Large size】：Measuring 800 x 300 mm/ 31. 5×12 inches, which is wider and taller than others. Large mouse pad can perfectly fit your keyboard and mouse of any size, and there is also ample space for peripherals such as phones, tablets, etc.
- 【LED backlight mouse pad】：Blade Hawks RGB mouse pad provides 7 static modes and 7 dynamic modes will give you the options you are looking for. Power-off memory function remembers the last lighting mode you selected. The super glow fiber Chroma will give you a colorful gaming setup that you want.
- 【Anti-slip rubber base】：Made from Natural rubber, this gaming mousepad will firmly grip your desktop, allowing you to enjoy the ultimate precision in the games you are most passionate about. It also comes with a texture that enhances this ability even further.
- 【Smooth and waterproof surface】: Micro-textured cloth surface, for extremely precise mouse control and a smooth movement. When liquid splashes on the gaming mouse pad, it forms water droplets and slides down. Will not delay your work or gameplay.
- 【Plug and play】: This mouse and keyboard pad is powered by USB, plug and play, no driver required. One button control light modes. Press one time to change the lighting mode, press twice to change the brightness, press and hold about 3 seconds turn ON/OFF.
Back up Postgres and binary data
Use a database-consistent Postgres backup such as the scheduled dump or snapshot procedure maintained for your database service. Verify that the backup can be read before the upgrade. If binary data is stored in an external object store, include that store in the recovery plan and retain its configuration. A database backup without the matching encryption key cannot restore usable credentials.
Verify the Compose file before recreating containers
Keep the existing persistent declaration, for example:
volumes:
- n8n_data:/home/node/.n8nDo not change the volume name, the mount target, or the host directory while changing the image. Keep all existing environment variables and secret references. If the service points to Postgres, leave its host, database name, user, password reference, and encryption-key configuration intact.
Check for accidental destructive options. docker compose down removes containers and the Compose network, but it does not remove named volumes by default. Adding -v or --volumes explicitly removes volumes declared by the project and can destroy the SQLite database. Review scripts and CI jobs as well as the command you type; an automated cleanup step can be just as destructive as a manual one.
Bind mounts are directories on the host and are not deleted by docker compose down, but pointing the replacement service at a different directory has the same effect as losing the data. Confirm the resolved mount with docker inspect or the rendered Compose configuration before stopping the old container.
Perform the Docker update
The following procedure assumes a Compose project with a service named n8n. Run it from the directory containing the Compose file.
- Record the rollback tag. Write down the image tag currently in use and keep the pre-upgrade database or volume backup accessible.
- Pull the reviewed image. For a pinned release, pull the exact image explicitly:
docker pull docker.n8n.io/n8nio/n8n:<version>In a Compose project,
docker compose pullpulls the image specified by the file. A floating stable or latest tag can be used only when your change policy accepts the possibility that it resolves to a newer build than the one you reviewed. Pinning a version is safer for a controlled production change.Rank #4
Sale
Vaydeer Wrist Rest for Keyboard and Mouse, Computer Ergonomic Wrist Support Pad, Soft Memory Foam Arm Cushion for Desk, Palm Hand Office Laptop Typing- 【Softer and More Comfortable】Vaydeer wrist rest has unique diamond pattern, which is the combination of softness and aesthetics. The materials of wrist rest are improved into higher quality memory foam and covered with silky smooth lycra. The computer wrist rest makes you as comfortable and cushiony as like rest your wrists on clouds.
- 【Ergonomic Wrist Saver】The wrist rests for keyboard and mouse comes with a 17.32×3.15×0.83 inch keyboard wrist pad and a 5.94×3.15×0.83 inch mouse wrist support. Based on ergonomic design, the unique concave shape is the perfect fit for your wrist joints. The wrist rest pad fits most computer keyboards and laptops, improve hand and wrist posture, release your wrist and arm stress.
- 【Non-Slip Rubber Bottom】Featuring an anti-skid silicone base on the bottom, this wrist keyboard support stays firmly in place on your desk, preventing the padding from sliding around, ensuring stable and consistent wrist support during extended computer sessions.
- 【Better Experience & Pain Relief】Our keyboard arm rest is beneficial to alleviate the soreness caused by direct contact and friction between your arm and a hard desk surface, reducing the risk of wrist fatigue or carpal tunnel. The soft texture of memory foam can evenly distribute the pressure around your wrists and provide good support with just enough give.
- 【Helpful in Multiple Scenarios】Whether you're working, studying, writing, typing, gaming, this keyboard and mouse rest combo is an essential accessory to add comfort and support to your hands and wrists. It’s also a great gift for men, women, family, friend, coworker, gamer, teacher, etc.
- Stop and remove the old containers.
docker compose downThis removes the containers and network while leaving named volumes in place unless volume removal was requested. Do not add
-vfor a normal application upgrade.Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy. - Start the new container.
docker compose up -dCompose creates a container from the pulled image, reconnects the preserved volume or database settings, and starts n8n in the background.
- Follow startup logs.
docker compose logs -f n8nWait until startup and any database migration finish. Seeing a migration message is expected when the new n8n version changes the schema. Do not interrupt the process or repeatedly recreate the container while it is migrating.
If you do not use Compose, the equivalent operation is to stop and remove the old container, pull the new image, and run it with exactly the same volume mounts, environment variables, ports, and network settings. Reusing only the image while omitting those runtime settings creates a different installation.
Verify the upgraded instance
Verification should test both the application and the data it needs to operate.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
- Confirm the version. Check the n8n user interface and startup logs to ensure the expected image, rather than an unintended floating-tag build, is running.
- Check the data mount. Confirm that the running container maps the original volume or host directory to
/home/node/.n8n. For Postgres, confirm that the connection points to the existing database. - Open representative workflows. Choose workflows that use different node types, schedules, webhooks, and integrations. Verify that names, active status, nodes, expressions, and execution history are present.
- Test credential decryption. Open or run nodes that use OAuth, API keys, or other stored credentials. A credential error after an otherwise successful startup usually indicates a changed encryption key or a missing n8n data mount.
- Run a safe execution. Use a test input or a non-destructive workflow that writes to a test destination. Check the execution log, node outputs, and any downstream response.
- Check triggers and webhooks. Confirm that the public URL, reverse-proxy routing, scheduled jobs, and webhook registrations still work. A container can be healthy while an omitted environment variable leaves external triggers unusable.
- Review health and security status. Inspect the n8n security audit and instance status. The audit can indicate that the installation is outdated, but it does not replace functional testing of your workflows.
Special cases that need coordinated upgrades
Single container with SQLite
This is the simplest case: preserve /home/node/.n8n, back up the volume, update one image, and validate workflows. SQLite is tied to the persisted directory, so deleting or changing that mount is the principal data-loss risk.
Compose with Postgres
Keep both sides of the deployment consistent: the n8n service must retain its local data directory and encryption settings, and the Postgres service or external database must retain its data volume and connection details. Take the database backup before the image change. Do not combine an n8n upgrade with a Postgres major-version migration unless you have a separate tested plan and rollback path.
Best Value
- 【No Drill Mounted】Cable management tray can be assembled in as little as 3 minutes or less-simply. Side clips easily clampe the edge of desk, pass through the holes on the sides, and secure excess cables with baskets. Desk cable management supports inward or outward installation to meet your needs in different scenarios, and provides you with great convenience when collecting and organizing wires.
- 【Rubber Pad Protects Desk】Wire organizer under desk built-in soft rubber pads on the clamp protect your desk from scratches, so you will not damage your furniture or office.
- 【Sturdy and Beautiful】Cord management under desk is made of high-quality carbon steel and holds about 15 lbs. The wire basket has 2 holes on each side of the tray to enable your cables to pass freely. Cable baskets are suitable for desk thickness use from 0.4" to 2.4".
- 【Space Saving & Keep Organized】Desk cable management tray holds all your power cords, outlet strips, USB hubs and computer transformers hidden from your feet, and the data cables will not enter the vacuum cleaner to keep your desk clean and tidy. Desk wire organizer is also suitable for use in the kitchen and outdoors.
- 【Reduce Safety Risks】Cable tray under desk keeps all plugs away from your kids, no more worry about tripping. Using 2 holes wire tray saves extra space, helps you easily cabling and wire protection. The mesh design is not easy to accumulate dust, but avoids safety accidents caused by messy wires.
Queue mode or a scaled deployment
Queue and scaled installations can include a main process, workers, and runners. Coordinate their image versions rather than upgrading one role in isolation. When external S3 binary storage is enabled, n8n states that main, worker, and runner should be upgraded to the same version at the same time; mismatched versions can create protocol incompatibilities even when the containers appear healthy.
Apply the same configuration and encryption-key settings to every role. Verify that workers can claim jobs, runners can execute code where applicable, and binary data can be read and written from the configured object store.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →How to roll back safely
Rollback is not simply changing the image tag if the new version has already migrated the database. First stop the new containers and inspect the startup logs to determine whether a migration completed. Keep the pre-upgrade backup untouched.
- Stop the upgraded deployment with
docker compose down. - Change the image back to the recorded previous tag.
- Start the previous version with the original mounts and environment variables.
- Test startup and a representative workflow.
- If the older image cannot use the migrated schema, restore the pre-upgrade database or volume backup, then start the previous version against that restored copy.
Restoring a database is destructive to changes made after the backup. When possible, restore the backup to a separate volume or database first and test the rollback there. For a scaled deployment, roll all main, worker, and runner roles back to the same version.
Update approaches compared
| Decision | Option A | Option B | What changes operationally |
|---|---|---|---|
| Database | SQLite in /home/node/.n8n |
External Postgres plus persisted n8n directory | SQLite needs a stopped-volume backup; Postgres needs a consistent database backup and separate database maintenance planning. |
| Container management | Docker Compose | Manual docker run |
Compose preserves a documented set of mounts and variables; manual updates require you to reproduce every runtime option exactly. |
| Image selection | Pinned version tag | Floating stable or latest tag | A pin makes testing and rollback deterministic; a floating tag reduces editing but can introduce an unreviewed build. |
| Backup method | Manual archive or dump before the change | Automated snapshots with restore tests | Manual backups are simple but depend on operator discipline; automated snapshots improve repeatability only when restoration is periodically verified. |
| Topology | One n8n container | Main, workers, and runners | One container can be upgraded as a unit; scaled roles must use coordinated versions, especially with S3 binary storage. |
Troubleshooting after an upgrade
The UI shows a setup wizard or no workflows
The service is probably using an empty or different data location. Stop it, inspect the mount, and compare the volume name or host path with the pre-upgrade Compose file. Reattach the original volume; do not create a new administrator account over the old installation.
Credentials fail to decrypt
Check that the encryption-key environment variable and the persisted /home/node/.n8n directory are unchanged. Restore the original key and restart. If the key was permanently lost, a database restore alone cannot recover the encrypted credential values.
Startup stops during migration
Keep the container running long enough to capture the complete log and avoid repeated restarts. Check available disk space, database connectivity, and the release notes for migration requirements. If the process fails consistently, use the rollback plan and the pre-upgrade backup rather than deleting the database volume.
Workflows exist but webhooks or schedules do not fire
Compare the new container’s environment variables, published ports, reverse-proxy route, timezone, and public URL with the recorded configuration. Then test one webhook and one scheduled workflow independently. A successful database migration does not prove that network or trigger configuration was preserved.
Workers do not process executions
In queue mode, verify that main, worker, and runner images are on the same release, that they share the expected queue and database settings, and that workers can reach Redis or the configured broker. If S3 binary storage is enabled, check object-store credentials and connectivity as well as version alignment.
Quick Recap
Final preflight and post-upgrade checklist
- Release notes and breaking changes reviewed for the target version.
- Current image tag recorded for rollback.
- SQLite volume or Postgres database backed up and the backup location verified.
/home/node/.n8nmount confirmed in the Compose configuration.- Encryption-key setting and all database variables preserved.
- No command or automation step uses
docker compose down -vunintentionally. - Reviewed image pulled, preferably by pinned version.
- Containers recreated with
docker compose pull,docker compose down, anddocker compose up -d. - Logs watched until migrations finish.
- Version, workflows, credentials, a safe execution, webhooks, and schedules verified.
- Scaled main, worker, and runner roles upgraded together where applicable.
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.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Clear out junk files and repair common Windows errors3Scan for outdated or missing drivers - takes under a minute
