These are some quick n' dirty instructions so people can get up and running fast.

I wish I had known this was possible sooner.

Instructions:

Check that your VPN supports port forwarding and you have it enabled.

Grab your VPN's internal IP with ip a

Find the interface for your VPN. For me it's called tun0.

Open up /etc/nginx/nginx.conf

You can back it up, or comment everything out, or pick what's necessary. Here's what my file looks like.

	worker_processes  1;
	include modules.d/*.conf;

	events {
		worker_connections  1024;
	}
	http {
		server {
			listen [VPN INTERNAL IP]:[VPN FORWARDED PORT];
			server_name  localhost;
			location / {
				root '[ABSOLUTE PATH TO YOUR WEBSITE ROOT FOLDER]';
				index index.html; # Relative to your website root.
			}
		}
	}

Make sure your permissions are correct. For me, the 'other' group needs read permissions to the root folder, including where it's mounted.

Start nginx with systemctl start nginx

You can visit your website on your host machine in a browser at [VPN INTERNAL IP]:[VPN FORWADED PORT]. For me, using the internal IP is required to view the website on my host machine.

To view the website on other machines, you can use [VPN EXTERNAL IP]:[VPN FORWARDED PORT]. The only thing you need to change is the IP address.

I hope this works for you and you are inspired to selfhost and take back power from those who stole it from us.

you are viewing a single comment's thread
view the rest of the comments
[–] [S] 16 points 1 year ago (18 children)

Thanks.

It's my understanding that https provides encryption for the data sent between you and the server. If you're not sending any sensitive data, then the encryption shouldn't be necessary.

Don't get me wrong, encryption is great even when it isn't necessary. For my demonstration purposes though, I chose not to include it.

I also believe it's possible to set up HTTPS encryption without a domain name, but it might result in that "we can't verify the authenticity of this website" warning in web browsers due to using a self-signed certificate.

  • source
  • parent
  • hideshow 18 child comments
  • [–] 19 points 1 year ago* (last edited 1 year ago) (1 child)

    Let's Encrypt are rolling out IP-based certs, you may wanna follow its development. I'm not sure if it could be used for your forwarded VPN port, but it'd be nice anyhow

    Edit: I believe encryption helps prevent tampering the data between the server and user too. It should prevent for example, someone MITM the connection and injecting malicious content that tells the user to download malware

  • source
  • parent
  • hideshow 1 child comment
  • [–] 18 points 1 year ago (1 child)

    That is a pretty bad take as all data is sensitive. Https also provides integrity to prevent man in the middle attacks.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 3 points 1 year ago

    You can pickup a cheap domain from gen.xyz. The cheapest domain is $0.99 which is pretty affordable especially since you probably are already paying for a internet connection.

    Once you have the domain you can point it to your IP and then set port 443 on that address to point to Caddy. On Caddy you can either configure it as a server or use it as a reverse proxy to point to something else.

    Security wise I would put all of this on its own vlan with ACLs to control access. If that sounds confusing start with https.

  • source
  • parent
  • [–] 5 points 1 year ago (2 children)

    It takes two seconds to get https and 10 bucks a year for a domain. Come on

  • source
  • parent
  • hideshow 2 child comments
  • [–] 3 points 1 year ago

    but it is sensitive data. the webserver can send executable code to the web browser. if it does not that doesn't matter, what matters is that it can be inserted by a middleman. It's not like there's a dedicated person needed to do that, it can just happen automatically.

  • source
  • parent
  • [–] 1 point 1 year ago (2 children)

    I also believe it's possible to set up HTTPS encryption without a domain name, but it might result in that "we can't verify the authenticity of this website" warning in web browsers due to using a self-signed certificate.

    Just create your own rootCA and IntermediateCA and sign your certificate with those, put the CA in your trust store of your system and get rid of this self-signed warning on every device and happily access all your service via: *.home.lab or whater ever local domain pleases you.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 3 points 1 year ago (1 child)

    I'm not installing OP's CA cert just to view his blog.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 1 point 1 year ago

    Fair point ! Yeah sure if you host a blog online it doesn't make sense... But if you only self-host your services for family and some friends and access them over VPN, a local CA is actually a privacy respecting choice.

    Hosting something on the web (specially self-hosted) without the propre software and hardware is a bad idea in the first place anyway !

  • source
  • parent
  • [–] 1 point 1 year ago (3 children)

    It's my understanding that https provides encryption for the data sent between you and the server. If you're not sending any sensitive data, then the encryption shouldn't be necessary.

    As others have pointed out, everything can be sensitive. If I’m self hosting nextcloud instance with chat that under British law should check for age… self hosting is now sensitive.

    In addition to that, without a secure connection you’re stuck with HTTP/1.1 from 1999 instead of the modern 2 or 3 versions.

    I also believe it's possible to set up HTTPS encryption without a domain name, but it might result in that "we can't verify the authenticity of this website" warning in web browsers due to using a self-signed certificate.

    You can: https://letsencrypt.org/2025/07/01/issuing-our-first-ip-address-certificate

  • source
  • parent
  • hideshow 3 child comments
  • [–] 1 point 1 year ago (2 children)

    In addition to that, without a secure connection you’re stuck with HTTP/1.1

    That's not entirely true. A lot of requests, even with https, are send over HTTP/1.1. And this is kinda mind blowing that in 2025 we still rely on something so old and insecure...

    Same goes with SMS and the old SS7 protocol from 1970... 2FA SMS is probably the most insecure way to get access to your bank account or what ever service promotes 2FA sms login.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 1 point 1 year ago

    Does that contradict what I said? Sure, HTTP 1 is still widely used, but without TLS you can’t use anything else.

    For SMS we don’t have a choice, but if you configure your own web server you do have a choice.

  • source
  • parent
  • [–] 0 points 1 year ago

    Anyone with the ability to inject or modify packets in the network path between server and client can inject malicious javascript or browser exploits into an unencrypted HTTP TCP stream. The client's User-Agent and other headers would allow the attacker to customize their attack to target that specific browser version, and compromise the client machine.

  • source
  • parent