nginx
TrialTools
A web server and reverse proxy commonly used to terminate TLS and route traffic.
Why it's here
Placed in Trial: 5 article(s) of evidence from 1 source(s), led by open-source activity, with 4 in the last 30 days. Confidence 46%.
Evidence (5)
- 4Hacker News·10/4/2026open_sourceSelf-hosted HTTP tunnels using SSH and Nginx
The article describes a self-hosted way to expose a local web service over the internet using only OpenSSH and Nginx. It uses SSH remote port forwarding to allocate an external port, then Nginx proxies a wildcard subdomain to that port and adds basic access control with secure_link and HTTP basic authentication.
- 4Hacker News·9/28/2026open_sourceHijacking PS5 Twitch RTMP Streams via DNS
The author describes redirecting PlayStation 5 broadcast streams away from Twitch by spoofing DNS responses for Twitch ingest domains. By pointing the PS5 at a local server running dnsmasq and nginx-rtmp, they were able to receive the console’s RTMP stream on a Mac without using a capture card.
- 4Hacker News·9/27/2026open_sourceUsing Custom Domains for Go Package Imports
The article argues that Go projects should avoid using a Git hosting domain directly in import paths, because it ties package URLs to a specific provider such as GitHub or GitLab. It recommends serving Go import metadata from a custom domain so repositories can move between hosts without changing import statements.
- 5Hacker News·9/13/2026securityTesla scan traffic accidentally targets NTP Pool server
A server operator reported receiving thousands of security scan requests that appeared to originate from Assetnote hosts and used Tesla-related hostnames, including pool-ntp.tesla.com. The operator traced the issue to Tesla's CNAME for an NTP Pool domain and concluded that active asset discovery likely treated external NTP Pool member servers as Tesla-owned assets. Tesla and the scanning vendor were contacted, and the issue was later marked resolved.
- 4Hacker News·7/9/2026open_sourceUsing split-horizon DNS and public CAs for internal TLS
The article argues that internal services can use public-domain names with split-horizon DNS instead of private TLDs and self-signed certificates. It demonstrates a setup using NetBird for DNS routing, acme.sh with Let’s Encrypt for certificate issuance, and nginx as a reverse proxy/WAF to keep internal services protected while maintaining trusted TLS.