What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
The dependable production setup is a Rust Actix Web binary managed by systemd, listening on 127.0.0.1:8080, with Nginx accepting public traffic on ports 80 and 443. Point your domain to the VPS, obtain a Let’s Encrypt certificate with Certbot, and verify both the private application endpoint and the public HTTPS route. Directly exposing Actix or terminating TLS inside Actix is possible, but the reverse-proxy layout is usually easier to operate when you need certificates, redirects, logs, or more than one service.
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
This guide deploys a small Actix Web application on an Ubuntu Linux VPS. The finished request path is:
As an Amazon Associate I earn from qualifying purchases.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →- A browser resolves your domain to the VPS public IP address.
- Nginx listens on TCP ports 80 and 443.
- Nginx forwards application requests to Actix at
127.0.0.1:8080. - systemd starts the Actix binary at boot, restarts it after a failure, and sends its output to the journal.
- UFW permits SSH, HTTP, and HTTPS while leaving the application port private.
Actix Web is an executable HTTP server framework rather than a separate daemon. Your Cargo binary creates routes, constructs an HttpServer, binds a socket, calls run(), and awaits the server future. Actix Web 4’s current getting-started documentation lists Rust 1.72 as the minimum supported Rust version and supports stable toolchains.
No benchmark or VPS price is implied by this deployment recipe. Performance depends on the VPS, application code, database, network, and traffic pattern.
#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.
Prerequisites and decisions
VPS and account requirements
- An Ubuntu VPS with a public IPv4 address (and IPv6 if you intend to publish it).
- A sudo-capable account. Keep a second SSH session available while changing firewall rules.
- A domain name whose DNS records you can edit.
- An SSH client. Ubuntu documents installing
openssh-serverand using key-based authorization; use keys rather than relying on a password-only administrator account.
Choose the socket layout
| Layout | Actix bind address | Public ports | Best fit | Trade-offs |
|---|---|---|---|---|
| Reverse proxy (recommended) | 127.0.0.1:8080 |
Nginx owns 80/443 | One or more web services, automatic certificate handling, redirects, access logs | One additional service to configure and monitor |
| Direct HTTP | 0.0.0.0:8080 or another public port |
Actix owns the chosen port | Private testing or an intentionally public non-TLS endpoint | Clients see the application port; no proxy features; you must handle exposure yourself |
| Direct Actix TLS | Public TLS socket, such as 0.0.0.0:443 |
Actix owns 443 | A single service where you want TLS in the Rust process | Certificate file permissions and renewal become application concerns |
Use 127.0.0.1 whenever a reverse proxy is the public entry point. Use 0.0.0.0 only when external clients are deliberately meant to reach Actix directly. Binding to all interfaces does not by itself configure TLS or a firewall.
1. Connect to the VPS and update Ubuntu
Connect using the account and key you created during VPS provisioning:
ssh your-user@YOUR_SERVER_IPUpdate package metadata and install the compiler prerequisites used by many Rust crates:
sudo apt update
sudo apt upgrade
sudo apt install build-essential pkg-configInstall Rust with rustup, then refresh the toolchain. The installer will ask whether to use the default stable toolchain; accept that choice unless your project has a documented toolchain file.
curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh
rustup update
source "$HOME/.cargo/env"
rustc --version
cargo --versionConfirm that the reported compiler is at least Rust 1.72 for the Actix Web 4 setup described here. A project that pins a newer compiler still takes precedence over the general minimum.
2. Create a minimal Actix application
Create a Cargo binary and enter its directory:
cargo new hello-actix
cd hello-actixReplace the dependencies section in Cargo.toml with:
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Clear out junk files and repair common Windows errors3Fix the driver behind crashes, sound loss and screen glitches[dependencies]
actix-web = "4"Replace src/main.rs with this minimal route and server:
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
use actix_web::{get, App, HttpServer, Responder};
#[get("/")]
async fn index() -> impl Responder {
"Hello from Actix on a VPS"
}
#[actix_web::main]
async fn main() -> std::io::Result<()> {
HttpServer::new(|| App::new().service(index))
.bind(("127.0.0.1", 8080))?
.run()
.await
}The #[get("/")] attribute creates a handler for the root path. App::new().service(index) registers it, bind selects the listening socket, and run().await keeps the asynchronous server alive until shutdown. Add your API routes, static-file service, authentication, and application state to the App factory as the project grows.
3. Compile and smoke-test before daemonizing
Build an optimized release binary:
cargo build --releaseRun it in the foreground for the first check:
./target/release/hello-actixKeep that SSH session open. In a second SSH session on the VPS, request the loopback endpoint:
curl -i http://127.0.0.1:8080/You should receive an HTTP response containing Hello from Actix on a VPS. If the connection is refused, inspect the foreground terminal for a bind error and confirm that the process is still running. Stop the test process with Ctrl+C; production should not depend on an open SSH session.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchWindows 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 reinstall4. Install the binary and create a systemd service
Use a dedicated service account
Do not run a network-facing application as root when it does not need root privileges. Create a system account and an application directory, then copy only the release artifact and files it actually needs:
sudo useradd --system --home /opt/hello-actix --shell /usr/sbin/nologin hello-actix
sudo install -d -o hello-actix -g hello-actix /opt/hello-actix
sudo install -o hello-actix -g hello-actix -m 0755 target/release/hello-actix /opt/hello-actix/hello-actixIf your application reads configuration, place it outside the executable and grant the service account read access only to the required files. Never put private keys or database passwords in the unit file when a more restricted secret mechanism is available.
Create the unit
Create /etc/systemd/system/hello-actix.service:
[Unit]
Description=Hello Actix Web service
After=network-online.target
Wants=network-online.target
[Service]
User=hello-actix
WorkingDirectory=/opt/hello-actix
ExecStart=/opt/hello-actix/hello-actix
Restart=on-failure
Environment=RUST_LOG=info
[Install]
WantedBy=multi-user.targetRestart=on-failure handles an unexpected process exit. The RUST_LOG environment variable is useful when the application initializes an Actix-compatible logger; otherwise, add the logging initialization in Rust before relying on it.
Enable, inspect, and follow logs
sudo systemctl daemon-reload
sudo systemctl enable --now hello-actix
sudo systemctl status hello-actix
journalctl -u hello-actix -fRun the loopback curl test again while systemd owns the process. To deploy a new binary, copy it into the same path and restart the unit:
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →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)
sudo systemctl restart hello-actix
sudo systemctl status hello-actixActix’s server future runs until shutdown; systemd supplies boot-time startup, supervision, and a persistent place to inspect standard output and errors.
5. Lock down the host with UFW
UFW is Ubuntu’s default firewall frontend and is disabled initially. Preserve SSH before enabling it, or you can lock yourself out:
sudo ufw allow OpenSSH
sudo ufw allow 80/tcp
sudo ufw allow 443/tcp
sudo ufw enable
sudo ufw status verboseWith Nginx forwarding to loopback, do not add a public rule for TCP 8080. Keep a second SSH connection open until ufw status verbose confirms the intended rules and you have tested the service. If your SSH daemon uses a nonstandard port, allow that port instead of the OpenSSH application profile.
6. Install Nginx and proxy the application
Install the reverse proxy:
sudo apt install nginxCreate a server block for the hostname you will use. The following HTTP-only block is sufficient to test routing before requesting a certificate:
server {
listen 80;
server_name example.com www.example.com;
location / {
proxy_pass http://127.0.0.1:8080;
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;
}
}Save the block in the distribution’s enabled-site layout, disable the default site if it would otherwise answer the same hostname, and validate before reloading:
sudo nginx -t
sudo systemctl reload nginxThe forwarded headers preserve the original host, client address, proxy chain, and scheme for frameworks or application logs that use them. Configure your application to trust forwarded headers only from your own proxy; accepting them blindly from direct clients can make logged addresses and security decisions unreliable.
7. Point DNS at the VPS
Create an A record for example.com pointing to the VPS IPv4 address and, if you publish IPv6, an AAAA record pointing to the VPS IPv6 address. Add www only if it appears in the Nginx server_name and in the certificate request. DNS changes can take time to appear according to the record’s TTL.
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
Before requesting HTTPS, verify that the hostname reaches this machine and that TCP port 80 is reachable from the public internet. A request to the raw IP can select a different Nginx server block, so test the hostname:
curl -I http://example.com/8. Obtain and maintain HTTPS with Certbot
Use the Nginx integration
Ubuntu documents Certbot as the automated path for Let’s Encrypt certificates. Install the snap package and request certificates for every hostname Nginx serves:
sudo snap install --classic certbot
sudo certbot --nginx -d example.com -d www.example.comCertbot may update the Nginx configuration to serve HTTPS and can offer an HTTP-to-HTTPS redirect. Choose the redirect if every public request should use TLS; if you need an exception for a separate HTTP endpoint, inspect the generated configuration before accepting a blanket redirect.
Let’s Encrypt certificates are valid for 90 days. Certbot installs a systemd renewal timer that attempts renewal twice daily, so check that the timer is active and perform a safe renewal simulation:
Free tools Windows power users keep installed
One-click scans. No signup required.
sudo systemctl status snap.certbot.renew.timer
sudo certbot renew --dry-runA dry run tests the renewal path without replacing the live certificate. Renewal still requires the validation method to work: the HTTP-01 challenge needs the hostname to resolve to this VPS and port 80 to be reachable.
Alternative: terminate TLS in Actix
Actix Web also supports direct HTTP/TLS operation. Its documentation recommends rustls for new applications and documents HTTP/2 when TLS is configured. Enable the rustls feature appropriate to the Actix Web version in your Cargo.toml, load the PEM certificate and private key, build the rustls server configuration, and bind with the matching API, such as bind_rustls_0_23 for the rustls 0.23 integration.
Direct TLS removes Nginx from the request path but makes your Rust process responsible for reading certificate files, reloading after renewal, and protecting the private key. It is a reasonable design for one service when you have an explicit certificate-reload plan. Nginx is generally simpler when several services share ports 80 and 443 or when you need mature proxy access logs and routing.
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.
| Concern | Nginx terminates TLS | Actix terminates TLS |
|---|---|---|
| Certificate lifecycle | Certbot’s Nginx integration can install and renew certificates at the proxy | Your deployment must make renewed PEM files visible and reload the Rust process safely |
| Application exposure | Actix stays on loopback; only Nginx is public | Actix owns the public TLS socket |
| HTTP/2 | Handled by the TLS-enabled proxy | Available when Actix’s TLS configuration enables it |
| Multiple services | One 80/443 listener can route to several upstreams | Each service needs its own address or an additional front end |
| Operational focus | Separate proxy and application logs and restart domains | Fewer processes, but certificate and proxy concerns live in the application deployment |
9. Verify every layer
Run checks from the VPS and, for the public checks, from a network outside the server:
curl -i http://127.0.0.1:8080/
curl -I http://example.com/
curl -I https://example.com/
sudo systemctl status hello-actix nginx
sudo ufw status verbose
journalctl -u hello-actix --no-pager -n 100- The loopback request proves the Actix process is listening and serving the route.
- The HTTP hostname request proves DNS, port 80, and Nginx routing. If you selected an HTTPS-only policy, it should return the redirect you configured.
- The HTTPS request proves the certificate and TLS listener are reachable. Inspect the certificate’s hostname and expiration date in a browser or with your TLS inspection tool.
- The systemd and journal checks reveal crashes, permission errors, missing files, and bind failures.
- The UFW output confirms that administrative access and only the intended public ports are allowed.
Common failures and targeted fixes
“Connection refused” on 127.0.0.1:8080
Check sudo systemctl status hello-actix and journalctl -u hello-actix -n 100. A process that exited, a typo in ExecStart, a missing dynamic dependency, or a different bind port will produce this symptom. Confirm the binary exists and is executable as the service user:
sudo -u hello-actix /opt/hello-actix/hello-actixStop that foreground test with Ctrl+C, then correct the unit and restart it.
Nginx returns 502 Bad Gateway
Nginx cannot reach its upstream. Confirm Actix is running on exactly 127.0.0.1:8080, test the endpoint locally, and inspect the Nginx error log. If Actix was changed to bind another address or port, update either the Rust configuration or proxy_pass; do not open a firewall port merely to mask a mismatch.
The domain shows the wrong site
Check the domain’s A and AAAA records, wait for DNS caches to expire, and verify the requested hostname exactly matches the Nginx server_name. An old AAAA record can send IPv6 clients to a different host even while IPv4 tests appear correct.
Certbot cannot complete the challenge
HTTP-01 validation needs public DNS pointing to this VPS and inbound TCP 80. Confirm the UFW rule, cloud-provider firewall, Nginx listener, and hostname resolution. A closed port, stale DNS record, or another service answering port 80 prevents validation.
The service fails after reboot
Use systemctl is-enabled hello-actix, inspect the unit’s After=network-online.target relationship, and read the journal from the failed boot. Verify that all files under /opt/hello-actix are readable by hello-actix and that configuration paths are absolute rather than dependent on an interactive shell.
Updating the application safely
Build the new revision in a separate checkout or release directory, run its local smoke test, and replace the deployed binary only after a successful release build. Then restart and verify the service:
cargo build --release
sudo install -o hello-actix -g hello-actix -m 0755 target/release/hello-actix /opt/hello-actix/hello-actix
sudo systemctl restart hello-actix
sudo systemctl is-active hello-actix
curl -i http://127.0.0.1:8080/For a larger application, add a health route that checks only process readiness, not an expensive external dependency, and use it during deployments. Keep the previous binary available until the new process has passed the loopback and public checks so that a quick rollback is possible.
Recommended Free Tools
Operational checklist
- Use a current stable Rust toolchain compatible with your chosen Actix Web release.
- Keep the Actix socket on loopback when Nginx is public.
- Run the binary as a non-root account under systemd.
- Review the journal after every deployment and on every unexpected restart.
- Allow SSH before enabling UFW; expose only the ports your topology needs.
- Keep DNS records, Nginx hostnames, and certificate names aligned.
- Test Certbot renewal with
certbot renew --dry-runand monitor the renewal timer. - Protect certificate private keys and grant the smallest practical file permissions.
- Recheck version-sensitive Actix rustls feature names and Ubuntu packaging instructions when upgrading.
When to choose each deployment model
Choose Nginx in front of Actix for the general internet-facing case: it keeps the Rust service private, centralizes ports 80 and 443, and fits Certbot’s documented integration. Choose direct Actix TLS when you intentionally want one Rust process to own HTTPS and have a tested plan for certificate permissions, renewal, and reloads. Choose direct HTTP only for controlled environments where exposing a non-TLS Actix port is deliberate; it is not a substitute for HTTPS on a public site.
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.
