hosting all on my own (currently a WIP)

[cult_status18]

so I found this video guide here and im going to be using it to host myself you can actually set it all up on most PC's but I'm going to be using a raspberry pi since I wont need that much RAM and it will need to stay running 24/7 so mabey don't try using your personal computer for this unless it stays on all day and night and your fine with replacing thermal paste and all that stuff also make sure you have acssess to you internet provider and all the passwords for that I will add what router I use when I get the chance I will also be using Linux but windows should work just fine

You can download the latest version of Apache here

I'm still figuring this all out and I'm waiting for a Raspberry Pi rn so I won't make much progress until then

[brisray]

There's lots of reasons to not run your own server. There's a lot to learn and take care of but even after 20+ years, I still get a kick out of knowing I own and run a tiny bit of the internet.

Good luck!

[rina]

There's lots of reasons to not run your own server. There's a lot to learn and take care of but even after 20+ years, I still get a kick out of knowing I own and run a tiny bit of the internet.

Good luck!

well the ISP issues including "you agree to not host" and CG-nat can be bypassed with a hybrid system, where a very cheap VPS acts as a reverse=tunnel. that way no ports are directly open on your own network. however, it is still a good practice to completely isolate the computer you're using. meaning firewalling it so only outbound port is 22 (or whatever else you pick for yhe ssh), as well as complete network isolation through vlans. so it cant communicate with your other devices in your network. with this setup, in theory, to your ISP's system it will look like you're communicating with some remote server, which is completely permited.

unless you're absolutely sure what you're doing, however, i'd advise against doing this. hosting your own stuff is cool, until you get hacked. and unless you've secured your stuff properly, there is always a risk. "who will hack me tho", you may ask, but the sad reality is there are countless of botnets constantly probing any server they can find on the internet.

[crazyroostereye]

well the ISP issues including "you agree to not host" and CG-nat can be bypassed with a hybrid system, where a very cheap VPS acts as a reverse=tunnel. that way no ports are directly open on your own network. however, it is still a good practice to completely isolate the computer you're using. meaning firewalling it so only outbound port is 22 (or whatever else you pick for yhe ssh), as well as complete network isolation through vlans. so it cant communicate with your other devices in your network. with this setup, in theory, to your ISP's system it will look like you're communicating with some remote server, which is completely permited.

unless you're absolutely sure what you're doing, however, i'd advise against doing this. hosting your own stuff is cool, until you get hacked. and unless you've secured your stuff properly, there is always a risk. "who will hack me tho", you may ask, but the sad reality is there are countless of botnets constantly probing any server they can find on the in

Can only agree with this, security is important. While I would say hosting only a Static Website with a modern Web server and exposing that, would be fairly Safe, ignoring (D)DOS Attacks. My better Recommendation is to just run a VPS (Virtual Privat Server) for Services that have to run in the Open Web and everything else keep it locked in your Home Net and use a VPN (Virtual Private Network) if you have to reach it from the Outside.