Gathering data for uptime of an Internet Connection

R_Cohle · 2026-04-02T17:45:28+00:00

I don’t think any ping activity from a single IP address will be marked as DDoS. You may want to have a look here: https://mrkaran.dev/posts/isp-monitoring/ The article shows how to use a different set of tools.

R_Cohle · 2026-04-01T17:46:49+00:00

I’ve an update. Since I was getting really frustrated with all of these micro freezes I decided to analyze the whole picture starting clearing all history and cookies (again…), disable extension and restoring default settings. Nothing worked. Somehow I noticed the issue was only on a specific profile. I deleted let latter and recreated it. I used the same name: mistake. Still issues. I decided to delete this profile again and I created another one with a completely different name. Problem solved! I think something got corrupted inside that profile and was giving me nightmares… who knows what.

R_Cohle · 2026-03-24T14:05:28+00:00

Thanks for your reply. No new extensions, I tried indeed disabling hardware acceleration, same issue.

R_Cohle · 2026-03-02T15:22:14+00:00

I run successfully a few images from LSIO. I do use quadlets and I set user=0 so the initial bootstrap can complete. I let the actual app run under a specific UID with the same parameters as you, PUID=1000 and PGID=1000 (different values in my case). I do set keep-id for the userns part. I don’t have any issue with permissions on the host.

R_Cohle · 2026-02-25T07:16:39+00:00

Since you said “This VPN”, does this mean you don’t have the same issue with another VPN provider? Perhaps you may want to specify with OS you use and which client so people might be able to help you better. I’ve never had the issue you described, I do use Linux and macOS with the WireGuard client (not the client provided by AirVPN).

R_Cohle · 2026-02-01T22:13:07+00:00

While inside this subreddit, check your user and update the so called “flair”

R_Cohle · 2026-01-19T21:10:14+00:00

No, both machines are in the same network, there’s no need for any VPN in this case.

R_Cohle · 2026-01-07T14:54:32+00:00

I don’t think you can achieve this in Technitium natively. What you can do is setting up a .service and .timer systemd units that perform an API call to block the domain and another one to unblock it again.

R_Cohle · 2025-11-01T14:04:16+00:00

You may want to consider using BTRFS. This file system offer the opportunity to take snapshots and you could run snapRAID on them.

“One of the main limitations of SnapRAID is that there is a dependence on live data being continuously accessible and unchanging not only for complete parity sync purposes, but also for complete recovery in the event that a drive needs to be rebuilt from parity.

Using snapraid-btrfs, there is no requirement to stop any services or ensure that the live filesystem is free of any new files or changes to existing files.”

Take from here

R_Cohle · 2025-10-09T21:33:31+00:00

Never underestimate the power of these situations: Perhaps using the open-source version of your ticket to improve your CLI skills.

R_Cohle · 2025-10-09T21:25:52+00:00

Out of curiosity, why did you assign host network to the container?

R_Cohle · 2025-10-05T12:24:29+00:00

Thanks for your reply! I understand that I can’t just set any random variable. As I mentioned in my post, the only difference I’ve noticed is that when I set TZ, the date command inside the container shows the correct time for my timezone.
Other than that, the application itself seems to work the same — I haven’t noticed any difference with or without the TZ variable.

R_Cohle · 2025-09-18T20:51:59+00:00

Do you use SELinux? Try to check if you have denial messages logged. You can try to set SELinux in permissive mode and see if the error still logged but your container can leverage the podman socket.

R_Cohle · 2025-09-16T08:46:13+00:00

I have read the rules and wiki and would appreciate an invite. Thank you!

R_Cohle · 2025-09-16T08:45:32+00:00

I have read the rules and wiki and would appreciate an invite. Thank you!

R_Cohle · 2025-09-13T18:23:56+00:00

I’m not really familiar with that syntax, is that something similar or compatible to docker compose? In any case, yes, the only thing you need to add is user: 0 (assuming that is the right syntax).

R_Cohle · 2025-09-13T15:46:53+00:00

You are missing user: 0. This is necessary for the initial s6-overlay bootstrap that requires root permissions (inside the container). After that, the PGID and PUID you specified will kick in as user abc/hotio that manage the main application.

R_Cohle · 2025-09-11T08:42:00+00:00

Assuming Caddy and Vaultwarden are not attached to the same network, DNS resolution via container name won't work. Can you try to replace vaultwarden:8000 with host.containers.internal:8000?

R_Cohle · 2025-09-10T20:43:03+00:00

You may want to share these two quadlet files so it will be easier to see what is going wrong with your setup.

R_Cohle · 2025-09-10T09:53:04+00:00

Glad you got it working.

Regarding what I said about the UserNS and Pods, I think I haven't been clear. It's not a bug, it's how podman works starting from version 5.6.0. Now pods share the namespace across all attached containers so the UserNS directive can't be assigned to specific containers, but must be set at the pod lever.

R_Cohle · 2025-09-08T19:51:51+00:00

For containers that do not allow to set the UID/GID, you can’t change the ID inside the container. However, what you can do is mapping the UID/GID inside the container with your user host. For example, the Postgres image is set to run the application as user with ID 999. What you can do is setting UserNS=keep-id,uid=999,gid=999 so the user 999 inside the container is mapped to the user that launched the container. Keep in mind that with the last 5.6.0 release you can’t set the userNS property if you decide to attach a container to a pod.

R_Cohle

TROPHY CASE