I managed to fix this problem by pointing my domain name to my private IP address (with pihole’s local DNS entries), so I could access it. Then, I just got certs for the domain and applied them with nginx.
I managed to fix this problem by pointing my domain name to my private IP address (with pihole’s local DNS entries), so I could access it. Then, I just got certs for the domain and applied them with nginx.
I know, but for some reason my router does not let me access my domain (with duckdns) when connected to my network. So even if I get certs for the domain, I will not be able to access it. I have set up local DNS entries (with Pi-Hole) to point to my srrver, but I don’t know if it possible to get certs for that, since it is not a real domain.
EDIT: Fixed it. (See reply for fix)
So, OP has 45.57 gold medals only for his first torrent on the list?
I am waiting for my medal
Yes, basically on internal LAN I put admin admin to everything.
I wish I could like a comment twice on Lemmy.
I just use ext4 on everything. It works pretty nicely.
I think you can encrypt drives by using a key stored in the TPM, if you have one. See the Arch wiki for info.
Though I have heard the TPM is not as secure..
Doesn’t Signal also require a phone number?
OK, WhatsApp is owned by Meta and it is proprietary, but why not Telegram?
I’d rather not. :)
Yes, I have little bandwidth so I always download low bitrate ones.
I don’t have any job that needs to run 24/7, so I poweroff my server at night (12 am) and start it in the morning using WOL.
OK, maybe I will think about some other use for the Raspberry Pi then.
Maybe, but I my router is not hackable and I don’t plan on buying one that is.
While trying to set up the WLAN, I couldn’t connect to the AP, it said no internet access, and I couldn’t connect to the Pi, or ping any device from it.
The Privilege Escalation hits hard