fix: change Umami external port from 3000 to 3001 to avoid conflict with Gitea

Co-authored-by: Junie <junie@jetbrains.com>
2026-07-25 22:53:34 +02:00
parent 5102945ab4
commit 11b77a6994
5 changed files with 30 additions and 9 deletions
@@ -41,7 +41,8 @@ Both the console and Sentry are now active (original Question 3 resolved as a co

 ### Website analytics — decided: self-hosted Umami
 **Decided**: self-hosted Umami, running via Podman on the webserver Pi (Pi Main,
-`192.168.1.103:3000`), reachable for the dashboard itself via `analytics.slpsoftware.nl`
+`192.168.1.103:3001` — note: not the default 3000, since Gitea already occupies
+that port on the same Pi), reachable for the dashboard itself via `analytics.slpsoftware.nl`
 (reverse-proxied + SSL via certbot, same pattern as `test.slpsoftware.nl`). Chosen over
 GA4 for privacy-friendliness (typically no cookie banner needed) and full self-hosted
 control, and over a hosted Umami/Plausible plan to avoid recurring cost.