dataprolet

joined 2 years ago
MODERATOR OF
[–] [email protected] 16 points 3 weeks ago

This is also true for DivestOS as a whole.

[–] [email protected] 4 points 3 weeks ago

And now do it without Google.

[–] [email protected] 2 points 3 weeks ago

AudioRelay?

[–] [email protected] 0 points 1 month ago (1 children)

Ever heard of socialist Zionism, dumbo?

[–] [email protected] 23 points 1 month ago (25 children)

"Journalists flock to yet another proprietary, commercial platform as the last becomes increasingly 'toxic' for reasons unknown."

[–] [email protected] 1 points 2 months ago

After changing the MTU to 1200 I have no timeouts anymore, but a lot of read ECONNRESET errors. -.-

[–] [email protected] 1 points 2 months ago

I just changed the Docker's MTU to 1200 and will observe the change.

[–] [email protected] 2 points 2 months ago (3 children)

So the MTU of Tailscale is actually 1280, but is the connection even going through the VPN or rather through my VPS, when Uptime-Kuma is trying to connect to my local domain?

[–] [email protected] 2 points 2 months ago

Thanks, since I access my home network and server through the public IPv4 of a VPS via Tailscale this could actually be the issue. I'll look into it, when I find the time.

[–] [email protected] 1 points 2 months ago* (last edited 2 months ago)

Not sure how this helps, but here you go.

[–] [email protected] 1 points 2 months ago

Yeah, I suspect it's simply an issue on the side of DuckDNS. :/

[–] [email protected] 1 points 2 months ago (6 children)

Yeah, it works fine through my browser. Sometimes the websites load a little longer. I feel like it's an issue with DuckDNS as it's seemingly random when it works and when not.

IPv6 doesn't work:

docker exec -it Uptime-Kuma curl -6 proxmox.datenprolet.duckdns.org
curl: (6) Could not resolve host: proxmox.datenprolet.duckdns.org

Besides that the issue has disappeares since last night. I automatically restart all containers at night and moved from uptime-kuma:1 to uptime-kuma:latest. That shouldn't make a difference, but maybe it did?

And it's not a typo in my config, but in my post. But good catch. ;)

16
submitted 2 months ago* (last edited 2 months ago) by [email protected] to c/[email protected]
 

I followed this tutorial to set up local domain names with SSL-certificates using DuckDNS: https://notthebe.ee/blog/easy-ssl-in-homelab-dns01/

I have three local domains for my Nginx Proxy Manager running on a VPS, for my self-hosted Nextcloud and my Proxmox-WebGUI both running on my local Homeserver. They follow the scheme service.dataprolet.duckdns.org.

Now I use Uptime-Kuma to monitor my services including the three domains and for some reason those three domains constantly time out after 48 seconds. I already set up the retries to 3, but to no avail.

I also use Pi-hole and Unbound and thought, that might be an issue, but testing my DNS using dig, mtr, traceroute, nslookup and host all returned normal values and no errors.

Does anybody have any idea what could cause this? I'm kind of clueless at this point. Thanks in advance!

EDIT: I don't get it.

  1. I can't ping duckdns.org on my home server. I only get 100 % packet loss. I can open the website in my browser though. I also can't ping www.duckdns.org, which redirects to appservers-duckdns-prod-1630339571.ca-central-1.elb.amazonaws.com. Also gets 100 % packet loss.
  2. I've added duckdns.org to my Uptime-Kuma and it got flagged as down because timeout of 48000ms exceeded but my other domains using DuckDNS were unaffected.
  3. I added another local domain to Uptime-Kuma to see the differences of having ignoring SSL errors tuned on or off and the number of retries:
  • Nextcloud
    • Ignore SSL error = false
    • Retries = 2
  • Proxmox
    • Ignore SSL error = true
    • Retries = 1
  • VPS
    • Ignore SSL error = false
    • Retries = 1
  • Homepage
    • Ignore SSL error = true
    • Retries = 2

Throughout the day only the newly added Homepage got flagged as down for 5 times. The 3 others were up the whole time.

15
submitted 5 months ago* (last edited 5 months ago) by [email protected] to c/[email protected]
 

I'm looking for an alternative Youtube front-end for Linux Desktop but FreeTube for example doesn't support resolutions higher than 1080p. Is there an easy to use client, that supports 1440p and higher out-of-the-box?

 

Is there a way to easily create Gotify notifications from critical system errors (journalctl -p 3)? I recently had a bunch of out-of-memory errors and it would've been great to be notified about them. There must be a pre-build solution for this, right? Ideally also dockerized. Thanks in advance!

 

Does anybody know whether there is a WebGUI/Docker for Deezloader?

 

So this is bugging me for a while and I'm just do dumb to get how I solve this, but here's the situation: Given I take a local backup of my system daily and have a retention policy that keeps a backup of the past 7 days each, a backup of the past 4 weeks each and a backup of the past 6 month each. That's either 17 backups or less if you consider some backups being counted as a daily and weekly or as a weekly and monthly. But that's not that important. The interesting part is, that I also take a remote backup of my local backup daily, which has the same retention policy, so it's cascading. Here there is obviously a huge overlap of backups, but I can't wrap my head around, how I calculate this. Is anybody willing and/or interested to solve this for and with me?

 

I'm looking for a simply solution to monitor all my servers and systems using a single dashboard. I want to see metrics like CPU usage, used RAM and storage to see if something is wrong.
I just set up Node-Exporter, Prometheus and Grafana but haven't found an existing dashboard that shows multiple hosts at once. Now I looked into Checkmk and Zabbix but I feel like both are a little overpowered for what I'm looking for. Do you have any recommendations?

 

I made a simple script and timer for a friend to automatically switch between light and dark theme on Plasma. In case anybody needs this.

 

I created this small script and thought it might be useful to someone else. Any feedback is welcome!

 

I set up Headscale and Tailscale using Docker on a VPS, which I want to use as my public IPv4 and Reverse Proxy to route incoming traffic to my local network and e. g. my home server. I also set up Tailscale using Docker on my home server and connected both to my Headscale server.
I am able to ping on Tailscale container from the other and vice versa and set up --advertise-routes=192.168.178.0/24 on my home server as well as --accept-routes on my VPS, but I can't ping local IP addresses from my VPS. What am I missing?
Both container are connected to the host network, I have opened UDP ports 41641 and 3478 on my VPS.

32
submitted 10 months ago* (last edited 10 months ago) by [email protected] to c/[email protected]
 

I'm looking for an easy way to upload files from my Android smartphone to my home server. is there a - ideally dockerized - solution for that? Some simple web GUI where I can click on "Upload" and the files will be saved to a certain directory on my home server?

EDIT: I should've added that I want to do this remotely and not in my local network. I want to be able to send files from my Android smartphone from anywhere via the internet to my home server. That's why I thought about a services hosted on my server, which frontend I could access through my smartphone. But I might've answered my question already with the following: https://github.com/zer0tonin/Mikochi

EDIT #2: Thanks guys, I ended up creating my own Docker container running nextcloudcmd inspired by this: https://github.com/juanitomint/nextcloud-client-docker But I built the container from scratch and it's very minimalistic. I can publish it on my Gitlab when it's somewhat ready. Here's a little preview.

Dockerfile

FROM alpine:latest
RUN apk update && apk add nextcloud-client
COPY nc.sh .
RUN chmod +x ./nc.sh
VOLUME /data
CMD ./nc.sh

nc. sh (How can I prevent automatic hyperlinking?)

#!/bin/sh
while true
do
        nextcloudcmd /data https://${username}:${passwort}@${nextcloud-domain}
        sleep 300
done
view more: next ›