What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
The most dependable beginner setup is n8n running in Docker with a persistent volume mounted at /home/node/.n8n. Start with a Manual Trigger, prove the workflow with test data, then switch to a schedule or public webhook only after timezone, HTTPS, credentials, and persistence are correct.
Antihost offers VPS plans with one-click n8n, NVMe storage and a 14-day free trial.
What you need before installing n8n
n8n connects applications that expose APIs and lets you manipulate their data with little or no code. Self-hosting puts the editor, execution process, credentials, and workflow database on infrastructure you control. That is useful for always-on automations and inbound webhooks, but it also makes you responsible for storage, updates, networking, backups, and access control.
As an Amazon Associate I earn from qualifying purchases.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Repair Windows errors before they cause bigger problems3Scan for outdated or missing drivers - takes under a minuteChoose where the server will run
| Setup | Best for | Important limitation |
|---|---|---|
| Local computer with Docker Desktop | Learning, prototyping, and testing workflows manually | A local machine may sleep or change networks, so it is not a dependable home for always-on jobs or inbound webhooks. |
| Headless Linux server | Scheduled jobs and integrations that must run continuously | You must administer Docker, HTTPS, backups, updates, and firewall access. |
| VPS or private server | Public webhooks and remote access | The server needs a reachable hostname, HTTPS, adequate resources, and a recovery plan. |
For a local learning instance, Docker Desktop is acceptable. For a headless Linux host, install Docker Engine and Docker Compose v2. The current n8n Compose sandbox documentation lists at least 4 GB of RAM and 2 vCPUs for that stack. Treat that as a baseline for the documented sandbox configuration, not a universal capacity guarantee: workload size, execution concurrency, binary data, and database choice can require more.
Decide whether the endpoint should be private or public
http://localhost:5678 is the normal local endpoint when Docker maps host port 5678 to the container. It is suitable for learning on the same machine. A webhook called by a service on the internet cannot reach your laptop’s localhost address. For that use case, place n8n on a server with a public hostname and configure HTTPS and a reverse proxy correctly. Do not activate a production webhook until an external request can reach that server.
#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.
Why Docker and persistence are the beginner defaults
n8n recommends Docker for most self-hosting needs. The image packages the application and its runtime, while Docker’s volume mechanism keeps n8n’s state outside the disposable container. Without that volume, removing or recreating the container can remove workflows, credentials, and other instance data.
Mount a named Docker volume at /home/node/.n8n. The official image uses this directory for the SQLite database, webhook URL, and encryption key. Preserving the directory preserves your work between restarts. Back up both the volume’s contents and the encryption key; a database backup without the key may not allow encrypted credentials to be recovered.
Recommended Free Tools
SQLite or PostgreSQL?
| Database | Role in a first deployment | When to consider it |
|---|---|---|
| SQLite | Default for a small, single n8n instance | Learning, personal automation, and modest workloads where a separate database service is unnecessary. |
| PostgreSQL | Documented production-oriented alternative | Deployments that need a more production-focused database architecture and the operational discipline to run and back it up. |
Changing databases is an operational migration, not a setting to toggle casually. Begin with the default only when its single-instance scope matches your needs, and plan the database, backup, and restore process before the workflow becomes business-critical.
Start a persistent n8n container with Docker
1. Create the data volume
Run this once on the Docker host:
docker volume create n8n_dataThe named volume is the durable location that will be mounted into the container.
2. Launch the official image
The following command is the official beginner pattern. Replace both timezone placeholders with the same valid timezone identifier for the server or the schedule you intend to use.
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
docker run -it --rm
--name n8n
-p 5678:5678
-e GENERIC_TIMEZONE="<YOUR_TIMEZONE>"
-e TZ="<YOUR_TIMEZONE>"
-e N8N_ENFORCE_SETTINGS_FILE_PERMISSIONS=true
-e N8N_RUNNERS_ENABLED=true
-v n8n_data:/home/node/.n8n
n8nio/n8n-p 5678:5678maps the host’s port 5678 to n8n’s editor port.-v n8n_data:/home/node/.n8nattaches the persistent volume to n8n’s state directory.GENERIC_TIMEZONEis used by schedule-oriented nodes;TZsets the container timezone. Set both deliberately.N8N_ENFORCE_SETTINGS_FILE_PERMISSIONS=trueenables the documented settings-file permission behavior.N8N_RUNNERS_ENABLED=trueenables the runner setting shown in the official example.--rmremoves the stopped container. That is safe only because the n8n data is in the named volume; it does not make the volume disposable.
The first run downloads the image, creates the container, maps the port, and starts n8n in the foreground. Keep that terminal open while learning. If you stop it, start the same command again; the named volume should bring back the instance data.
Free tools Windows power users keep installed
One-click scans. No signup required.
3. Use Docker Compose for a repeatable server
docker run is the quickest experiment. Compose is easier to reproduce, review, extend, and restart on a server. Create a project directory, place the documented n8n Compose configuration there, and keep secrets in a local .env file that is excluded from version control. Start it with:
docker compose up -dAfter the service starts, check the local health endpoint:
curl -sf http://localhost:5678/healthzA successful command confirms that the host can reach the n8n health endpoint. If it fails, inspect container status and logs before troubleshooting the workflow itself. A stopped container, an incorrect port mapping, or a service bound only to a different interface must be fixed at the deployment layer.
Open n8n and complete first-run setup
Local installation
- Open
http://localhost:5678in a browser on the Docker host. - Complete the first-run owner-account setup.
- Only after the owner account exists, add credentials for external services.
On a remote server, use the configured hostname and HTTPS endpoint instead of localhost. Keep the editor restricted to the people who need administrative access. A public webhook endpoint and a public editor are different exposure decisions; do not expose the administrative interface merely because an integration needs to send webhook requests.
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)
Build a safe first workflow
Use a workflow that cannot be called unexpectedly while you learn. The simplest useful exercise is:
Manual Trigger → Edit Fields (Set) → optional HTTP Request1. Add a Manual Trigger
Create a new workflow and add the Manual Trigger node. This trigger runs only when you explicitly execute the workflow from the editor, so it is safer than starting with a public webhook or a schedule.
2. Add an Edit Fields (Set) node
Connect an Edit Fields (Set) node to the trigger. Enter one or two test values, such as a text field and a number. Keep the first payload small; the aim is to see how one node’s output becomes the next node’s input.
3. Execute and inspect each node
- Click Execute Workflow.
- Open the Manual Trigger output and confirm that the run started.
- Open the Edit Fields output and verify that your test values are present and have the expected types.
- Correct the node before moving on if a field is missing, renamed, or mapped to the wrong value.
n8n’s editor shows execution data and provides a data-mapping interface. Drag fields from the input pane into later node parameters, or generate an expression in the editor. Inspect the resulting value rather than assuming that a visually similar field name points to the intended item.
4. Add an HTTP Request only after the first two nodes work
An HTTP Request node can send the test data to a public test endpoint, but it introduces another failure surface: URL, method, request body, response status, and authentication. Add it after the trigger and transformation execute successfully. If it needs credentials, create them in n8n’s credentials area. Do not paste secrets into expressions or workflow text.
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
Move from manual testing to an active trigger
Do not activate a production trigger until the manual path is understood and its outputs are correct. Replace the Manual Trigger according to the job you are automating.
Scheduled work: Schedule Trigger
Use a Schedule Trigger for recurring jobs. Confirm GENERIC_TIMEZONE before judging whether a run happened at the right local time. A container’s host timezone and the schedule node’s configured timezone are not assumptions to leave implicit; set the environment variables deliberately and test one interval before relying on a daily or monthly schedule.
Inbound requests: Webhook
A Webhook trigger requires a server address that the calling service can reach. Localhost works for local testing, not for an internet service. For a public endpoint:
- Use a public hostname that resolves to the server.
- Terminate traffic with HTTPS through an appropriately configured reverse proxy.
- Confirm that the proxy forwards the webhook request to n8n and preserves the path and method.
- Keep the editor and administrative endpoints restricted even when the webhook itself is public.
- Send a real test request from outside the server’s network before activating the workflow.
Activation is a deliberate production change. Test the production URL, payload shape, authentication, and expected response first; otherwise a trigger that appears configured may never receive a request.
Application-specific triggers
App triggers follow the same sequence: create the required credential, select the event, run a controlled test, inspect the incoming item, map its fields, and activate only after the path is repeatable. The exact event and credential fields depend on the application, so validate the payload in the execution view rather than designing expressions from an assumption.
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.
Debug failed or missing executions
When a run fails, open the Executions view and inspect the status, the failing node, its input, and its output. n8n’s execution tools allow a failed execution to be retried with the currently saved workflow or with the original workflow. Choose deliberately: retrying the saved version tests your current fix, while retrying the original reproduces the version that actually failed.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →Webhook never fires
- Local-only address: Replace localhost with a publicly reachable hostname for external callers.
- Workflow inactive: Activate the workflow after testing the production path.
- HTTPS or proxy error: Check TLS termination, forwarding, hostname resolution, and firewall rules.
- Wrong URL or method: Compare the caller’s request with the webhook path and expected method in n8n.
- Container unavailable: Verify that the Compose service or container is running and that port 5678 is mapped as intended.
Schedule runs at the wrong time
- Check the values of both
TZandGENERIC_TIMEZONE. - Confirm the schedule node’s interval and saved workflow version.
- Run a short test interval before switching to the desired production cadence.
Credentials or mapped fields fail
- Confirm that the credential exists in the owner-configured instance and is selected in the node.
- Inspect the previous node’s actual output item; do not rely on a guessed field path.
- Use the data-mapping UI to insert the field or expression, then execute the node again.
- Keep secrets in n8n credentials rather than in expressions, text fields, or exported workflow content.
Workflows disappear after a restart
Check the container’s volume mapping first. It must mount the named volume at /home/node/.n8n. If the container was started without that mount, the instance may have written its database and encryption material into disposable container storage. Recreate it with the persistent volume and establish backups before continuing.
Protect and maintain a self-hosted instance
Back up the state that makes recovery possible
Back up the Docker volume and the encryption key together. The volume contains the SQLite database and instance settings, while the key is required to decrypt protected credentials. Test that a backup can be restored on a separate test instance; a backup that has never been restored is an assumption, not a recovery plan.
Limit exposure
- Use HTTPS for any public access.
- Restrict the editor and administrative endpoints to trusted users or networks.
- Expose only the webhook paths that an integration needs.
- Keep secrets out of shell history, source control, expressions, and workflow text.
- Apply operating-system, Docker, and n8n updates through a controlled maintenance process.
Run the n8n security audit
After the workflow works, run n8n audit, or use the API or n8n audit node. The audit reports unused credentials, risky or community nodes, filesystem access, unprotected webhooks, missing security settings, and findings related to an outdated instance. Treat each finding as a review item: remove what is unused, protect what is exposed, and update only after checking compatibility and backup recovery.
Deployment choices at a glance
| Decision | Beginner choice | Reason |
|---|---|---|
| Local versus public | Localhost for learning; VPS or private server for always-on work | Inbound webhooks need a reachable server address, while localhost is simplest for manual practice. |
| Docker run versus Compose | Docker run for a first experiment; Compose for a repeatable server | The one-line command is quick, while Compose is easier to reproduce and extend. |
| Manual versus event trigger | Manual Trigger first | It prevents unexpected calls while you inspect node outputs and mappings. |
| Temporary versus persistent data | Named volume at /home/node/.n8n |
It preserves workflows, credentials, the database, webhook URL, and encryption key across container replacement. |
| SQLite versus PostgreSQL | SQLite for a small single instance; PostgreSQL for a production-oriented architecture | The default keeps a first deployment simple; PostgreSQL is the documented alternative when operational needs justify it. |
A practical first-day checklist
- Docker Engine and Docker Compose v2 are installed on the host.
- The host meets the documented Compose sandbox baseline of 4 GB RAM and 2 vCPUs.
- A named volume is mounted at
/home/node/.n8n. TZandGENERIC_TIMEZONEare set intentionally.- The editor opens at
http://localhost:5678locally, or at the configured HTTPS hostname remotely. - The owner account is created before credentials are added.
- A Manual Trigger and Edit Fields (Set) workflow executes successfully.
- Each node’s output has been inspected and mapped values are visible.
- Any HTTP Request uses n8n credentials rather than embedded secrets.
- A scheduled or webhook trigger has been tested on its real production path before activation.
- The health endpoint responds with
curl -sf http://localhost:5678/healthzon a Compose host. - The volume and encryption key have a tested backup.
- The security audit has been run and its findings reviewed.
What a successful first workflow looks like
A sound first deployment is intentionally unexciting: Docker starts n8n, the named volume survives a restart, the owner account can open the editor, a Manual Trigger creates an execution, Edit Fields produces the expected test item, and an optional HTTP Request succeeds only after the earlier nodes are verified. Once that path is dependable, replace the manual trigger with a timezone-tested schedule or a publicly reachable HTTPS webhook, then monitor executions and maintain backups as part of normal server administration.
Quick Recap
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.
