Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Freelance · nginx

Freelance Linux server administrator who runs his own production servers

I am one senior engineer who administers Ubuntu servers and nginx for live products, because I run my own. TaxiDex runs on Linux with nginx doing TLS, caching and security headers, and my company site is served by nginx under a strict Content-Security-Policy. I work remotely, by the project or month by month.

Who hires a freelance nginx engineer?

  • Companies whose server was set up once by someone who left and has not been looked at since.
  • Founders who need a site or API put behind nginx with working TLS and sensible security headers.
  • Teams without an ops person who want one senior engineer to own the server, the deploys and the checks after them.

What do I do with nginx?

  • nginx in front of appsTLS, caching and security headers in front of a Node.js API, a Next.js portal and a static site, configured to match what runs behind them.
  • Strict security headersMy own company site ships a strict Content-Security-Policy, and I test everything I release against the live headers, not only a local preview.
  • HardeningHardening with fail2ban, a strict CSP and TLS settings on the Ubuntu servers I run day to day.
  • Process management beside nginxPM2 keeps the Node.js processes up while nginx proxies to them, with ports and timeouts that agree with each other.
  • Monitoring and error reportingA watchdog tests the services every five minutes and Sentry reports application errors, so I hear about a failure first.
  • Self-hosted mail and toolsI also host the mail stack (Postfix, Dovecot, rspamd with DKIM, SPF and DMARC) and my business tools on the same kind of servers.

Which nginx problems am I usually called in for?

  • nginx shows 502 in front of a Node.js app

    The process is down or listens where nginx is not looking. The logs say which before I touch the configuration.

    The step-by-step fix
  • Requests end in a 504 gateway timeout

    A slow upstream outlasts the proxy timeout, and the right fix is usually in the slow part, not the timeout.

    The step-by-step fix
  • Live connections close after sixty seconds

    The proxy treats an idle WebSocket as finished and closes it.

    The step-by-step fix
  • Browsers distrust the certificate

    An intermediate certificate is missing from the chain, so some clients fail while others pass.

    The step-by-step fix
  • The certificate did not renew

    A renewal that worked for months stops after a change nobody connected to it.

    The step-by-step fix
  • The server is under constant login attempts

    Brute-force traffic fills the logs, and the fix is to block it, not just to ignore it.

    The step-by-step fix

How does working with me on nginx work?

  1. Send the log lines and the configThe error log lines around the failure and the nginx site config. I reply within 24 hours.
  2. A call on the setupA call within 48 hours covering what sits behind nginx and how traffic reaches it.
  3. Scope in writingHardening, headers or migration, written down in order of risk.
  4. Work in two-week sprintsKickoff is typically inside two weeks, and each sprint closes with a change checked on the live server.
  5. Test before reloadEvery production change starts with a backup and a rollback I have tested, then I check the site after the reload.

What do people ask about nginx work?

Do you manage servers monthly or only by the project?

Either. A one-off hardening or migration is a project, and ongoing care is available as a monthly plan.

Which Linux do you use?

Ubuntu, which is what I run day to day.

Can you move a site to a new server?

Yes. I take a backup first, build and test the new server, switch over and keep the way back until the live system checks out.

Do you also write the application?

Yes, I build the APIs and apps as well, so a server problem is traced into the code when needed.

Why do I get a 504 from nginx?

The app behind nginx did not answer in time. I wrote a fix page on 504 timeouts: find the slow request instead of only raising the timeout.

Proof

Products I built with nginx

All projects

Own product · Taxi dispatch SaaS

TaxiDex

My own multi-tenant taxi dispatch SaaS: API, dispatcher portal, driver and passenger apps, and the servers underneath.

TypeScriptNode.jsAdonisJSNext.js

Company website · Static generator

stegnor.com

My company site: 804 pages from a Python and Jinja generator, with 15 free browser tools.

PythonJinjaYAMLMarkdown

Next step

Need a senior nginx engineer?

A discovery call within 48 hours, and a kickoff typically inside two weeks.