dataprolet
@dataprolet@lemmy.dbzer0.com
Formerly know as u/Arjab. Anarchist | Antifascist | Anticapitalist Arch Linux | FOSS | Piracy | Security & Privacy
- Comment on lightweight blog ? 1 week ago:
Not sure how lightweight it needs to be, but I use Ghost and it’s pretty simple and basic.
- Comment on Release v1.130.0 · immich-app/immich 1 week ago:
An initial library scan with 19k assets: 1m40s down to 9 seconds.
Insane!
- Comment on GrapheneOS partial offline backup? 1 week ago:
If you can’t type a twelve word passphrase, nobody can help you…
- Comment on Law is a maximally complex representation of reality manifested by anxiety. 5 weeks ago:
Law is not a representation of reality. Reality form law.
- Comment on Local domains constantly time out according to Uptime-Kuma 4 months ago:
It’s HTTPS, what else should it be, when I monitor a domain?
- Comment on Local domains constantly time out according to Uptime-Kuma 4 months ago:
What do you mean by tracker? I’m monitoring local domains, that point to local services and their respective web interfaces like Proxmox or Nextcloud. The local domains have a wildcard SSL certificate via DuckDNS.
- Comment on Local domains constantly time out according to Uptime-Kuma 4 months ago:
Yep
- Comment on Local domains constantly time out according to Uptime-Kuma 4 months ago:
Yes, Uptime-Kuma is running on the same domain as the other services, except the Nginx-Proxy-Manager, which runs on a VPS which I access via WireGuard. And yes, I’m using Docker. I tried curl’ing one of the domains from the Uptime-Kuma container and got the folllowing error:
curl: (35) OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to service.datenprolet.duckdns.org:443. So thanks, now I have an idea about what I should investigate. - Submitted 4 months ago to selfhosted@lemmy.world | 11 comments