Read the changelogs from 1.5.3 to 1.5.5 and see if you need to take additional steps
ngircd has the concept of a global password. Distribute this password and you’ve got a simple psk based acl mechanism
what error message are you getting?
It all depends on what you do with the box, how the applications you run utilize the cpu (single vs multithreaded/multiprocess but also stuff like cpu cache utilization. if you profile the workload that you want to run (see if its cpu, memory or io bound for instance) will help you in figuring out what works best for you.
Have a look at mailcow if you’re new to MTA’s. Use that and a (sub)domain to figure out how to set things up. Once youre satisfied with the setup, reconfigure your domain on the new MTA. Use a mailclient with $yourformat and imap support to import your old email.
And above all, dont be discouraged by the naysayers that think its an impossible task; Its not, but it is complicated to get right bc all the parts involved ;-)
So what research did you already do? If you didnt, its better to ask some account or sales person this question…
Ask your engineers to configure a local mta that authenticates and forwards all mail. Next, reconfigure all apps.
Ask your engineers to configure a local mta that authenticates and forwards all mail. Next, reconfigure all apps.
Hard to say without proper info
If you want to forward an ssh connection over an existing ssh connection, ProxyJump is the way to go.
This. You need to tune the zfs memory, esp if the box is shared with other applications.
They have some pointers in their documentation: https://webmin.com/faq/
you need to reconfigure webmin to serve you a wss:// url towards that websocket. The second S in wss stands for securitah! :)
Definetely! In your case I would get a vps from somewhere and host from there. Cloudflare is not going to work around your power issues. Some caching CDN might, but that would make the service read-only
Mja, business decisions are up to you and your clients. This sub is about selfhosting, so you can expect answers that are about, well, selfhosting ;-)
For me, selfhosting is about selfhosting. Using 3rd party options hosted by someone else is not selfhosting by its very definition. A reverse proxy works, and you can trivially use that to host a gazillion websites on the same ip+port due to the magic of a ‘virtual host’
Objectively you reduce your attack surface if you actually self-host wireguard, since you dont control 3rd party products, and cannot give any guarantees wrt their security.
Unpopular opinion, yes, but security > convenience ;-)
Start by reading what DNS can do. Good luck!
You will be in for a surprise once you learn about tcpdump ;-) Welcome to internet hosting!