Dashboard — 2026-04-21

Nazwa	Status	Obraz
vaultwarden	OK Up 2 hours (healthy)	vaultwarden/server:latest
reports	OK Up 8 hours (healthy)	nginx:alpine
redis	OK Up 43 minutes (healthy)	redis:7-alpine
n8n	OK Up 8 hours (healthy)	n8nio/n8n:latest
nginx-proxy-manager	OK Up 9 hours (healthy)	jc21/nginx-proxy-manager:latest
postgres	OK Up 42 hours (healthy)	postgres:16
uptime-kuma	OK Up 42 hours (healthy)	louislam/uptime-kuma:1
authelia	OK Up 42 hours (healthy)	authelia/authelia:latest

Domena	Ważny do	Pozostało
npm.gresmosoft.com	2026-07-11	81 dni
uptime.kumai.dev	2026-07-11	81 dni
n8n.kumai.dev	2026-07-11	81 dni
pass.kumai.dev	2026-07-11	81 dni

Sprawdzenie	Status	Szczegóły
Kontenery	OK	8/8 działa
RAM	OK	43%
Dysk	OK	46%
Backup	OK	19.5h temu
Logi (1h)	OK	czyste
Porty	OK	OK
SSL	OK	wszystkie OK
Fail2ban	OK	0 zablokowanych IP

76 zdarzeń z 6 kontenerów

vaultwarden 5

INFO| Starting Vaultwarden |

INFO[2026-04-20 20:19:15.924][start][INFO] Rocket has launched from http://0.0.0.0:80

INFO[2026-04-20 20:46:50.181][vaultwarden::api::identity][INFO] User gresmo logged in successfully. IP: 176.121.82.178

INFO[2026-04-20 20:54:11.385][vaultwarden::api::identity][INFO] User gresmo logged in successfully. IP: 176.121.82.178

INFO[2026-04-20 21:01:49.418][vaultwarden::api::identity][INFO] User gresmo logged in successfully. IP: 176.121.82.178

redis 26

ERROR1:C 20 Apr 2026 14:35:19.682 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can also cause failures w

INFO1:C 20 Apr 2026 14:35:19.682 * oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo

INFO1:C 20 Apr 2026 14:35:19.682 * Redis version=7.4.8, bits=64, commit=00000000, modified=0, pid=1, just started

INFO1:C 20 Apr 2026 14:35:19.682 * Configuration loaded

INFO1:M 20 Apr 2026 14:35:19.685 * Running mode=standalone, port=6379.

INFO1:M 20 Apr 2026 14:35:19.686 * Done loading RDB, keys loaded: 3, keys expired: 0.

INFO1:M 20 Apr 2026 14:35:19.686 * DB loaded from disk: 0.001 seconds

INFO1:M 20 Apr 2026 14:35:19.686 * Ready to accept connections tcp

INFO1:M 20 Apr 2026 15:35:20.089 * Background saving started by pid 721

INFO1:M 20 Apr 2026 15:35:20.190 * Background saving terminated with success

INFO1:M 20 Apr 2026 16:48:55.679 * Background saving started by pid 1598

INFO1:M 20 Apr 2026 16:48:55.781 * Background saving terminated with success

INFO1:M 20 Apr 2026 17:48:56.068 * Background saving started by pid 2310

INFO1:M 20 Apr 2026 17:48:56.169 * Background saving terminated with success

INFO1:M 20 Apr 2026 18:48:57.023 * Background saving started by pid 3009

INFO1:M 20 Apr 2026 18:48:57.125 * Background saving terminated with success

INFO1:M 20 Apr 2026 20:22:39.866 * Background saving started by pid 4102

INFO1:M 20 Apr 2026 20:22:39.969 * Background saving terminated with success

INFO1:M 20 Apr 2026 21:43:45.348 # Redis is now ready to exit, bye bye...

INFO1:C 20 Apr 2026 21:43:45.883 * oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo

INFO1:C 20 Apr 2026 21:43:45.883 * Redis version=7.4.8, bits=64, commit=00000000, modified=0, pid=1, just started

INFO1:C 20 Apr 2026 21:43:45.883 * Configuration loaded

INFO1:M 20 Apr 2026 21:43:45.888 * Running mode=standalone, port=6379.

INFO1:M 20 Apr 2026 21:43:45.890 * Done loading RDB, keys loaded: 3, keys expired: 0.

INFO1:M 20 Apr 2026 21:43:45.891 * DB loaded from disk: 0.001 seconds

INFO1:M 20 Apr 2026 21:43:45.891 * Ready to accept connections tcp

n8n 3

INFOn8n ready on ::, port 5678

INFOn8n Task Broker ready on 127.0.0.1, port 5679

ERRORFailed to start Python task runner in internal mode. because Python 3 is missing from this system. Launching a Python runner in internal mode is intended only for debugging and is not recommended for

nginx-proxy-manager 5

WARNuseradd warning: npm's uid 0 outside of the UID_MIN 1000 and UID_MAX 60000 range.

INFO[1;34m❯ [1;36mStarting backend ...[0m

INFO[1;34m❯ [1;36mStarting nginx ...[0m

INFO[4/20/2026] [8:21:15 PM] [SSL ] › ✔ success Requesting a certificate for pass.kumai.dev

INFOSuccessfully received certificate.

postgres 36

INFO2026-04-19 23:02:11.652 UTC [26] LOG: checkpoint starting: time

INFO2026-04-19 23:07:12.043 UTC [26] LOG: checkpoint starting: time

INFO2026-04-20 00:02:13.862 UTC [26] LOG: checkpoint starting: time

INFO2026-04-20 01:02:14.941 UTC [26] LOG: checkpoint starting: time

INFO2026-04-20 01:07:14.144 UTC [26] LOG: checkpoint starting: time

INFO2026-04-20 02:02:15.864 UTC [26] LOG: checkpoint starting: time

INFO2026-04-20 02:07:15.962 UTC [26] LOG: checkpoint starting: time

INFO2026-04-20 03:02:16.365 UTC [26] LOG: checkpoint starting: time

INFO2026-04-20 04:02:17.180 UTC [26] LOG: checkpoint starting: time

INFO2026-04-20 04:07:17.086 UTC [26] LOG: checkpoint starting: time

INFO2026-04-20 05:02:18.352 UTC [26] LOG: checkpoint starting: time

INFO2026-04-20 05:07:18.519 UTC [26] LOG: checkpoint starting: time

INFO2026-04-20 06:02:19.775 UTC [26] LOG: checkpoint starting: time

INFO2026-04-20 06:07:19.459 UTC [26] LOG: checkpoint starting: time

INFO2026-04-20 07:02:20.032 UTC [26] LOG: checkpoint starting: time

INFO2026-04-20 07:07:20.541 UTC [26] LOG: checkpoint starting: time

INFO2026-04-20 08:02:21.648 UTC [26] LOG: checkpoint starting: time

INFO2026-04-20 08:07:21.374 UTC [26] LOG: checkpoint starting: time

INFO2026-04-20 09:02:22.195 UTC [26] LOG: checkpoint starting: time

INFO2026-04-20 09:07:22.823 UTC [26] LOG: checkpoint starting: time

INFO2026-04-20 10:02:23.029 UTC [26] LOG: checkpoint starting: time

INFO2026-04-20 10:07:23.354 UTC [26] LOG: checkpoint starting: time

INFO2026-04-20 11:02:24.237 UTC [26] LOG: checkpoint starting: time

INFO2026-04-20 12:02:25.359 UTC [26] LOG: checkpoint starting: time

INFO2026-04-20 12:07:25.462 UTC [26] LOG: checkpoint starting: time

INFO2026-04-20 13:02:25.928 UTC [26] LOG: checkpoint starting: time

INFO2026-04-20 14:02:26.138 UTC [26] LOG: checkpoint starting: time

INFO2026-04-20 14:07:26.300 UTC [26] LOG: checkpoint starting: time

INFO2026-04-20 14:37:27.069 UTC [26] LOG: checkpoint starting: time

INFO2026-04-20 15:37:28.690 UTC [26] LOG: checkpoint starting: time

INFO2026-04-20 16:37:29.756 UTC [26] LOG: checkpoint starting: time

INFO2026-04-20 17:37:30.748 UTC [26] LOG: checkpoint starting: time

INFO2026-04-20 18:37:31.924 UTC [26] LOG: checkpoint starting: time

INFO2026-04-20 19:37:32.607 UTC [26] LOG: checkpoint starting: time

INFO2026-04-20 20:37:33.510 UTC [26] LOG: checkpoint starting: time

INFO2026-04-20 21:37:34.188 UTC [26] LOG: checkpoint starting: time

uptime-kuma 1

INFO2026-04-20T18:48:48+02:00 [AUTH] INFO: Successfully logged in user [email protected]. IP=172.18.0.5

vaultwarden 23

[2026-04-20 20:22:18.727][vaultwarden::api::web::_][WARN] Parameter guard `p: PathBuf` is forwarding: BadStart('.').
[2026-04-20 20:22:18.773][vaultwarden::api::web::_][WARN] Parameter guard `p: PathBuf` is forwarding: BadStart('.').
[2026-04-20 20:22:18.810][vaultwarden::api::web::_][WARN] Parameter guard `p: PathBuf` is forwarding: BadStart('.').
[2026-04-20 20:22:18.844][vaultwarden::api::web::_][WARN] Parameter guard `p: PathBuf` is forwarding: BadStart('.').
[2026-04-20 20:22:28.904][vaultwarden::api::web::_][WARN] Parameter guard `p: PathBuf` is forwarding: BadStart('.').
[2026-04-20 20:22:29.713][vaultwarden::api::web::_][WARN] Parameter guard `p: PathBuf` is forwarding: BadStart('.').
[2026-04-20 20:22:33.714][vaultwarden::api::web::_][WARN] Parameter guard `p: PathBuf` is forwarding: BadStart('.').
[2026-04-20 20:22:39.729][vaultwarden::api::web::_][WARN] Parameter guard `p: PathBuf` is forwarding: BadStart('.').
[2026-04-20 20:22:50.642][vaultwarden::api::web::_][WARN] Parameter guard `p: PathBuf` is forwarding: BadStart('.').
[2026-04-20 20:22:50.891][vaultwarden::api::web::_][WARN] Parameter guard `p: PathBuf` is forwarding: BadStart('.').
[2026-04-20 20:22:51.243][vaultwarden::api::web::_][WARN] Parameter guard `p: PathBuf` is forwarding: BadStart('.').
[2026-04-20 20:22:51.601][vaultwarden::api::web::_][WARN] Parameter guard `p: PathBuf` is forwarding: BadStart('.').
[2026-04-20 20:22:54.564][vaultwarden::api::web::_][WARN] Parameter guard `p: PathBuf` is forwarding: BadStart('.').
[2026-04-20 20:22:54.729][vaultwarden::api::web::_][WARN] Parameter guard `p: PathBuf` is forwarding: BadStart('.').
[2026-04-20 20:22:54.736][vaultwarden::api::web::_][WARN] Parameter guard `p: PathBuf` is forwarding: BadStart('.').
[2026-04-20 20:22:55.156][vaultwarden::api::web::_][WARN] Parameter guard `p: PathBuf` is forwarding: BadStart('.').
[2026-04-20 20:22:55.488][vaultwarden::api::web::_][WARN] Parameter guard `p: PathBuf` is forwarding: BadStart('.').
[2026-04-20 20:23:52.109][vaultwarden::api::web::_][WARN] Parameter guard `p: PathBuf` is forwarding: BadStart('.').
[2026-04-20 20:23:52.348][vaultwarden::api::web::_][WARN] Parameter guard `p: PathBuf` is forwarding: BadStart('.').
[2026-04-20 20:23:52.871][vaultwarden::api::web::_][WARN] Parameter guard `p: PathBuf` is forwarding: BadStart('.').
[2026-04-20 21:49:18.161][vaultwarden::api::web::_][WARN] Parameter guard `p: PathBuf` is forwarding: BadStart('.').
[2026-04-20 21:54:15.097][vaultwarden::api::web::_][WARN] Parameter guard `p: PathBuf` is forwarding: BadStart('.').
[2026-04-20 21:54:35.723][vaultwarden::api::web::_][WARN] Parameter guard `p: PathBuf` is forwarding: BadStart('.').

redis 1

1:C 20 Apr 2026 14:35:19.682 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can also cause failures without low memory condition, see https://github.com/jemalloc/jemalloc/issues/1328. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.

nginx-proxy-manager 1

useradd warning: npm's uid 0 outside of the UID_MIN 1000 and UID_MAX 60000 range.

Historia backupów

Plik	Rozmiar	Wiek	Status
backup_20260420_0300.sql.gz	26.3 KB	19h 27m	OK
backup_20260419_0300.sql.gz	26.3 KB	43h 27m	OK
backup_20260418_0300.sql.gz	26.3 KB	67h 27m	OK
backup_20260417_0300.sql.gz	26.3 KB	91h 27m	OK
backup_20260416_0300.sql.gz	26.3 KB	115h 27m	OK
backup_20260415_0300.sql.gz	26.3 KB	139h 27m	OK
backup_20260414_0300.sql.gz	26.3 KB	163h 27m	OK
backup_test_20260413_1820.sql.gz	1.0 KB	172h 7m	OK

Łącznie: 0.2 MB · 8 plików

Docker — porty

Kontener	Porty	Uwaga
vaultwarden	`80/tcp`	OK
reports	`80/tcp`	OK
redis	`6379/tcp`	OK
n8n	`127.0.0.1:5678->5678/tcp`	OK
nginx-proxy-manager	`0.0.0.0:80->80/tcp, [::]:80->80/tcp, 0.0.0.0:443->443/tcp, [::]:443->443/tcp, 127.0.0.1:81->81/tcp`	OK
postgres	`127.0.0.1:5432->5432/tcp`	OK
uptime-kuma	`127.0.0.1:3001->3001/tcp`	OK
authelia	`9091/tcp`	OK

UFW status

UFW nieaktywny lub brak danych

Nasłuchujące porty (ss)

LISTEN 0      4096       127.0.0.1:3001      0.0.0.0:*          
LISTEN 0      4096       127.0.0.1:81        0.0.0.0:*          
LISTEN 0      4096   127.0.0.53%lo:53        0.0.0.0:*          
LISTEN 0      4096       127.0.0.1:5678      0.0.0.0:*          
LISTEN 0      4096      127.0.0.54:53        0.0.0.0:*          
LISTEN 0      4096         0.0.0.0:443       0.0.0.0:*          
LISTEN 0      4096         0.0.0.0:80        0.0.0.0:*          
LISTEN 0      4096         0.0.0.0:2222      0.0.0.0:*          
LISTEN 0      4096       127.0.0.1:5432      0.0.0.0:*          
LISTEN 0      4096            [::]:443          [::]:*          
LISTEN 0      4096            [::]:80           [::]:*          
LISTEN 0      4096            [::]:2222         [::]:*

basecamp dashboard

Kontenery

Zasoby

Backup Postgres

Certyfikaty SSL

Błędy (ostatnie 12h)

Wyniki