Someone: “… the new php vulnerability”
Me: “wait what, another one?”
S: “Yes”
I had exposed services for years, never a problem. I don’t have time to be on top of all of this. Im going random high port wireguard access only.
Random high port will not make you any more secure.
You can use a tool like shodan or censys to quickly get a list of IP:ports with PHP <8.0.
Wireguard is UDP only. A UDP service doesn’t have to answer invalid requests and Wireguard doesn’t, unless you present the right key. This means it’s basically impossible to tell an open port from one where no service is listening.
Depends on your firewall though. If you have a “default deny” then the random wireguard port will not send a RST package while the closed ports will. But UDP only sends a few RSTs per second so if you do a UDP-portscan, most systems will only send RSTs for the first few ports and then stop. If you scan very slowly you can find a wireguard port, but you can still not know it is wireguard, just that the port is actually open.
Reject is good for internal rules, but externally you should use drop all the time
If you had told me 30 years ago that PHP would be responsible for billions of dollars of losses, I would have said, “I TOLD YOU SO!” Haven’t run it since I was forced to write it, the worst thing I’ve ever written in.
Why a random high port? Wireguard doesn’t respond on its port unless it gets its “handshake”, so acts as stealth.
Because im trying to be cool.
But serious. If ever a wireguard vulnerability is found, which I is not very probable and a terrifying prospect, the default port will be the main target.
I use 443 udp, less public networks block it.
also you can be very edgy, e.g. 42069 or 57007 (0xDEAF)
I was a heavy stoner for years… I used 51420.
Funny is that once I forgot I configured that port and took me some hours of debugging to find out. :(
I’m on the fence. I have auto updates on, I have my services routed through Cloudflare’s proxy (besides Jellyfin) with rules blocking any connection from outside of my country, all running as rootless containers, all passing every security scan I’ve thrown at them… But I still have a sinking feeling something’s gonna bite me.
But I really like being able to share links or connect without faffing with a VPN…
If you’re using cloudflare tunnels, you might consider using mTLS, which effectively blocks (or provides a challenge, depending on how you configure your WAF rules) anything without your mTLS. The catch is that generally, apps need to support mTLS themselves, although this is not the case for browser based access.
I get that. I have my Nextcloud locked down pretty good. It’s my only public facing service. But even with an A+ on Nextcloud’s security scan and best practices on everything else, it still makes me a bit uncomfortable. Anything else goes over Wireguard. Everyone has a different level of comfort I guess. I’m a fairly careful individual when it comes to unrelated non-tech life decisions too. Some things just don’t belong on the web… or in an AI infested operating system.
Every solution has its pros and cons. If you rely on something that requires public access (like randomly sharing access with others) than this is not a solution for you. With that said, you can go hybrid, anything high risk that you will never share with others (or only with a few predefined set of people that you can share a VPN config with) can go behind a VPN, anything you intend to share with others stays public but goes into a VM on a separate VLAN with restricted access to stuff to minimize the blast radius should sh*t go down. Personally this is what I’m trying to do, most things have been moved behind VPNs, only a few things remain public and I’m slowly moving them to separate VMs in a restricted network.
What made me change:
I can know that there is a php bug. But I still need for nextcloud to patch/update.
Same here, for quite a while. There is no reason for my NextCloud server to be exposed on the public internet. I still have access to it from everything via Tailscale and it works perfectly.
same here more or less, at home nothing is open anymore, everything goes through tailscale and a raspberry pi that also does the wake on lan for the big pc when I need it. the only thing exposed is a hetzner vps with a small browser game, and there I keep it boring, ufw with just 80 and 443 (and rtmp for a stream relay), caddy in front, the node app and postgres only reachable from inside the box. I guess that’s the trade off that works for me, whatever strangers need to reach lives on one machine I watch closely, the rest stays behind the vpn
I already do this but I get nervus still with this second php thingy. Knock on wood that wireguard vulnerabities are not going to come into the thing.
Wireguard was actively designed to have fewer vulns. There’s very little configuration available which dramatically reduces the number of scenarios a developer needs to consider when writing software. There are surely issues because no piece of software is perfect, but that was at least a stated design goal.
Wireguard is a relatively speaking new technology compared to PHP. Less legacy code to worry about.
I do not doubt there will/are vulnerabilities for it, but with any luck they will be few and far between with quick patches
Everything everywhere all at once, AI will be there to take away everything.
Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I’ve seen in this thread:
Fewer Letters More Letters Git Popular version control system, primarily for code SSH Secure Shell for remote terminal access TLS Transport Layer Security, supersedes SSL UDP User Datagram Protocol, for real-time communications VPN Virtual Private Network nginx Popular HTTP server
6 acronyms in this thread; the most compressed thread commented on today has 8 acronyms.
[Thread #173 for this comm, first seen 20th Nov 2026, 11:40] [FAQ] [Full list] [Contact] [Source code]
The keycloak/java one is a big deal since it was used to get into a few places.
Thanks god I’m not using any public-facing PHP applications anymore.
I fear this will eventually become the only way to safely selfhost for pretty much everyone. :/
It has always been the safest way to host private apps.
I don’t mean WG specifically (although that’s a great method) but I think everybody should be using some second layer that’s enforced on a different level from the app itself: mTLS, OAuth, basic auth in the reverse proxy, even some geoblocking, anything.
would you keep your doors unlocked and open 24/7? no? then why would you expose your server publicly?
This doesn’t make any sense lol
I only keep my server in a air tight safe, nothing in or out. It’s the only way.
an open port is to an open door as an unsecured port is to an unlocked door.
if you open your unsecured ports to the internet you’re telling anyone “walking” by that they can “come on in” and to “take or do anything” that they want to.
No? Thats not quite how it works.
you do realize why ports are called ports, right?
The term port in networking derives from the Latin words porta, meaning “gate,” and portus, meaning “harbor.” This reflects the concept of ports as entry and exit points for data, similar to how a harbor serves as a docking point for ships.
now tell me…what would you call a door on a house? a way…a gate…a gateway…oh yeah, a port of entry and exit!
go back to networking 101.
Give it a rest Donny, you’re out of your element.
Your rudimentary understanding of networking and security that exist only in the abrstact aren’t fooling anyone.
small words coming from a schlub on a selfhosting community that has failed to provide anything other than a blunted wit.
Are you referring to yourself here?
to provide services???
With the recent nginx vulns I was just thinking about all the docker containers that are sitting there with a test webpage on an ancient version of nginx. I went and nuked all my test containers to reduce attack surface. But also sticking with VPN or Tailscale.
I’ve been doing this since I set up remote access. Nobody else should ever be using this but me, so why bother exposing anything?
Writing iptables isn’t even that hard
I’m honestly considering this for some of my small business customers too, expose their services other than their standard websites on high ports, that way it’s generally only expected business contacts who will be making connections to those services.
AI has so many customers flapping about security at the moment.





