How to Run Multiple Node.js Apps on One Domain with Nginx

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 Linux VPS plans with full root access, unlimited traffic on a 1 Gbps port and a 14-day free trial.

Run each Node.js application on its own localhost port, then let NGINX listen on ports 80 and 443 and reverse-proxy requests to the correct port. Use URL prefixes such as example.com/app1/ and example.com/app2/ when one hostname should expose several applications; use separate subdomains and server_name blocks when each application should behave as if it owns the root path.

How the architecture works

A single public domain does not require a single Node.js process. NGINX is the public entry point and traffic director:

#	Preview	Product	Price
1		Compressed Air Duster,130000RPM Super Power Cordless Air Duster,Rechargeable Brushless Blower,3 Gear...	$21.59	Buy on Amazon
2		EVEO® Screen Cleaner Spray Kit (Streak-Free) TV Screen Cleaner for Smart TV, Lcd, LEd, Oled |...	$15.97	Buy on Amazon
3		BladeHawks RGB Gaming Mouse Pad Extra Large Extended 31.5x12 Inch-Black	$14.99	Buy on Amazon
4		Vaydeer Wrist Rest for Keyboard and Mouse, Computer Ergonomic Wrist Support Pad, Soft Memory Foam...	$15.99	Buy on Amazon
5		Under Desk Cable Management Tray No Drill, Metal Mesh Cable Management Under Desk with Clamp Mount,...	$13.99	Buy on Amazon

• NGINX accepts HTTP and HTTPS traffic on ports 80 and 443.
• Each Node.js app listens on a different private port, such as 127.0.0.1:3001 and 127.0.0.1:3002.
• NGINX matches the hostname or URL path and forwards the request to the appropriate local port.
• NGINX can terminate TLS, redirect HTTP to HTTPS, add forwarding headers, and handle WebSocket upgrades.

The Node listeners should normally bind to localhost rather than a public interface. That prevents users from bypassing NGINX and reaching an application without its TLS, routing, logging, or access-control layer.

There are two routing designs:

NGINX chooses the longest matching prefix when several prefix locations match. This makes specific locations such as /app1/api/ take precedence over a broader /app1/ location, provided the configuration is written deliberately.

#1 Best Overall

Sale

Compressed Air Duster,130000RPM Super Power Cordless Air Duster,Rechargeable Brushless Blower,3 Gear Adjustable Blower with LED Light,Dust Remover for Computer/House/Outdoor/Car

• 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.

$21.59

Buy on Amazon

Choose paths or subdomains before configuring NGINX

When URL paths are the better fit

• You want one canonical hostname for users, bookmarks, and an existing site.
• The applications are logically sections of one product, such as a dashboard and an API.
• You can configure each frontend, API router, cookie, and asset URL to understand its prefix.
• You prefer one certificate and one DNS record for the public entry point.

Path routing is convenient, but the prefix becomes part of every browser-visible URL. A frontend that emits /assets/main.js instead of /app1/assets/main.js will request the wrong application. Client-side routers, API calls, redirects, cookie paths, service workers, and absolute links all need review.

When subdomains are the better fit

• Each application already expects to run at / and should not be changed.
• The applications have independent teams, deployments, cookies, or security policies.
• Users benefit from clear hostnames such as api.example.com and admin.example.com.
• You can create DNS records and obtain certificates for every hostname.

Subdomains avoid most prefix-aware routing work. In exchange, you must manage DNS, certificate coverage, cross-origin requests, and cookie scope. A cookie scoped to app1.example.com is not automatically sent to app2.example.com; a cookie scoped to .example.com is shared more broadly and therefore deserves stricter security review.

Prepare the server and Node.js applications

Install the required components

You need a Linux server, a DNS name pointed at it, NGINX, Node.js, and a process supervisor. Package-manager commands vary by distribution, so use the supported NGINX and Node.js packages for your operating system. Confirm the components before changing the proxy:

nginx -v
node --version
npm --version
sudo systemctl status nginx

Open only ports 80 and 443 in the firewall. The application ports do not need public firewall rules when the apps listen on 127.0.0.1.

Give every app a distinct listener and environment

Configure one port per application. For example, app 1 uses 3001 and app 2 uses 3002:

PORT=3001 node /srv/app1/app.js
PORT=3002 node /srv/app2/app.js

Use separate working directories, environment files, log files, and deployment identities where practical. Each application should handle graceful shutdown and report startup failures clearly; otherwise NGINX will return gateway errors while the underlying process is stopped.

Rank #2

EVEO® Screen Cleaner Spray Kit (Streak-Free) TV Screen Cleaner for Smart TV, Lcd, LEd, Oled | Computer Screen Cleaner Spray and Wipe Microfiber Cloth - TV, Monitor, Laptop, iPad, Car - 6.7oz 1 Pack

• 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

$15.97

Buy on Amazon

Make the application proxy-aware

Applications commonly need to trust the proxy for the original protocol and client address. In an Express application, for example, configure the framework’s proxy-trust setting according to your network topology, then use the forwarded protocol and host when generating redirects. Do not blindly trust arbitrary forwarding headers if the app can also be reached directly from an untrusted network.

For a path-mounted app, configure the frontend build and server-side router with its public base URL. A browser request to /app1/ should result in asset, API, and client-side navigation URLs that retain /app1/. If the app cannot be configured this way, a subdomain is usually safer than trying to patch every generated URL at the proxy.

Configure path-based routing on one domain

The following example sends /app1/ to port 3001 and /app2/ to port 3002. The upstream names keep backend definitions separate from the public locations.

http {
    upstream app1_backend {
        server 127.0.0.1:3001;
    }

    upstream app2_backend {
        server 127.0.0.1:3002;
    }

    map $http_upgrade $connection_upgrade {
        default upgrade;
        ''      close;
    }

    server {
        listen 80;
        server_name example.com;

        location = /app1 {
            return 301 /app1/;
        }

        location /app1/ {
            proxy_http_version 1.1;
            proxy_set_header Host $host;
            proxy_set_header X-Real-IP $remote_addr;
            proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
            proxy_set_header X-Forwarded-Proto $scheme;
            proxy_set_header Upgrade $http_upgrade;
            proxy_set_header Connection $connection_upgrade;
            proxy_pass http://app1_backend/;
        }

        location = /app2 {
            return 301 /app2/;
        }

        location /app2/ {
            proxy_http_version 1.1;
            proxy_set_header Host $host;
            proxy_set_header X-Real-IP $remote_addr;
            proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
            proxy_set_header X-Forwarded-Proto $scheme;
            proxy_set_header Upgrade $http_upgrade;
            proxy_set_header Connection $connection_upgrade;
            proxy_pass http://app2_backend/;
        }
    }
}

Why the trailing slash in proxy_pass matters

In location /app1/, the directive proxy_pass http://app1_backend/; includes a URI, namely /. NGINX replaces the part of the request URI that matched the location. Therefore, a client request for /app1/orders/42 reaches app 1 as /orders/42.

If you write proxy_pass http://app1_backend; without the trailing slash, NGINX forwards the original URI, so the backend receives /app1/orders/42. Choose the behavior that matches the application’s router. Do not change the slash casually: it is a common cause of unexpected 404 responses and duplicated prefixes.

Handle the prefix inside the application

With the configuration above, the backend sees root-relative paths such as /orders/42. The application still needs to generate browser-facing URLs with /app1 when users access it through the public domain. Typical fixes include setting a framework base path, configuring the frontend’s public path, setting a router basename, and ensuring redirects include the prefix. Test hard-coded links, form actions, CSS URLs, JavaScript chunks, images, favicon requests, API calls, and WebSocket endpoints.

Rank #3

BladeHawks RGB Gaming Mouse Pad Extra Large Extended 31.5x12 Inch-Black

• 【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.

$14.99

Buy on Amazon

Prevent prefix collisions

Reserve each prefix and document it. A broad location / for a main site can coexist with location /app1/ because the longer prefix wins. Avoid overlapping prefixes such as /app and /app1 unless you have tested every edge case; use clear names and exact redirects for the prefix without its trailing slash.

Configure subdomains with separate server blocks

For app1.example.com and app2.example.com, create DNS records pointing both names to the NGINX server. Then use one server block per hostname:

http {
    upstream app1_backend {
        server 127.0.0.1:3001;
    }

    upstream app2_backend {
        server 127.0.0.1:3002;
    }

    server {
        listen 80;
        server_name app1.example.com;

        location / {
            proxy_http_version 1.1;
            proxy_set_header Host $host;
            proxy_set_header X-Real-IP $remote_addr;
            proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
            proxy_set_header X-Forwarded-Proto $scheme;
            proxy_set_header Upgrade $http_upgrade;
            proxy_set_header Connection $connection_upgrade;
            proxy_pass http://app1_backend;
        }
    }

    server {
        listen 80;
        server_name app2.example.com;

        location / {
            proxy_http_version 1.1;
            proxy_set_header Host $host;
            proxy_set_header X-Real-IP $remote_addr;
            proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
            proxy_set_header X-Forwarded-Proto $scheme;
            proxy_set_header Upgrade $http_upgrade;
            proxy_set_header Connection $connection_upgrade;
            proxy_pass http://app2_backend;
        }
    }
}

When the location is simply /, omitting a URI in proxy_pass preserves the full request path. Both applications can therefore receive /, /login, and other root-relative routes exactly as they do when run alone.

The map block used for WebSockets must be declared in the http context, above the server blocks. If you do not need WebSockets, the upgrade headers can be omitted; retaining them is harmless when the application handles ordinary HTTP requests correctly.

Add HTTPS and redirect HTTP

Terminate TLS at NGINX. Obtain a certificate covering the public hostname or hostnames, then use an HTTP server only for the redirect:

server {
    listen 80;
    server_name example.com;
    return 301 https://$host$request_uri;
}

server {
    listen 443 ssl;
    server_name example.com;

    ssl_certificate     /etc/letsencrypt/live/example.com/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/example.com/privkey.pem;

    location /app1/ {
        proxy_http_version 1.1;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection $connection_upgrade;
        proxy_pass http://app1_backend/;
    }

    location /app2/ {
        proxy_http_version 1.1;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection $connection_upgrade;
        proxy_pass http://app2_backend/;
    }
}

For subdomains, create corresponding HTTPS blocks and ensure the certificate includes app1.example.com and app2.example.com. A wildcard certificate can cover a matching subdomain pattern, but it does not cover the bare domain unless that name is also included.

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.

$15.99

Buy on Amazon

Forward X-Forwarded-Proto so the application knows that the user connected with HTTPS. Without it, an app may issue an HTTP redirect from an already secure request, creating redirect loops or insecure absolute links.

Run and supervise the Node.js processes

Use a process supervisor

Do not rely on an interactive SSH session. A supervisor should start each app at boot, restart it after an unexpected exit, retain separate logs, and apply the correct environment variables. PM2 is one option:

pm2 start /srv/app1/app.js --name app1 --env production
pm2 start /srv/app2/app.js --name app2 --env production
pm2 save
pm2 startup

Follow the command printed by pm2 startup to register the boot-time service. Keep app names distinct so status, restart, and log commands target the intended process.

Use one process per app when isolation is the priority

One supervised process per application makes memory limits, deployments, logs, and failures easier to understand. A crash in app 1 does not require restarting app 2. This model is often the simplest starting point for several unrelated services on one host.

Use cluster mode for CPU scaling

PM2 can start multiple workers for one application:

pm2 start /srv/app1/app.js -i max --name app1

The built-in load balancer distributes networked Node.js applications across available CPUs without application-code changes. Cluster mode is suitable only when the app is safe to run statelessly across workers. Store sessions, rate-limit counters, background-job state, and other shared data in an external store or use another persistence strategy. In-memory sessions can send a user to a worker that does not contain the session created by another worker.

Best Value

Sale

Under Desk Cable Management Tray No Drill, Metal Mesh Cable Management Under Desk with Clamp Mount, 2 Hole Cable Tray with Wire Management and Cord Organizer for Home Office Standing Desk

• 【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.

$13.99

Buy on Amazon

Use named upstreams for multiple backend instances

A named upstream can contain more than one server. NGINX uses round-robin distribution by default:

upstream app1_backend {
    server 127.0.0.1:3001;
    server 127.0.0.1:3002;
}

server {
    listen 443 ssl;
    server_name app1.example.com;

    location / {
        proxy_pass http://app1_backend;
    }
}

Do not place unrelated applications in the same upstream. Every server listed in one upstream must serve the same application and be able to handle any request that reaches it. If a worker depends on local files, local sessions, or local uploads, make that state shared or use a persistence mechanism before distributing traffic.

With path routing, create a separate upstream for each public app. With subdomains, each server block points to its own upstream. This keeps scaling decisions independent: app 1 might need four workers while app 2 remains a single process.

Support WebSockets and long-lived connections

WebSocket handshakes require HTTP/1.1 and the Upgrade and Connection headers. The map and proxy headers shown earlier support both ordinary HTTP requests and upgrades. Test the actual WebSocket URL through the public hostname, not only against localhost.

NGINX’s default proxy read timeout may close an idle long-lived connection. Increase proxy_read_timeout only when the application’s protocol requires it:

location /app1/ {
    proxy_http_version 1.1;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection $connection_upgrade;
    proxy_read_timeout 300s;
    proxy_pass http://app1_backend/;
}

A long timeout consumes connection capacity for longer, so do not use an arbitrarily large value for every location. Prefer application-level ping messages when the protocol supports them.

Validate, reload, and monitor the deployment

1. Check the syntax before applying a change: sudo nginx -t. Do not reload if this reports an error.
2. Reload without dropping existing connections: sudo systemctl reload nginx.
3. Confirm both Node processes are listening only where intended: ss -ltnp | grep -E '3001|3002'.
4. Test each public path or hostname: curl -I https://example.com/app1/, curl -I https://example.com/app2/, or the corresponding subdomain URLs.
5. Test the prefix without its trailing slash and verify it redirects to the slash form.
6. Open browser developer tools and check HTML, JavaScript, CSS, image, API, redirect, cookie, and WebSocket requests.
7. Inspect NGINX’s error log and the matching application’s log when a request fails.

A successful nginx -t proves syntax, not application behavior. A 502 response usually means NGINX cannot connect to the configured port, the process has stopped, or a local firewall or socket permission prevents access. A 404 can indicate an incorrect proxy_pass slash, a router that still expects the prefix, or an application route that does not exist. A redirect loop commonly indicates that the app is unaware TLS was terminated at NGINX or that X-Forwarded-Proto is missing.

Troubleshoot the common failure modes

Security and operational practices

• Bind Node.js to 127.0.0.1 unless another network exposure is intentional.
• Expose only ports 80 and 443 publicly, with administrative access restricted separately.
• Run applications as a non-root user and give each process only the filesystem permissions it needs.
• Keep secrets in the supervisor or deployment environment rather than in a public repository or NGINX configuration committed to source control.
• Use separate access and error logs, and include the hostname or application name in log paths when several services share a machine.
• Set request size, buffering, and timeout values according to the application instead of copying large limits to every location.
• Reload NGINX only after syntax validation, and keep a known-good configuration available for rollback.
• Monitor disk space, memory, CPU, process restarts, upstream errors, certificate expiry, and log growth.

Path routing versus subdomains: a practical decision

Choose path routing when a single origin and compact URL structure outweigh the work of making every application prefix-aware. Choose subdomains when independent applications already assume root-relative URLs, need separate ownership, or have different release and security boundaries. Neither design increases the number of public listeners: one NGINX instance can route dozens of hostnames and paths to private Node.js ports.

Start with separate localhost ports and explicit upstreams even if you expect to scale later. That separation lets you move from one process to several workers, or from one server to multiple backend instances, without changing the public URL contract. Once routing works, add TLS, process supervision, health checks, and WebSocket testing as separate, verifiable changes.

Quick Recap

SaleBestseller No. 1

Compressed Air Duster,130000RPM Super Power Cordless Air Duster,Rechargeable Brushless Blower,3 Gear Adjustable Blower with LED Light,Dust Remover for Computer/House/Outdoor/Car

$21.59

Bestseller No. 2

EVEO® Screen Cleaner Spray Kit (Streak-Free) TV Screen Cleaner for Smart TV, Lcd, LEd, Oled | Computer Screen Cleaner Spray and Wipe Microfiber Cloth - TV, Monitor, Laptop, iPad, Car - 6.7oz 1 Pack

$15.97

Bestseller No. 3

BladeHawks RGB Gaming Mouse Pad Extra Large Extended 31.5x12 Inch-Black

$14.99

SaleBestseller No. 4

Vaydeer Wrist Rest for Keyboard and Mouse, Computer Ergonomic Wrist Support Pad, Soft Memory Foam Arm Cushion for Desk, Palm Hand Office Laptop Typing

$15.99

SaleBestseller No. 5

Under Desk Cable Management Tray No Drill, Metal Mesh Cable Management Under Desk with Clamp Mount, 2 Hole Cable Tray with Wire Management and Cord Organizer for Home Office Standing Desk

$13.99

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.