Comments (10)
n0w33d
commented on June 11, 2024
2
Okay I figured out the solution:
Per Steve's analysis, I completely wiped my WSL setup and started over from scratch. This did not resolve the situation.
The actual issue was that I was launching Debian WSL with a terminal under administrator privileges and it did not have the environment configured the same way it is if you launch Debian WSL from its Start Menu shortcut.
In summary, the fix was to simply launch WSL from the distro start menu shortcut instead of manually via terminal CLI (PowerShell or whatever).
from runtipi.
meienberger
commented on June 11, 2024
1
What does docker ps -a show for runtipi-reverse-proxy?
Maybe traefik doesn't support this setup
Please keep in mind that Windows + WSL is not officially supported and not tested against so it might take some more investigation on your side if we want to fix the bug
from runtipi.
n0w33d
commented on June 11, 2024
The following is the output for docker ps -a (not sure how to show it for runtipi-reverse-proxy that you requested)
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
8d558493a351 traefik:v2.11 "/entrypoint.sh --pr…" About a minute ago Created runtipi-reverse-proxy
1c6eb7221e3d ghcr.io/runtipi/runtipi:v3.1.3 "docker-entrypoint.s…" About a minute ago Up About a minute (unhealthy) 3000/tcp, 5000-5001/tcp runtipi
957a99e46d62 redis:7.2.0 "docker-entrypoint.s…" About a minute ago Up About a minute (healthy) 0.0.0.0:6379->6379/tcp runtipi-redis
4379747aa0cb postgres:14 "docker-entrypoint.s…" About a minute ago Up About a minute (healthy) 0.0.0.0:5432->5432/tcp runtipi-db
from runtipi.
n0w33d
commented on June 11, 2024
The following is the entire Docker log dump when executing runtipi-cli start taken from Docker Desktop:
2024-04-14 00:33:21 runtipi-redis | 1:C 14 Apr 2024 04:33:21.519 * oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
2024-04-14 00:33:21 runtipi-redis | 1:C 14 Apr 2024 04:33:21.519 * Redis version=7.2.0, bits=64, commit=00000000, modified=0, pid=1, just started
2024-04-14 00:33:21 runtipi-redis | 1:C 14 Apr 2024 04:33:21.519 * Configuration loaded
2024-04-14 00:33:21 runtipi-redis | 1:M 14 Apr 2024 04:33:21.519 * monotonic clock: POSIX clock_gettime
2024-04-14 00:33:21 runtipi-redis | 1:M 14 Apr 2024 04:33:21.519 * Running mode=standalone, port=6379.
2024-04-14 00:33:21 runtipi-redis | 1:M 14 Apr 2024 04:33:21.520 * Server initialized
2024-04-14 00:33:21 runtipi-redis | 1:M 14 Apr 2024 04:33:21.520 * Loading RDB produced by version 7.2.0
2024-04-14 00:33:21 runtipi-redis | 1:M 14 Apr 2024 04:33:21.520 * RDB age 81 seconds
2024-04-14 00:33:21 runtipi-redis | 1:M 14 Apr 2024 04:33:21.520 * RDB memory usage when created 0.83 Mb
2024-04-14 00:33:21 runtipi-redis | 1:M 14 Apr 2024 04:33:21.520 * Done loading RDB, keys loaded: 0, keys expired: 0.
2024-04-14 00:33:21 runtipi-redis | 1:M 14 Apr 2024 04:33:21.520 * DB loaded from disk: 0.000 seconds
2024-04-14 00:33:21 runtipi-redis | 1:M 14 Apr 2024 04:33:21.520 * Ready to accept connections tcp
2024-04-14 00:33:21 runtipi-db |
2024-04-14 00:33:21 runtipi-db | PostgreSQL Database directory appears to contain a database; Skipping initialization
2024-04-14 00:33:21 runtipi-db |
2024-04-14 00:33:21 runtipi-db | 2024-04-14 04:33:21.410 UTC [1] LOG: starting PostgreSQL 14.11 (Debian 14.11-1.pgdg120+2) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit
2024-04-14 00:33:21 runtipi-db | 2024-04-14 04:33:21.453 UTC [1] LOG: listening on IPv4 address "0.0.0.0", port 5432
2024-04-14 00:33:21 runtipi-db | 2024-04-14 04:33:21.453 UTC [1] LOG: listening on IPv6 address "::", port 5432
2024-04-14 00:33:21 runtipi-db | 2024-04-14 04:33:21.458 UTC [1] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2024-04-14 00:33:21 runtipi-db | 2024-04-14 04:33:21.497 UTC [27] LOG: database system was shut down at 2024-04-14 04:32:00 UTC
2024-04-14 00:33:21 runtipi-db | 2024-04-14 04:33:21.501 UTC [1] LOG: database system is ready to accept connections
2024-04-14 00:33:27 runtipi |
2024-04-14 00:33:27 runtipi | -------------
2024-04-14 00:33:27 runtipi |
2024-04-14 00:33:27 runtipi | __/\\\\\\\\\\\\\____/\\\\____________/\\\\____/\\\\\\\\\_____
2024-04-14 00:33:27 runtipi | _\/\\\/////////\\\_\/\\\\\\________/\\\\\\__/\\\///////\\\___
2024-04-14 00:33:27 runtipi | _\/\\\_______\/\\\_\/\\\//\\\____/\\\//\\\_\///______\//\\\__
2024-04-14 00:33:27 runtipi | _\/\\\\\\\\\\\\\/__\/\\\\///\\\/\\\/_\/\\\___________/\\\/___
2024-04-14 00:33:27 runtipi | _\/\\\/////////____\/\\\__\///\\\/___\/\\\________/\\\//_____
2024-04-14 00:33:27 runtipi | _\/\\\_____________\/\\\____\///_____\/\\\_____/\\\//________
2024-04-14 00:33:27 runtipi | _\/\\\_____________\/\\\_____________\/\\\___/\\\/___________
2024-04-14 00:33:27 runtipi | _\/\\\_____________\/\\\_____________\/\\\__/\\\\\\\\\\\\\\\_
2024-04-14 00:33:27 runtipi | _\///______________\///______________\///__\///////////////__
2024-04-14 00:33:27 runtipi |
2024-04-14 00:33:27 runtipi |
2024-04-14 00:33:27 runtipi | Runtime Edition
2024-04-14 00:33:27 runtipi |
2024-04-14 00:33:27 runtipi | PM2 is a Production Process Manager for Node.js applications
2024-04-14 00:33:27 runtipi | with a built-in Load Balancer.
2024-04-14 00:33:27 runtipi |
2024-04-14 00:33:27 runtipi | Start and Daemonize any application:
2024-04-14 00:33:27 runtipi | $ pm2 start app.js
2024-04-14 00:33:27 runtipi |
2024-04-14 00:33:27 runtipi | Load Balance 4 instances of api.js:
2024-04-14 00:33:27 runtipi | $ pm2 start api.js -i 4
2024-04-14 00:33:27 runtipi |
2024-04-14 00:33:27 runtipi | Monitor in production:
2024-04-14 00:33:27 runtipi | $ pm2 monitor
2024-04-14 00:33:27 runtipi |
2024-04-14 00:33:27 runtipi | Make pm2 auto-boot at server restart:
2024-04-14 00:33:27 runtipi | $ pm2 startup
2024-04-14 00:33:27 runtipi |
2024-04-14 00:33:27 runtipi | To go further checkout:
2024-04-14 00:33:27 runtipi | http://pm2.io/
2024-04-14 00:33:27 runtipi |
2024-04-14 00:33:27 runtipi |
2024-04-14 00:33:27 runtipi | -------------
2024-04-14 00:33:27 runtipi |
2024-04-14 00:33:27 runtipi | [PM2] Spawning PM2 daemon with pm2_home=/root/.pm2
2024-04-14 00:33:27 runtipi | [PM2] PM2 Successfully daemonized
2024-04-14 00:33:27 runtipi | [PM2] Starting /worker/index.js in fork_mode (1 instance)
2024-04-14 00:33:27 runtipi | [PM2] Done.
2024-04-14 00:33:27 runtipi | ┌────┬───────────┬─────────────┬─────────┬─────────┬──────────┬────────┬──────┬───────────┬──────────┬──────────┬──────────┬──────────┐
2024-04-14 00:33:27 runtipi | │ id │ name │ namespace │ version │ mode │ pid │ uptime │ ↺ │ status │ cpu │ mem │ user │ watching │
2024-04-14 00:33:27 runtipi | ├────┼───────────┼─────────────┼─────────┼─────────┼──────────┼────────┼──────┼───────────┼──────────┼──────────┼──────────┼──────────┤
2024-04-14 00:33:27 runtipi | │ 0 │ worker │ default │ N/A │ fork │ 38 │ 0s │ 0 │ online │ 0% │ 20.3mb │ root │ disabled │
2024-04-14 00:33:27 runtipi | └────┴───────────┴─────────────┴─────────┴─────────┴──────────┴────────┴──────┴───────────┴──────────┴──────────┴──────────┴──────────┘
2024-04-14 00:33:25 runtipi-reverse-proxy | time="2024-04-14T04:33:25Z" level=info msg="Configuration loaded from flags."
As you can see, runtipi-reverse-proxy runs last, this is becuase I manually started it after executing the runtipi CLI binary since it does not auto start that service on its own when ran, otherwise it would not even show up at all in the logs.
Ultimately it sits there until it finally fails and reports the container being "unhealthy".
from runtipi.
n0w33d
commented on June 11, 2024
Here is another log dump for another attempt to troubleshoot:
2024-04-26 16:46:52 runtipi |
2024-04-26 16:46:52 runtipi | -------------
2024-04-26 16:46:52 runtipi |
2024-04-26 16:46:52 runtipi | __/\\\\\\\\\\\\\____/\\\\____________/\\\\____/\\\\\\\\\_____
2024-04-26 16:46:52 runtipi | _\/\\\/////////\\\_\/\\\\\\________/\\\\\\__/\\\///////\\\___
2024-04-26 16:46:52 runtipi | _\/\\\_______\/\\\_\/\\\//\\\____/\\\//\\\_\///______\//\\\__
2024-04-26 16:46:52 runtipi | _\/\\\\\\\\\\\\\/__\/\\\\///\\\/\\\/_\/\\\___________/\\\/___
2024-04-26 16:46:52 runtipi | _\/\\\/////////____\/\\\__\///\\\/___\/\\\________/\\\//_____
2024-04-26 16:46:52 runtipi | _\/\\\_____________\/\\\____\///_____\/\\\_____/\\\//________
2024-04-26 16:46:52 runtipi | _\/\\\_____________\/\\\_____________\/\\\___/\\\/___________
2024-04-26 16:46:52 runtipi | _\/\\\_____________\/\\\_____________\/\\\__/\\\\\\\\\\\\\\\_
2024-04-26 16:46:52 runtipi | _\///______________\///______________\///__\///////////////__
2024-04-26 16:46:52 runtipi |
2024-04-26 16:46:52 runtipi |
2024-04-26 16:46:52 runtipi | Runtime Edition
2024-04-26 16:46:52 runtipi |
2024-04-26 16:46:52 runtipi | PM2 is a Production Process Manager for Node.js applications
2024-04-26 16:46:52 runtipi | with a built-in Load Balancer.
2024-04-26 16:46:52 runtipi |
2024-04-26 16:46:52 runtipi | Start and Daemonize any application:
2024-04-26 16:46:52 runtipi | $ pm2 start app.js
2024-04-26 16:46:52 runtipi |
2024-04-26 16:46:52 runtipi | Load Balance 4 instances of api.js:
2024-04-26 16:46:52 runtipi | $ pm2 start api.js -i 4
2024-04-26 16:46:52 runtipi |
2024-04-26 16:46:52 runtipi | Monitor in production:
2024-04-26 16:46:52 runtipi | $ pm2 monitor
2024-04-26 16:46:52 runtipi |
2024-04-26 16:46:52 runtipi | Make pm2 auto-boot at server restart:
2024-04-26 16:46:52 runtipi | $ pm2 startup
2024-04-26 16:46:52 runtipi |
2024-04-26 16:46:52 runtipi | To go further checkout:
2024-04-26 16:46:52 runtipi | http://pm2.io/
2024-04-26 16:46:52 runtipi |
2024-04-26 16:46:52 runtipi |
2024-04-26 16:46:52 runtipi | -------------
2024-04-26 16:46:52 runtipi |
2024-04-26 16:46:52 runtipi | [PM2] Spawning PM2 daemon with pm2_home=/root/.pm2
2024-04-26 16:46:53 runtipi | [PM2] PM2 Successfully daemonized
2024-04-26 16:46:53 runtipi | [PM2] Starting /worker/index.js in fork_mode (1 instance)
2024-04-26 16:46:53 runtipi | [PM2] Done.
2024-04-26 16:46:53 runtipi | ┌────┬───────────┬─────────────┬─────────┬─────────┬──────────┬────────┬──────┬───────────┬──────────┬──────────┬──────────┬──────────┐
2024-04-26 16:46:53 runtipi | │ id │ name │ namespace │ version │ mode │ pid │ uptime │ ↺ │ status │ cpu │ mem │ user │ watching │
2024-04-26 16:46:53 runtipi | ├────┼───────────┼─────────────┼─────────┼─────────┼──────────┼────────┼──────┼───────────┼──────────┼──────────┼──────────┼──────────┤
2024-04-26 16:46:53 runtipi | │ 0 │ worker │ default │ N/A │ fork │ 37 │ 0s │ 0 │ online │ 0% │ 20.4mb │ root │ disabled │
2024-04-26 16:46:53 runtipi | └────┴───────────┴─────────────┴─────────┴─────────┴──────────┴────────┴──────┴───────────┴──────────┴──────────┴──────────┴──────────┘
2024-04-26 16:46:46 runtipi-db |
2024-04-26 16:46:46 runtipi-db | PostgreSQL Database directory appears to contain a database; Skipping initialization
2024-04-26 16:46:46 runtipi-db |
2024-04-26 16:46:46 runtipi-db | 2024-04-26 20:46:46.776 UTC [1] LOG: starting PostgreSQL 14.11 (Debian 14.11-1.pgdg120+2) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit
2024-04-26 16:46:46 runtipi-db | 2024-04-26 20:46:46.777 UTC [1] LOG: listening on IPv4 address "0.0.0.0", port 5432
2024-04-26 16:46:46 runtipi-db | 2024-04-26 20:46:46.777 UTC [1] LOG: listening on IPv6 address "::", port 5432
2024-04-26 16:46:46 runtipi-db | 2024-04-26 20:46:46.781 UTC [1] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2024-04-26 16:46:46 runtipi-db | 2024-04-26 20:46:46.785 UTC [27] LOG: database system was shut down at 2024-04-20 17:29:30 UTC
2024-04-26 16:46:46 runtipi-db | 2024-04-26 20:46:46.789 UTC [1] LOG: database system is ready to accept connections
2024-04-26 16:52:01 runtipi-db | 2024-04-26 20:52:01.424 UTC [535] LOG: invalid length of startup packet
2024-04-26 16:46:46 runtipi-redis | 1:C 26 Apr 2024 20:46:46.660 * oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
2024-04-26 16:46:46 runtipi-redis | 1:C 26 Apr 2024 20:46:46.660 * Redis version=7.2.0, bits=64, commit=00000000, modified=0, pid=1, just started
2024-04-26 16:46:46 runtipi-redis | 1:C 26 Apr 2024 20:46:46.660 * Configuration loaded
2024-04-26 16:46:46 runtipi-redis | 1:M 26 Apr 2024 20:46:46.660 * monotonic clock: POSIX clock_gettime
2024-04-26 16:46:46 runtipi-redis | 1:M 26 Apr 2024 20:46:46.660 * Running mode=standalone, port=6379.
2024-04-26 16:46:46 runtipi-redis | 1:M 26 Apr 2024 20:46:46.661 * Server initialized
2024-04-26 16:46:46 runtipi-redis | 1:M 26 Apr 2024 20:46:46.661 * Loading RDB produced by version 7.2.0
2024-04-26 16:46:46 runtipi-redis | 1:M 26 Apr 2024 20:46:46.661 * RDB age 530236 seconds
2024-04-26 16:46:46 runtipi-redis | 1:M 26 Apr 2024 20:46:46.661 * RDB memory usage when created 0.83 Mb
2024-04-26 16:46:46 runtipi-redis | 1:M 26 Apr 2024 20:46:46.661 * Done loading RDB, keys loaded: 0, keys expired: 0.
2024-04-26 16:46:46 runtipi-redis | 1:M 26 Apr 2024 20:46:46.661 * DB loaded from disk: 0.000 seconds
2024-04-26 16:46:46 runtipi-redis | 1:M 26 Apr 2024 20:46:46.661 * Ready to accept connections tcp
2024-04-26 16:52:05 runtipi-redis | 1:M 26 Apr 2024 20:52:05.564 # Possible SECURITY ATTACK detected. It looks like somebody is sending POST or Host: commands to Redis. This is likely due to an attacker attempting to use Cross Protocol Scripting to compromise your Redis instance. Connection from 192.168.32.1:36076 aborted.
2024-04-26 16:56:26 runtipi-reverse-proxy | time="2024-04-26T20:56:26Z" level=info msg="Configuration loaded from flags."
from runtipi.
meienberger
commented on June 11, 2024
Last lines of logs are weird
What is running on this port? It is spamming redis 192.168.32.1:36076
from runtipi.
n0w33d
commented on June 11, 2024
Last lines of logs are weird
What is running on this port? It is spamming redis 192.168.32.1:36076
I shut down the docker-container and that IP disappeared, so it was something launched with tipi. I ran the runtipi-cli update latest after deleting all docker containers with docker system prune and now redis is spitting out a new IP address prompted an "attack:"
2024-04-27 23:50:10 1:C 28 Apr 2024 03:50:10.630 * oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
2024-04-27 23:50:10 1:C 28 Apr 2024 03:50:10.630 * Redis version=7.2.0, bits=64, commit=00000000, modified=0, pid=1, just started
2024-04-27 23:50:10 1:C 28 Apr 2024 03:50:10.630 * Configuration loaded
2024-04-27 23:50:10 1:M 28 Apr 2024 03:50:10.630 * monotonic clock: POSIX clock_gettime
2024-04-27 23:50:10 1:M 28 Apr 2024 03:50:10.630 * Running mode=standalone, port=6379.
2024-04-27 23:50:10 1:M 28 Apr 2024 03:50:10.631 * Server initialized
2024-04-27 23:50:10 1:M 28 Apr 2024 03:50:10.631 * Loading RDB produced by version 7.2.0
2024-04-27 23:50:10 1:M 28 Apr 2024 03:50:10.631 * RDB age 109854 seconds
2024-04-27 23:50:10 1:M 28 Apr 2024 03:50:10.631 * RDB memory usage when created 0.83 Mb
2024-04-27 23:50:10 1:M 28 Apr 2024 03:50:10.631 * Done loading RDB, keys loaded: 0, keys expired: 0.
2024-04-27 23:50:10 1:M 28 Apr 2024 03:50:10.631 * DB loaded from disk: 0.000 seconds
2024-04-27 23:50:10 1:M 28 Apr 2024 03:50:10.631 * Ready to accept connections tcp
2024-04-27 23:50:41 1:M 28 Apr 2024 03:50:41.546 # Possible SECURITY ATTACK detected. It looks like somebody is sending POST or Host: commands to Redis. This is likely due to an attacker attempting to use Cross Protocol Scripting to compromise your Redis instance. Connection from 192.168.160.1:35020 aborted.
the "192.168.160.x" and "192.168.32.x" subnets are not deliberately part of my network topology, its likely something coming out of docker. This makes sense since tipi is the only software running via docker-compose; I literally have nothing else running, just tipi.
from runtipi.
n0w33d
commented on June 11, 2024
Another attempt, this time with tipi version 3.2.0:
Running the following command sudo ./runtipi-cli update latest, results in the following output:
Welcome to Runtipi CLI ✨
✓ Tipi successfully stopped
✓ Found version 3.2.0
✓ Downloaded runtipi-cli-linux-x86_64.tar.gz
✓ Extracted tarball
✓ Tipi updated successfully. Starting new CLI
╔════════════════════════ Runtipi started successfully ════════════════════════╗
║ ║
║ Visit http://172.21.147.158:80 to access the dashboard ║
║ ║
║ You are now running version 3.2.0 ║
║ ║
║ Tipi is entirely written in TypeScript and we are looking for ║
║ contributors! ║
║ ║
╚══════════════════════════════════════════════════════════════════════════════╝
Accessing the IP address that is stated in the CLI output simply does not display a page, just a 404 error.
Docker logs are below:
2024-05-03 13:23:39 runtipi |
2024-05-03 13:23:39 runtipi | -------------
2024-05-03 13:23:39 runtipi |
2024-05-03 13:23:39 runtipi | __/\\\\\\\\\\\\\____/\\\\____________/\\\\____/\\\\\\\\\_____
2024-05-03 13:23:39 runtipi | _\/\\\/////////\\\_\/\\\\\\________/\\\\\\__/\\\///////\\\___
2024-05-03 13:23:39 runtipi | _\/\\\_______\/\\\_\/\\\//\\\____/\\\//\\\_\///______\//\\\__
2024-05-03 13:23:39 runtipi | _\/\\\\\\\\\\\\\/__\/\\\\///\\\/\\\/_\/\\\___________/\\\/___
2024-05-03 13:23:39 runtipi | _\/\\\/////////____\/\\\__\///\\\/___\/\\\________/\\\//_____
2024-05-03 13:23:39 runtipi | _\/\\\_____________\/\\\____\///_____\/\\\_____/\\\//________
2024-05-03 13:23:39 runtipi | _\/\\\_____________\/\\\_____________\/\\\___/\\\/___________
2024-05-03 13:23:39 runtipi | _\/\\\_____________\/\\\_____________\/\\\__/\\\\\\\\\\\\\\\_
2024-05-03 13:23:39 runtipi | _\///______________\///______________\///__\///////////////__
2024-05-03 13:23:39 runtipi |
2024-05-03 13:23:39 runtipi |
2024-05-03 13:23:39 runtipi | Runtime Edition
2024-05-03 13:23:39 runtipi |
2024-05-03 13:23:39 runtipi | PM2 is a Production Process Manager for Node.js applications
2024-05-03 13:23:39 runtipi | with a built-in Load Balancer.
2024-05-03 13:23:39 runtipi |
2024-05-03 13:23:39 runtipi | Start and Daemonize any application:
2024-05-03 13:23:39 runtipi | $ pm2 start app.js
2024-05-03 13:23:39 runtipi |
2024-05-03 13:23:39 runtipi | Load Balance 4 instances of api.js:
2024-05-03 13:23:39 runtipi | $ pm2 start api.js -i 4
2024-05-03 13:23:39 runtipi |
2024-05-03 13:23:39 runtipi | Monitor in production:
2024-05-03 13:23:39 runtipi | $ pm2 monitor
2024-05-03 13:23:39 runtipi |
2024-05-03 13:23:39 runtipi | Make pm2 auto-boot at server restart:
2024-05-03 13:23:39 runtipi | $ pm2 startup
2024-05-03 13:23:39 runtipi |
2024-05-03 13:23:39 runtipi | To go further checkout:
2024-05-03 13:23:39 runtipi | http://pm2.io/
2024-05-03 13:23:39 runtipi |
2024-05-03 13:23:39 runtipi |
2024-05-03 13:23:39 runtipi | -------------
2024-05-03 13:23:39 runtipi |
2024-05-03 13:23:39 runtipi | [PM2] Spawning PM2 daemon with pm2_home=/root/.pm2
2024-05-03 13:23:39 runtipi | [PM2] PM2 Successfully daemonized
2024-05-03 13:23:39 runtipi | [PM2] Starting /worker/index.js in fork_mode (1 instance)
2024-05-03 13:23:39 runtipi | [PM2] Done.
2024-05-03 13:23:39 runtipi | ┌────┬───────────┬─────────────┬─────────┬─────────┬──────────┬────────┬──────┬───────────┬──────────┬──────────┬──────────┬──────────┐
2024-05-03 13:23:39 runtipi | │ id │ name │ namespace │ version │ mode │ pid │ uptime │ ↺ │ status │ cpu │ mem │ user │ watching │
2024-05-03 13:23:39 runtipi | ├────┼───────────┼─────────────┼─────────┼─────────┼──────────┼────────┼──────┼───────────┼──────────┼──────────┼──────────┼──────────┤
2024-05-03 13:23:39 runtipi | │ 0 │ worker │ default │ N/A │ fork │ 37 │ 0s │ 0 │ online │ 0% │ 20.2mb │ root │ disabled │
2024-05-03 13:23:39 runtipi | └────┴───────────┴─────────────┴─────────┴─────────┴──────────┴────────┴──────┴───────────┴──────────┴──────────┴──────────┴──────────┘
2024-05-03 13:23:32 runtipi-redis | 1:C 03 May 2024 17:23:32.854 * oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
2024-05-03 13:23:32 runtipi-redis | 1:C 03 May 2024 17:23:32.854 * Redis version=7.2.0, bits=64, commit=00000000, modified=0, pid=1, just started
2024-05-03 13:23:32 runtipi-redis | 1:C 03 May 2024 17:23:32.854 * Configuration loaded
2024-05-03 13:23:32 runtipi-redis | 1:M 03 May 2024 17:23:32.855 * monotonic clock: POSIX clock_gettime
2024-05-03 13:23:32 runtipi-redis | 1:M 03 May 2024 17:23:32.855 * Running mode=standalone, port=6379.
2024-05-03 13:23:32 runtipi-redis | 1:M 03 May 2024 17:23:32.855 * Server initialized
2024-05-03 13:23:32 runtipi-redis | 1:M 03 May 2024 17:23:32.856 * Loading RDB produced by version 7.2.0
2024-05-03 13:23:32 runtipi-redis | 1:M 03 May 2024 17:23:32.856 * RDB age 477580 seconds
2024-05-03 13:23:32 runtipi-redis | 1:M 03 May 2024 17:23:32.856 * RDB memory usage when created 0.83 Mb
2024-05-03 13:23:32 runtipi-redis | 1:M 03 May 2024 17:23:32.856 * Done loading RDB, keys loaded: 0, keys expired: 0.
2024-05-03 13:23:32 runtipi-redis | 1:M 03 May 2024 17:23:32.856 * DB loaded from disk: 0.001 seconds
2024-05-03 13:23:32 runtipi-redis | 1:M 03 May 2024 17:23:32.856 * Ready to accept connections tcp
2024-05-03 13:25:58 runtipi-reverse-proxy | time="2024-05-03T17:25:58Z" level=info msg="Configuration loaded from flags."
2024-05-03 13:23:33 runtipi-db |
2024-05-03 13:23:33 runtipi-db | PostgreSQL Database directory appears to contain a database; Skipping initialization
2024-05-03 13:23:33 runtipi-db |
2024-05-03 13:23:33 runtipi-db | 2024-05-03 17:23:33.107 UTC [1] LOG: starting PostgreSQL 14.11 (Debian 14.11-1.pgdg120+2) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit
2024-05-03 13:23:33 runtipi-db | 2024-05-03 17:23:33.107 UTC [1] LOG: listening on IPv4 address "0.0.0.0", port 5432
2024-05-03 13:23:33 runtipi-db | 2024-05-03 17:23:33.107 UTC [1] LOG: listening on IPv6 address "::", port 5432
2024-05-03 13:23:33 runtipi-db | 2024-05-03 17:23:33.112 UTC [1] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2024-05-03 13:23:33 runtipi-db | 2024-05-03 17:23:33.119 UTC [27] LOG: database system was shut down at 2024-04-28 04:43:52 UTC
2024-05-03 13:23:33 runtipi-db | 2024-05-03 17:23:33.126 UTC [1] LOG: database system is ready to accept connections
Traefic still does not want to start automatically, and when manually started, nothing is accessible still via whatever that IP the CLI spits out, as well as 127.0.0.1 or localhost:443.
Someone please for the love of blah help me.
from runtipi.
steveiliop56
commented on June 11, 2024
Hello @n0w33d,
Something is really wrong with your instance. To begin with some of your environment variables are not set, I would try restarting runtipi through the cli and test if the env file is regenerated correctly. Secondly because some major environment variables are not set it seems logical to me that the worker won't start because things like the jwt token are quite important. Lastly concerning redis the 192.168.x.x range is not something that a docker network would use, docker networks use some othe subnets like 172.18.x.x in my case, this could be some misconfiguration on your part if you played with docker and changed something or perhaps a broken install? I say all these because I use wsl 2 on windows 11 pro too and because I play a lot with it and reset it a lot I never face issues with installing and using tipi. If the issue persists I would recommend trying to reset the wsl app and/or reinstalling your selected wsl distro.
from runtipi.
Wraithers
commented on June 11, 2024
Hey, @n0w33d, this probably won't help, but sharing what happened for me.
Raspberry Pi 4B, 4GB RAM, Debian 12 Bookworm Lite OS
I used rsync to copy over the runtipi folder from my old SD card to my new SD card on my Raspberry Pi 4 and after installing Docker and trying to run sudo ./runtipi-cli start I ran into the same container runtipi is unhealthy issue.
Knowing that, in at least my case, all I really needed was the app-data & user-config folders from my old install, I wiped Runtipi from my new SD card and installed it with the install script fresh sudo curl -L https://setup.runtipi.io | sudo bash and this at least got me up and running with a clean, base install of Runtipi, no container runtipi is unhealthy issue.
After copying those folders back, reinstalling the apps and then restarting Runtipi, everything looks good 👍
from runtipi.
Related Issues (20)
- [REQUEST] adding "default" property for formfields HOT 5
- [BUG] After Update to 3.1.2 Runtipi cannnot start anymore! HOT 3
- [BUG] formfield type password length check HOT 8
- [BUG] Archivebox dead after update from 3.1.0 to 3.1.2 HOT 5
- [BUG] AppStore integration app search categories is not de-selectable HOT 3
- [REQUEST] IPV6 Support HOT 3
- [BUG] Fresh install - Safari - WS issue HOT 8
- [REQUEST] add a default basic-auth middleware to tipi HOT 1
- [BUG] docker of apps running, but not present in My Apps tab HOT 8
- [REQUEST] Allow users to attach volumes to containers HOT 2
- [BUG] When changing the global settings the .env of apps isnt updating HOT 1
- Pending restart (app) HOT 2
- [BUG] Cloudflared webUI is broken. HOT 1
- Add Brazilian Portuguese translation support HOT 1
- [BUG] Failed to copy system files HOT 2
- [REQUEST] runtipi-cli additions
- [BUG] runtipi-cli app update error
- Auto backup before app update
- [BUG] runtipi-cli error if executed outside its working directory
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from runtipi.