overview for justawittyusername

Nuclear fusion reaction releases almost twice the energy put in in c/news

[–] justawittyusername 9 points 9 months ago

We need to make sure we knot it at the joins so it doesn’t get accidentally disconnected.

Do you guys know about slowerpace? I'm in love with his music. in c/vaporwave

[–] justawittyusername 1 points 9 months ago

Yep! But not that album. Ill check it out thanks!

Hosting websites over 4g in c/selfhosted

[–] justawittyusername 2 points 9 months ago

Thanks thats good to know! I have got onto tailscale and have a test lab setup with a digital ocean vps for the public IP(exit node) and a ubuntu machine with a tunnel to it. Its working, just need to translate that to pfsense...

Why would I need backlit keys anyway? in c/memes

[–] justawittyusername 3 points 9 months ago

I just wish they wrote the function key text in a bright colour so I can see it in low light…

Hosting websites over 4g in c/selfhosted

[–] justawittyusername 4 points 10 months ago (1 children)

Good question, I will want to host more in the future, im trying to keep costs as low as possible.

16

Hosting websites over 4g (self.selfhosted)

submitted 10 months ago* (last edited 10 months ago) by justawittyusername to c/selfhosted

16 comments fedilink

I have been hosting a few websites from my home server and it has taught me a lot. I have recently had major issues with the electrical storms, Kogan NBN support (Australia), and the NBN network in general. I know 4g is not fast, but I would like to use it so that in the event of a network outage, im not at the mercy of NBN. On to the question!

I run pfsense in hyper v with a 4 port nic which passes through those ports to pfsense.

I realized that 4g ip addresses are not public, which stops me from hosting the websites.

Reading into wireguard and vpn services my plan is to:

Set up a VPS ✅
Set up wireguard on the VPS ✅
Create a wireguard connection on my windows server, and pass that in as an interface to pfsense, so that hopefully, I wont need to change to much on my internal infrastructure.

Does this sound like an OK plan? I'm open to any other ideas where I can achieve the following:

web app >> nginx >> pfsense >> vpn tunnel >> VPS with Public IP (can be dynamic)

Thanks!---

What are you doing?! I'm posting on the post page, you compost heap! in c/mildlyinfuriating