Make my IPv6 selfhosted service available on IPv4 network.

SteveTech , 24 days ago

If you can't get the VPS to work, alternatively there's Cloudflare but last I checked streaming was a little out of their free terms. With it, you should just have to set your AAAA record and make the cloud orange, that way Cloudflare will proxy it, and IPv4 will work. There's also Cloudflare tunnels which lets you host websites without port forwarding anything.

Decronym Bot , 24 days ago (edited 23 days ago)

Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I've seen in this thread:

Fewer Letters	More Letters
HTTP	Hypertext Transfer Protocol, the Web
HTTPS	HTTP over SSL
IP	Internet Protocol
SSL	Secure Sockets Layer, for transparent encryption
VPS	Virtual Private Server (opposed to shared hosting)
nginx	Popular HTTP server

---

[Thread #778 for this sub, first seen 1st Jun 2024, 14:35]
[FAQ] [Full list] [Contact] [Source code]

Albbi , 24 days ago

Holy shit that's a great bot!

exu , 24 days ago

You'll want to install a reverse proxy of your choice on the VPS. Have clients access it over ipv4 and configure it to proxy pass it to your ipv6 address. Nginx at least is capable of doing ipv4 & ipv6 -> ipv4, I think the inverse should also be possible.

Gobo , 24 days ago

Setup nginx as a v6 to v4 reverse proxy. Or the inverse if you have a public v4 in a vpc to use as a dmz.

slazer2au , 24 days ago

I'd say running the VPS as a proxy or nat64 setup would be the way to go. Cgnat kinda messes everything up.

smileyhead OP , 24 days ago

What I want to do. But the question is how?

VPS as a proxy... but when I point A record to VPS and AAAA record to server in my home, how would the VPS know which traffic to pass and how.

mhzawadi , 24 days ago

A and AAAA records can have different IPs, the VPS will know it's the host for your A and to forward AAAA to your home IP

TCB13 , 24 days ago (edited 23 days ago)

how would the VPS know which traffic to pass and how.

Install nginx in your VPS and configure it as reverse proxy to your home IPv6:

server {
    listen 80; # listens only on IPv4 port 80
    server_name example.com; # your domain name
    location / {
        proxy_pass http://[2a03:2880:f003:c07:face:b00c::2] # replace with your home server IPv6. Keep the brackets.
        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_redirect off;
    }
}

Point your A record to your VPS, and your AAAA to the home server.

---

• Security recommendation about X-Real-IP: https://lemmy.world/comment/10392284
• Once your setup works, try to increase your security by using SSL / disabling plain HTTP: https://lemmy.world/comment/10398545

i_am_not_a_robot , 24 days ago

Be careful with doing this. X-Real-IP and X-Forwarded-For are good for when the client is a trusted proxy, but can be easily faked if you don't whitelist who's allowed to use those headers. Somebody with IPv6 access could send "X-Real-IP: 127.0.0.1" or something and if the server believes it then you'll see 127.0.0.1 in logs and depending on what you're running the user may gain special permissions.

Also be careful with the opposite problem. If your server doesn't trust the proxy, it will show the VPS IP in logs, and if you're running something like fail2ban you'll end up blocking your VPS and then nobody will be able to connect over IPv4.

TCB13 , 24 days ago (edited 24 days ago)

Fair enough yeah. :)

The OP can solve that potential security issue with this option: https://nginx.org/en/docs/http/ngx_http_realip_module.html#set_real_ip_from on the local server nginx:

http {
(...)
        real_ip_header    X-Real-IP;
        set_real_ip_from  [2a03::aaaac::1]; # Replace with the VPS IPv6 address.
}

This will make sure only the VPS is allowed to override the real IP.