Problem n8n self-hosted server

Questions
1

I got a problem at my n8n self-hosted server, n8n goes offline and reconnects from time to time. I got this logs from the container:
n8n Task Broker ready on yyy.y.y.y, port 5679
Failed 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 production. Users are encouraged to deploy in external mode. See: Task runners | n8n Docs
[license SDK] Skipping renewal on init: license cert is not initialized
Registered runner “JS Task Runner” (UU-z7gPHHD0JUDog3JJhR)
Currently active workflows:
Teams → n8n (receive and persist) (ID: GsbS1N6eCj79VU1D)
[Recovery] Logs available, amended execution
(node:7) [DEP0040] DeprecationWarning: The punycode module is deprecated. Please use a userland alternative instead.
(Use node --trace-deprecation … to show where the warning was created)
[Recovery] Logs available, amended execution
[Recovery] Logs available, amended execution
[Recovery] Logs available, amended execution
[Recovery] Logs available, amended execution
Found unfinished executions: 3, 5, 23, 30, 61
This could be due to a crash of an active workflow or a restart of n8n
Version: 2.13.3
Building workflow dependency index…
Start Active Workflows:
Finished building workflow dependency index. Processed 1 draft workflows, 0 published workflows.
Activated workflow “Teams → n8n (receive and persist)” (ID: GsbS1N6eCj79VU1D)
Editor is now accessible via:
http://yy.yyy.yy.yy:5678
(node:7) [DEP0060] DeprecationWarning: The util._extend API is deprecated. Please use Object.assign() instead.
[init] ERROR: n8n no respondió a tiempo.
Last session crashed
Initializing n8n process
n8n ready on ::, port 5678
n8n Task Broker ready on yyy.y.y.y, port 5679
Failed 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 production. Users are encouraged to deploy in external mode. See: Task runners | n8n Docs
[license SDK] Skipping renewal on init: license cert is not initialized
Registered runner “JS Task Runner” (pb2V3-DdbDoDAuHIdnqy0)
Currently active workflows:
Teams → n8n (receive and persist) (ID: GsbS1N6eCj79VU1D)
[Recovery] Logs available, amended execution
(node:7) [DEP0040] DeprecationWarning: The punycode module is deprecated. Please use a userland alternative instead.
(Use node --trace-deprecation … to show where the warning was created)
[Recovery] Logs available, amended execution
[Recovery] Logs available, amended execution
[Recovery] Logs available, amended execution
[Recovery] Logs available, amended execution
Found unfinished executions: 3, 5, 23, 30, 61
This could be due to a crash of an active workflow or a restart of n8n
Version: 2.13.3
Building workflow dependency index…
Start Active Workflows:
Finished building workflow dependency index. Processed 1 draft workflows, 0 published workflows.
Activated workflow “Teams → n8n (receive and persist)” (ID: GsbS1N6eCj79VU1D)
i dont use python, the last message repeats the same like 5 more times

Describe the problem/error/question

What is the error message (if any)?

Please share your workflow

(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)

Share the output returned by the last node

Information on your n8n setup

  • n8n version:
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
  • Operating system:
2

hey @Ryutaro_Arimura when did the issue start happening? a friend also experienced similar issue

3

literally installed n8n on my server, published a workflow and started to restar the connection

4

This looks like a crash/restart loop, not a Python issue the Python warning can be ignored.

From your logs:

  • “Last session crashed”

  • “Found unfinished executions”

  • repeated restarts

This means your n8n instance is crashing and restarting continuously.

What’s likely causing it

  • An active workflow is crashing the process (your “Teams → n8n” workflow is a strong suspect)

  • Low server memory or CPU

  • Missing or improper restart configuration

What you should do

  1. Disable the active workflow temporarily
    Turn off the “Teams → n8n (receive and persist)” workflow and check if n8n stays stable. If it does, then that workflow is causing the crash.

  2. Set proper Docker restart policy
    Make sure your container includes:

restart: always

  1. Check server resources
    Low RAM/CPU can cause n8n to crash during execution. Monitor usage or upgrade if needed.

  2. Set execution mode for stability
    Add this environment variable:

EXECUTIONS_PROCESS=main
  1. Review workflow logic
    Check for things like infinite loops, large data processing, or too many simultaneous executions.

Important note

The “Python 3 is missing…” message is not the issue it’s optional and safe to ignore.

5

that ‘[init] ERROR: n8n no respondió a tiempo’ log is the key clue — it’s an initialization timeout, not a random crash. n8n starts, tries to activate the Teams workflow during boot, and hangs before the healthcheck completes. since you’re stuck in a restart loop and can’t reach the UI, you’ll need to stop the container and temporarily disable the workflow directly in the DB (set active = 0 in the workflow_entity table) before restarting. once it boots stable you can inspect the Teams workflow for any webhook registration or blocking startup logic.

6

That’s a really solid insight the initialization timeout explains the restart loop much better.

If n8n is hanging while activating the Teams workflow during startup, it makes sense that the healthcheck fails and the container keeps restarting.

Disabling the workflow directly in the database (active = 0) is a smart move in this case, especially since the UI isn’t accessible. That should allow n8n to boot normally so the workflow can be reviewed safely.

Once it’s stable, checking the workflow for things like webhook registration or any blocking logic during startup is definitely the right next step.