{"id":2611,"date":"2026-10-31T16:21:49","date_gmt":"2026-10-31T13:21:49","guid":{"rendered":"https:\/\/www.fibacloud.com\/community\/tutorials\/?p=2611"},"modified":"2026-10-31T16:21:49","modified_gmt":"2026-10-31T13:21:49","slug":"install-n8n-ubuntu-docker","status":"publish","type":"post","link":"https:\/\/www.fibacloud.com\/community\/tutorials\/en\/install-n8n-ubuntu-docker\/","title":{"rendered":"Install n8n on Ubuntu with Docker Compose and HTTPS"},"content":{"rendered":"<p>You can run n8n on your own Ubuntu VPS and use it through a domain you control. This guide brings together Docker Compose, PostgreSQL, Caddy and an external task runner. You will send an authenticated request over HTTPS, check that the workflow executes, and verify that its data survives container replacement and restoration from a backup.<\/p>\n<p>This setup suits users who want to manage their server and updates. The n8n Community edition can support your internal workflows; the server, domain and any external services have separate costs. Providing n8n access as a service to customers requires a separate look at the licence terms.<\/p>\n<h2 id=\"test-environment\">Test environment and scope<\/h2>\n<p>This installation was run on Ubuntu on 31 October 2026. The small sample workflow accepts an authenticated POST request, adds one to 41 in the Code node and returns JSON.<\/p>\n<table>\n<thead>\n<tr>\n<th>Item<\/th>\n<th>Value used in the test<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Operating system<\/td>\n<td>Ubuntu 24.04.5 LTS, amd64<\/td>\n<\/tr>\n<tr>\n<td>Server<\/td>\n<td>1 vCPU, approximately 1967 MiB RAM, 4 GiB swap<\/td>\n<\/tr>\n<tr>\n<td>Docker \/ Compose<\/td>\n<td>29.9.2 \/ 5.6.1<\/td>\n<\/tr>\n<tr>\n<td>Images used<\/td>\n<td>n8n and runners 2.45.7, PostgreSQL 17.11, Caddy 2.11.7; pinned by version and digest, with the pulled digests checked.<\/td>\n<\/tr>\n<tr>\n<td>External access<\/td>\n<td>TLS 1.3 with a trusted Let\u2019s Encrypt certificate; the initial IP restriction returned HTTP 403 for a disallowed address. Ports 5432, 5678, 5679 and 5680 were unreachable externally.<\/td>\n<\/tr>\n<tr>\n<td>Function and persistence<\/td>\n<td>The native three-node workflow, production webhook 403\/403\/200 checks, the same results after replacing n8n and runner containers, and credential recovery in a separate project with fresh volumes were verified.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>The external runner used a separate container with UID 1000 and a read-only root filesystem. On the restored copy, <code>external<\/code> mode and a JavaScript runner process matching the successful Code check were confirmed from configuration and logs.<\/p>\n<p>Login and webhook checks on the original installation used verified HTTPS. The restored copy published no host port: its webhook and login request with the saved owner account were tested over HTTP inside the container. That second check does not validate a new public HTTPS endpoint. Python, additional community nodes and heavy parallel load were outside this test.<\/p>\n<p>The examples use <code>n8n.example.com<\/code>, the administrator IP <code>203.0.113.10\/32<\/code>, and the project directory <code>\/opt\/n8n<\/code>. Replace the domain and IP with your own values. A RAM figure alone does not establish workflow or concurrent-user capacity: large files, execution overlap and the data each workflow processes all matter.<\/p>\n<p>This guide covers n8n\u2019s core workflows and the external runner used by the Code node. Assistant may appear in the application; this setup does not configure its model connection or sandbox.<\/p>\n<h2 id=\"prerequisites\">What you need before starting<\/h2>\n<ul>\n<li>An Ubuntu server with SSH and <code>sudo<\/code> access. For the initial connection, see <a href=\"https:\/\/www.fibacloud.com\/community\/tutorials\/en\/how-to-connect-to-a-remote-server-via-ssh\/\">connecting to a remote server over SSH<\/a>.<\/li>\n<li>Docker Engine and the Compose plugin. If needed, first complete our <a href=\"https:\/\/www.fibacloud.com\/community\/tutorials\/en\/how-to-deploy-an-application-with-docker-docker-installation-and-management\/\">Docker installation and application deployment guide<\/a>.<\/li>\n<li>A subdomain pointing to the server\u2019s public IP. Check its A record and make sure any AAAA record points to the correct IPv6 address.<\/li>\n<li>80\/TCP and 443\/TCP reaching the server. 443\/UDP supports Caddy\u2019s HTTP\/3 connections. Check both the provider firewall and the server\u2019s rules.<\/li>\n<li>The public IP of the computer you will use to create the initial owner account. Initial setup will be restricted to this address.<\/li>\n<\/ul>\n<div class=\"fc-code-example\">\n<pre><code>docker --version\ndocker compose version\nsudo ss -ltnup<\/code><\/pre>\n<\/div>\n<p>If <code>ss<\/code> shows another service using 80 or 443, resolve the port ownership before continuing. Stopping an existing Plesk, Apache or Nginx web service can interrupt other sites. This guide assumes an application server where Caddy can own those ports; adding n8n behind a panel-managed reverse proxy requires a different configuration.<\/p>\n<h2 id=\"architecture\">What each service does<\/h2>\n<table>\n<thead>\n<tr>\n<th>Service<\/th>\n<th>Purpose<\/th>\n<th>Storage and access<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Caddy<\/td>\n<td>HTTPS, certificate renewal and forwarding requests to n8n<\/td>\n<td>Only 80\/443 are published; certificate material persists in a volume.<\/td>\n<\/tr>\n<tr>\n<td>n8n<\/td>\n<td>Editor, webhooks and workflow management<\/td>\n<td>5678 stays within container networks; its <code>.n8n<\/code> directory persists.<\/td>\n<\/tr>\n<tr>\n<td>PostgreSQL<\/td>\n<td>Database for workflows, users and stored credentials<\/td>\n<td>5432 is not published; n8n connects with a separate database role.<\/td>\n<\/tr>\n<tr>\n<td>Task runner<\/td>\n<td>Running Code-node scripts in a separate container<\/td>\n<td>Authenticates to the n8n broker on 5679; receives neither the database password nor the n8n encryption key.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>The external runner follows n8n\u2019s recommended arrangement for executing code. Webhook and Edit Fields nodes do not themselves submit Code-runner tasks, but this installation includes the runner so that Code remains usable. n8n and its runner must have matching application versions; their image digests are different because they are different images. The <a href=\"https:\/\/docs.n8n.io\/deploy\/host-n8n\/configure-n8n\/set-up-task-runners.md\" rel=\"nofollow noopener\" target=\"_blank\">official task-runner guide<\/a> explains the components.<\/p>\n<h2 id=\"project-files\">Prepare the project directory and secrets<\/h2>\n<p>Create the files with the steps below or <a href=\"https:\/\/www.fibacloud.com\/community\/tutorials\/wp-content\/uploads\/2026\/10\/fibacloud-n8n-20261031\/n8n-compose.zip\">download the Compose configuration bundle<\/a>. It contains no real passwords: prepare your own domain, administrator IP and secrets. You can also use the <a href=\"https:\/\/www.fibacloud.com\/community\/tutorials\/wp-content\/uploads\/2026\/10\/fibacloud-n8n-20261031\/workflow.json\">sample webhook workflow JSON<\/a>; create its Header Auth credential in your own n8n instance.<\/p>\n<p>The following steps create a new installation under <code>\/opt\/n8n<\/code>. If you already use that directory, preserve the existing files rather than overwriting them. From this point the commands run in a root shell, with a private directory and file permissions.<\/p>\n<div class=\"fc-code-example\">\n<pre><code>sudo -i\ninstall -d -m 700 \/opt\/n8n\ncd \/opt\/n8n\numask 077<\/code><\/pre>\n<\/div>\n<p>Create <code>.env<\/code>. Set <code>N8N_HOST<\/code> to your domain and <code>BOOTSTRAP_ALLOWED_IP<\/code> to your actual public IP. Leaving the example IP in place will prevent you from reaching initial setup.<\/p>\n<div class=\"fc-code-example\">\n<pre><code>cat &gt; .env &lt;&lt;&#x27;ENV&#x27;\nCOMPOSE_PROJECT_NAME=n8n\nN8N_HOST=n8n.example.com\nBOOTSTRAP_ALLOWED_IP=203.0.113.10\/32\nGENERIC_TIMEZONE=Europe\/Istanbul\n\nPOSTGRES_ADMIN_PASSWORD=REPLACE_WITH_SEPARATE_RANDOM_64_HEX_CHARACTERS\nN8N_DB_PASSWORD=REPLACE_WITH_SEPARATE_RANDOM_64_HEX_CHARACTERS\nN8N_ENCRYPTION_KEY=REPLACE_WITH_SEPARATE_RANDOM_64_HEX_CHARACTERS_AND_KEEP_FOR_RESTORE\nN8N_RUNNERS_AUTH_TOKEN=REPLACE_WITH_SEPARATE_RANDOM_64_HEX_CHARACTERS\n\nN8N_IMAGE=docker.io\/n8nio\/n8n:2.45.7@sha256:9a8d8dcea75667496695d7810d7e1fe018a65efb36cc499d347f3931b3957b5d\nRUNNERS_IMAGE=docker.io\/n8nio\/runners:2.45.7@sha256:2f07088829b6a1df2b6a84746bb8b32c1eaef270315fb5466aa01b1045e9b300\nPOSTGRES_IMAGE=docker.io\/library\/postgres:17.11-bookworm@sha256:839fbb5a4942a7758dd93e18b42ea5649807491a0545b5eeeb8f0b8bb11857a5\nCADDY_IMAGE=docker.io\/library\/caddy:2.11.7-alpine@sha256:e70b164da81ef698b3ad19af799ea6086ce6d9e48ed4079eb9fe26f6fbf14ee5\nENV<\/code><\/pre>\n<\/div>\n<p>Generate four independent random secrets. This command replaces only values beginning with <code>REPLACE_WITH_<\/code> and does not print the resulting secrets. It leaves an already generated encryption key intact.<\/p>\n<div class=\"fc-code-example\">\n<pre><code>python3 - &lt;&lt;&#x27;PY&#x27;\nfrom pathlib import Path\nfrom secrets import token_hex\nimport re\n\npath = Path(&quot;.env&quot;)\ntext = path.read_text()\nkeys = (\n    &quot;POSTGRES_ADMIN_PASSWORD&quot;,\n    &quot;N8N_DB_PASSWORD&quot;,\n    &quot;N8N_ENCRYPTION_KEY&quot;,\n    &quot;N8N_RUNNERS_AUTH_TOKEN&quot;,\n)\nfor key in keys:\n    text = re.sub(\n        rf&quot;^{key}=REPLACE_WITH_[^\\n]*$&quot;,\n        lambda match: f&quot;{key}={token_hex(32)}&quot;,\n        text,\n        flags=re.MULTILINE,\n    )\nif &quot;REPLACE_WITH_&quot; in text:\n    raise SystemExit(&quot;Unreplaced placeholder in .env&quot;)\npath.write_text(text)\npath.chmod(0o600)\nPY<\/code><\/pre>\n<\/div>\n<p><code>N8N_ENCRYPTION_KEY<\/code> is required to decrypt stored n8n credentials. Preserve it alongside the database backup. Reinstalling the server does not make an existing database usable with a different key. Keep the real <code>.env<\/code> out of Git repositories, support messages and screenshots.<\/p>\n<h2 id=\"docker-compose\">Configure Docker Compose and PostgreSQL<\/h2>\n<p>The following file defines services, health checks and persistent volumes. Images are pinned by version and digest so replacing a container does not silently select a different image. Updates remain an explicit maintenance step.<\/p>\n<div class=\"fc-code-example\">\n<pre><code>cat &gt; compose.yml &lt;&lt;&#x27;YAML&#x27;\nservices:\n  postgres:\n    image: ${POSTGRES_IMAGE:?Set POSTGRES_IMAGE in .env}\n    restart: unless-stopped\n    environment:\n      POSTGRES_USER: postgres\n      POSTGRES_DB: n8n\n      POSTGRES_PASSWORD: ${POSTGRES_ADMIN_PASSWORD:?Generate POSTGRES_ADMIN_PASSWORD}\n      N8N_DB_PASSWORD: ${N8N_DB_PASSWORD:?Generate N8N_DB_PASSWORD}\n    volumes:\n      - postgres_data:\/var\/lib\/postgresql\/data\n      - .\/initdb.sh:\/docker-entrypoint-initdb.d\/10-n8n.sh:ro\n    networks:\n      - database\n    healthcheck:\n      test: [&quot;CMD&quot;, &quot;pg_isready&quot;, &quot;-h&quot;, &quot;127.0.0.1&quot;, &quot;-U&quot;, &quot;postgres&quot;, &quot;-d&quot;, &quot;n8n&quot;]\n      interval: 10s\n      timeout: 5s\n      retries: 12\n      start_period: 30s\n    logging:\n      driver: json-file\n      options:\n        max-size: &quot;10m&quot;\n        max-file: &quot;3&quot;\n\n  n8n:\n    image: ${N8N_IMAGE:?Set N8N_IMAGE in .env}\n    restart: unless-stopped\n    depends_on:\n      postgres:\n        condition: service_healthy\n    environment:\n      DB_TYPE: postgresdb\n      DB_POSTGRESDB_HOST: postgres\n      DB_POSTGRESDB_PORT: &quot;5432&quot;\n      DB_POSTGRESDB_DATABASE: n8n\n      DB_POSTGRESDB_USER: n8n_app\n      DB_POSTGRESDB_PASSWORD: ${N8N_DB_PASSWORD:?Generate N8N_DB_PASSWORD}\n      N8N_ENCRYPTION_KEY: ${N8N_ENCRYPTION_KEY:?Generate and preserve N8N_ENCRYPTION_KEY}\n      N8N_HOST: ${N8N_HOST:?Set the DNS hostname}\n      N8N_PORT: &quot;5678&quot;\n      N8N_LISTEN_ADDRESS: &quot;0.0.0.0&quot;\n      N8N_PROTOCOL: https\n      N8N_EDITOR_BASE_URL: https:\/\/${N8N_HOST:?Set the DNS hostname}\/\n      N8N_WEBHOOK_URL: https:\/\/${N8N_HOST:?Set the DNS hostname}\/\n      N8N_PROXY_HOPS: &quot;1&quot;\n      GENERIC_TIMEZONE: ${GENERIC_TIMEZONE:-Europe\/Istanbul}\n      TZ: ${GENERIC_TIMEZONE:-Europe\/Istanbul}\n      N8N_ENFORCE_SETTINGS_FILE_PERMISSIONS: &quot;true&quot;\n      N8N_BLOCK_ENV_ACCESS_IN_NODE: &quot;true&quot;\n      N8N_AI_ENABLED: &quot;false&quot;\n      N8N_RUNNERS_MODE: external\n      N8N_RUNNERS_BROKER_LISTEN_ADDRESS: &quot;0.0.0.0&quot;\n      N8N_RUNNERS_AUTH_TOKEN: ${N8N_RUNNERS_AUTH_TOKEN:?Generate N8N_RUNNERS_AUTH_TOKEN}\n      EXECUTIONS_DATA_PRUNE: &quot;true&quot;\n      EXECUTIONS_DATA_MAX_AGE: &quot;168&quot;\n    volumes:\n      - n8n_data:\/home\/node\/.n8n\n    networks:\n      - edge\n      - database\n      - runner\n    healthcheck:\n      test:\n        - CMD\n        - node\n        - -e\n        - &quot;fetch(&#x27;http:\/\/127.0.0.1:5678\/healthz\/readiness&#x27;, {signal: AbortSignal.timeout(4000)}).then(r =&gt; process.exit(r.ok ? 0 : 1)).catch(() =&gt; process.exit(1))&quot;\n      interval: 15s\n      timeout: 5s\n      retries: 12\n      start_period: 120s\n    stop_grace_period: 60s\n    logging:\n      driver: json-file\n      options:\n        max-size: &quot;10m&quot;\n        max-file: &quot;3&quot;\n\n  task-runners:\n    image: ${RUNNERS_IMAGE:?Set the runner image matching the n8n version}\n    restart: unless-stopped\n    depends_on:\n      n8n:\n        condition: service_healthy\n    environment:\n      N8N_RUNNERS_TASK_BROKER_URI: http:\/\/n8n:5679\n      N8N_RUNNERS_AUTH_TOKEN: ${N8N_RUNNERS_AUTH_TOKEN:?Generate N8N_RUNNERS_AUTH_TOKEN}\n      N8N_RUNNERS_AUTO_SHUTDOWN_TIMEOUT: &quot;15&quot;\n      GENERIC_TIMEZONE: ${GENERIC_TIMEZONE:-Europe\/Istanbul}\n    read_only: true\n    tmpfs:\n      - \/tmp:rw,noexec,nosuid,size=64m\n    cap_drop:\n      - ALL\n    security_opt:\n      - no-new-privileges:true\n    networks:\n      - runner\n    logging:\n      driver: json-file\n      options:\n        max-size: &quot;10m&quot;\n        max-file: &quot;3&quot;\n\n  caddy:\n    image: ${CADDY_IMAGE:?Set CADDY_IMAGE in .env}\n    restart: unless-stopped\n    depends_on:\n      n8n:\n        condition: service_healthy\n    environment:\n      N8N_HOST: ${N8N_HOST:?Set the DNS hostname}\n      BOOTSTRAP_ALLOWED_IP: ${BOOTSTRAP_ALLOWED_IP:?Set the initial operator public IP}\n    ports:\n      - &quot;80:80&quot;\n      - &quot;443:443&quot;\n      - &quot;443:443\/udp&quot;\n    volumes:\n      - .\/Caddyfile:\/etc\/caddy\/Caddyfile:ro\n      - caddy_data:\/data\n      - caddy_config:\/config\n    networks:\n      - edge\n    logging:\n      driver: json-file\n      options:\n        max-size: &quot;10m&quot;\n        max-file: &quot;3&quot;\n\nvolumes:\n  postgres_data:\n  n8n_data:\n  caddy_data:\n  caddy_config:\n\nnetworks:\n  edge:\n  database:\n    internal: true\n  runner:\n    internal: true\nYAML<\/code><\/pre>\n<\/div>\n<p>n8n does not need a PostgreSQL superuser account. On the database\u2019s first startup, create <code>n8n_app<\/code> as the owner of its own database:<\/p>\n<div class=\"fc-code-example\">\n<pre><code>cat &gt; initdb.sh &lt;&lt;&#x27;SH&#x27;\n#!\/bin\/sh\nset -eu\n\n# Runs only when postgres_data is first initialized. Identifiers are fixed;\n# psql safely quotes the application password as a SQL literal.\n: &quot;${N8N_DB_PASSWORD:?N8N_DB_PASSWORD must be set}&quot;\npsql --username &quot;$POSTGRES_USER&quot; --dbname &quot;$POSTGRES_DB&quot; \\\n  --set=ON_ERROR_STOP=1 --set=n8n_password=&quot;$N8N_DB_PASSWORD&quot; &lt;&lt;&#x27;SQL&#x27;\nCREATE ROLE n8n_app WITH LOGIN PASSWORD :&#x27;n8n_password&#x27; NOSUPERUSER NOCREATEDB NOCREATEROLE;\nALTER DATABASE n8n OWNER TO n8n_app;\nGRANT ALL ON SCHEMA public TO n8n_app;\nSQL\nSH\nchmod 644 initdb.sh<\/code><\/pre>\n<\/div>\n<p>This initialization script runs only when the PostgreSQL volume is empty. Editing a password in <code>.env<\/code> later does not automatically change an existing PostgreSQL role\u2019s password; apply a password change to both PostgreSQL and n8n together.<\/p>\n<p>None of the three application ports is published on the host, so the editor, broker and database do not gain a direct internet entry point. The runner belongs only to its private network, while n8n retains outbound access for normal service connections. The database\u2019s protection therefore does not depend on assuming that a host firewall blocks Docker-published ports.<\/p>\n<h2 id=\"https-owner-setup\">Enable HTTPS and protect initial owner setup<\/h2>\n<p>Save the normal Caddy configuration as <code>Caddyfile.final<\/code>. Caddy obtains and renews a certificate for the hostname and redirects HTTP to HTTPS. Its persistent <code>\/data<\/code> volume also holds certificate keys. The <a href=\"https:\/\/caddyserver.com\/docs\/automatic-https\" rel=\"nofollow noopener\" target=\"_blank\">automatic HTTPS requirements<\/a> include correct DNS and the relevant ports reaching Caddy.<\/p>\n<div class=\"fc-code-example\">\n<pre><code>cat &gt; Caddyfile.final &lt;&lt;&#x27;CADDY&#x27;\n{$N8N_HOST} {\n    reverse_proxy n8n:5678\n}\nCADDY<\/code><\/pre>\n<\/div>\n<p>For the first start, use the following active configuration instead. It restricts the initial n8n owner-account screen to your IP while Caddy continues to handle certificate validation. Point the hostname directly at the server without an unconfigured CDN or proxy in front of it: this matcher uses the connecting client\u2019s address.<\/p>\n<div class=\"fc-code-example\">\n<pre><code>cat &gt; Caddyfile &lt;&lt;&#x27;CADDY&#x27;\n{$N8N_HOST} {\n    @notOperator not remote_ip {$BOOTSTRAP_ALLOWED_IP}\n    respond @notOperator &quot;Initial setup is restricted.&quot; 403\n    reverse_proxy n8n:5678\n}\nCADDY<\/code><\/pre>\n<\/div>\n<p>Validate the configuration, pull the images and start the services. A fully expanded <code>docker compose config<\/code> can expose passwords, so use <code>--quiet<\/code> here.<\/p>\n<div class=\"fc-code-example\">\n<pre><code>docker compose config --quiet\ndocker compose pull\ndocker compose run --rm --no-deps caddy caddy validate --config \/etc\/caddy\/Caddyfile --adapter caddyfile\ndocker compose up -d\ndocker compose ps<\/code><\/pre>\n<\/div>\n<p>On first startup, PostgreSQL initializes and n8n applies database migrations. Check <code>docker compose ps<\/code> for healthy PostgreSQL and n8n services and a running task runner. To inspect versions and recent application messages:<\/p>\n<div class=\"fc-code-example\">\n<pre><code>docker compose exec n8n n8n --version\ndocker compose exec postgres psql -U postgres -d n8n -c &#x27;SELECT version();&#x27;\ndocker compose exec caddy caddy version\ndocker compose logs --tail=60 n8n task-runners<\/code><\/pre>\n<\/div>\n<p>Open <code>https:\/\/n8n.example.com<\/code> from the allowed connection. A request from a different network should receive 403 at this stage. On <strong>Set up owner account<\/strong>, enter your email, name and a strong password, then select <strong>Next<\/strong>. On <strong>Customize n8n to you<\/strong>, you can leave the optional questions unanswered and select <strong>Get started<\/strong>. If the free licence-key offer appears, choose <strong>Skip<\/strong> to continue with this setup.<\/p>\n<figure><a href=\"https:\/\/www.fibacloud.com\/community\/tutorials\/wp-content\/uploads\/2026\/10\/fibacloud-n8n-20261031\/owner-setup.webp\"><img loading=\"lazy\" src=\"https:\/\/www.fibacloud.com\/community\/tutorials\/wp-content\/uploads\/2026\/10\/fibacloud-n8n-20261031\/owner-setup.webp\" width=\"440\" height=\"680\"  decoding=\"async\" alt=\"n8n owner-account setup with email and password hidden\"><\/a><figcaption>Create the initial owner account while the IP restriction is active. Email and password are hidden in this example.<\/figcaption><\/figure>\n<p>If the first screen is <strong>Assistant Preview<\/strong>, choose <strong>Turn off for this instance<\/strong> and confirm the <strong>Turn off n8n Assistant<\/strong> dialog to continue to the workflow editor used in this guide. Then open the same domain in a private browser window and confirm that you can use <strong>Sign in<\/strong> with the email and password you just created. Once owner setup and login are confirmed, switch to the normal proxy configuration:<\/p>\n<figure><a href=\"https:\/\/www.fibacloud.com\/community\/tutorials\/wp-content\/uploads\/2026\/10\/fibacloud-n8n-20261031\/sign-in.webp\"><img loading=\"lazy\" src=\"https:\/\/www.fibacloud.com\/community\/tutorials\/wp-content\/uploads\/2026\/10\/fibacloud-n8n-20261031\/sign-in.webp\" width=\"440\" height=\"470\"  decoding=\"async\" alt=\"n8n Sign in screen with email and password fields\"><\/a><figcaption>Verify login from a new private browser window.<\/figcaption><\/figure>\n<div class=\"fc-code-example\">\n<pre><code>cp Caddyfile.final Caddyfile\ndocker compose exec caddy caddy reload --config \/etc\/caddy\/Caddyfile --adapter caddyfile<\/code><\/pre>\n<\/div>\n<p><code>cp<\/code> updates the existing file\u2019s contents and preserves the file Caddy sees through its bind mount. If you use an atomic rename instead, recreate the Caddy container so it does not retain the old file. The public site should now show n8n\u2019s login screen rather than an unclaimed owner-setup screen.<\/p>\n<div class=\"fc-code-example\">\n<pre><code>curl -I http:\/\/n8n.example.com\/\ncurl -I https:\/\/n8n.example.com\/<\/code><\/pre>\n<\/div>\n<p>Run the HTTPS check without <code>-k<\/code>; disabling certificate verification does not establish valid TLS. Caddy handles the required <code>X-Forwarded-*<\/code> headers and WebSocket upgrades. For this single-proxy arrangement, <code>N8N_PROXY_HOPS=1<\/code> and <code>N8N_WEBHOOK_URL=https:\/\/your-domain\/<\/code> match the request path. The old <code>WEBHOOK_URL<\/code> setting found in earlier examples is deprecated.<\/p>\n<h2 id=\"authenticated-webhook\">Run your first authenticated webhook<\/h2>\n<p>A working login page is only the start. Use three nodes to check HTTPS ingress, stored credentials, workflow execution and the external Code runner together: <strong>Webhook \u2192 Code \u2192 Respond to Webhook<\/strong>.<\/p>\n<p>Create a separate key for webhook requests. The command refuses to overwrite an existing header file:<\/p>\n<div class=\"fc-code-example\">\n<pre><code>install -d -m 700 \/opt\/n8n\/secrets\npython3 - &lt;&lt;&#x27;PY&#x27;\nfrom pathlib import Path\nfrom secrets import token_hex\n\npath = Path(&quot;\/opt\/n8n\/secrets\/webhook-header.txt&quot;)\nwith path.open(&quot;x&quot;) as output:\n    output.write(&quot;Authorization: Bearer &quot; + token_hex(32) + &quot;\\n&quot;)\npath.chmod(0o600)\nPY<\/code><\/pre>\n<\/div>\n<p>To use the downloaded example JSON, choose <strong>Build a workflow<\/strong> in the workspace. Open the three-dot menu at the top and select <strong>Import \u2192 From file<\/strong>. If the <strong>Importing this from an AI tool?<\/strong> offer appears, select <strong>Skip<\/strong>; this example needs no MCP connection. When all three nodes appear, save with <strong>Ctrl+S<\/strong>.<\/p>\n<p>Open the Webhook node in the editor, or add it if building from scratch. Set HTTP Method to <strong>POST<\/strong>, Path to <code>fc-n8n-runner-check<\/code>, and Authentication to <strong>Header Auth<\/strong>. Select <strong>Connect to Header Auth<\/strong> to create its credential. Use Name <code>Authorization<\/code> and the value beginning with <code>Bearer <\/code> from your private file, then select <strong>Save<\/strong>. Read it only in your own secure terminal and transfer it to the HTTPS interface; do not put it in shared logs or screenshots. Webhook execution data can show request headers and this value; do not assume it is automatically hidden.<\/p>\n<p>Set the Webhook response option to <strong>Using Respond to Webhook Node<\/strong>. Add a Code node with JavaScript and <strong>Run Once for All Items<\/strong>, then enter:<\/p>\n<div class=\"fc-code-example\">\n<pre><code>const body = $input.first().json.body;\nreturn [{\n  json: {\n    ok: true,\n    received: String(body.message ?? &#x27;&#x27;),\n    result: Number(body.value) + 1\n  }\n}];<\/code><\/pre>\n<\/div>\n<p>For Respond to Webhook, choose <strong>First Incoming Item<\/strong> and HTTP 200; disable streaming for this simple JSON response. We deliberately return only selected fields, so request headers and the authentication value are not echoed back.<\/p>\n<p>Copy the address from the Webhook\u2019s <strong>Test URL<\/strong> tab, close the node panel and save the workflow. To test all three nodes, select <strong>Execute<\/strong> at the bottom of the canvas and wait for <strong>Waiting for you to call the Test URL<\/strong>. The node\u2019s <strong>Listen for test event<\/strong> action tests only the Webhook: in this version, it returned HTTP 200 with an empty body and did not run Code or the response node. Send the following request while the full workflow is listening, adjusting its domain and path to the copied URL:<\/p>\n<div class=\"fc-code-example\">\n<pre><code>curl --fail-with-body --silent --show-error \\\n  --header @\/opt\/n8n\/secrets\/webhook-header.txt \\\n  --header &#x27;Content-Type: application\/json&#x27; \\\n  --data &#x27;{&quot;value&quot;:41,&quot;message&quot;:&quot;fibacloud-lab&quot;}&#x27; \\\n  &#x27;https:\/\/n8n.example.com\/webhook-test\/fc-n8n-runner-check&#x27;<\/code><\/pre>\n<\/div>\n<p>The full workflow test returned this response, which you should also expect from your installation:<\/p>\n<div class=\"fc-code-example\">\n<pre><code>{&quot;ok&quot;:true,&quot;received&quot;:&quot;fibacloud-lab&quot;,&quot;result&quot;:42}<\/code><\/pre>\n<\/div>\n<figure><a href=\"https:\/\/www.fibacloud.com\/community\/tutorials\/wp-content\/uploads\/2026\/10\/fibacloud-n8n-20261031\/code-result.webp\"><img loading=\"lazy\" src=\"https:\/\/www.fibacloud.com\/community\/tutorials\/wp-content\/uploads\/2026\/10\/fibacloud-n8n-20261031\/code-result.webp\" width=\"1015\" height=\"485\"  decoding=\"async\" alt=\"n8n Code node JavaScript and output showing ok true, received fibacloud-lab and result 42\"><\/a><figcaption>In the real full-workflow test, Code converted the input 41 to the result 42. This crop shows only the script and selected response fields.<\/figcaption><\/figure>\n<p>The Test URL works while its test listener is active. For a persistent webhook, select <strong>Publish<\/strong> at the top, enter a version name in <strong>Publish workflow<\/strong>, then select <strong>Publish<\/strong> again. Dismiss <strong>Workflow published<\/strong> with <strong>Got it<\/strong>; the toolbar should show <strong>Published<\/strong>. Copy the address from the Webhook\u2019s <strong>Production URL<\/strong> tab. Production requests do not require the test listener.<\/p>\n<figure><a href=\"https:\/\/www.fibacloud.com\/community\/tutorials\/wp-content\/uploads\/2026\/10\/fibacloud-n8n-20261031\/workflow.webp\"><img loading=\"lazy\" src=\"https:\/\/www.fibacloud.com\/community\/tutorials\/wp-content\/uploads\/2026\/10\/fibacloud-n8n-20261031\/workflow.webp\" width=\"1440\" height=\"1080\"  decoding=\"async\" alt=\"Published workflow with Webhook, Code and Respond to Webhook nodes\"><\/a><figcaption>The published three-node example. Select the image to open its full size.<\/figcaption><\/figure>\n<div class=\"fc-code-example\">\n<pre><code>curl --fail-with-body --silent --show-error \\\n  --header @\/opt\/n8n\/secrets\/webhook-header.txt \\\n  --header &#x27;Content-Type: application\/json&#x27; \\\n  --data &#x27;{&quot;value&quot;:41,&quot;message&quot;:&quot;fibacloud-lab&quot;}&#x27; \\\n  &#x27;https:\/\/n8n.example.com\/webhook\/fc-n8n-runner-check&#x27;<\/code><\/pre>\n<\/div>\n<p>After the production request, open <strong>Executions<\/strong> and check that the new run shows <strong>Succeeded<\/strong>; production results do not automatically replace the editor\u2019s earlier test output. Also send requests to the same production URL with no key and with an incorrect key:<\/p>\n<div class=\"fc-code-example\">\n<pre><code>curl --silent --show-error --output \/dev\/null --write-out &#x27;%{http_code}\\n&#x27; \\\n  --header &#x27;Content-Type: application\/json&#x27; \\\n  --data &#x27;{&quot;value&quot;:41,&quot;message&quot;:&quot;fibacloud-lab&quot;}&#x27; \\\n  &#x27;https:\/\/n8n.example.com\/webhook\/fc-n8n-runner-check&#x27;\n\ncurl --silent --show-error --output \/dev\/null --write-out &#x27;%{http_code}\\n&#x27; \\\n  --header &#x27;Authorization: Bearer invalid-test-value&#x27; \\\n  --header &#x27;Content-Type: application\/json&#x27; \\\n  --data &#x27;{&quot;value&quot;:41,&quot;message&quot;:&quot;fibacloud-lab&quot;}&#x27; \\\n  &#x27;https:\/\/n8n.example.com\/webhook\/fc-n8n-runner-check&#x27;<\/code><\/pre>\n<\/div>\n<p>Both requests were rejected with HTTP <strong>403<\/strong> in this lab. The correct key returned HTTP <strong>200<\/strong> and the JSON above. Check the successful JSON response and the rejection status codes together on your own installation. Being logged into the editor does not automatically authorize an external webhook request; Header Auth protects this endpoint separately. See the <a href=\"https:\/\/docs.n8n.io\/integrations\/builtin\/credentials\/webhook\" rel=\"nofollow noopener\" target=\"_blank\">webhook credential documentation<\/a> for supported methods.<\/p>\n<p>When you only need to add or rename fields, use Edit Fields instead of Code. Mapping a <code>received<\/code> field to <code>{{ $json.body.message }}<\/code>, for example, does not require a custom script. We use Code here to check that the external runner actually executes a task.<\/p>\n<h2 id=\"persistence-resources\">Check persistence and resource use<\/h2>\n<p>After saving the workflow, recreate n8n and the runner without deleting volumes:<\/p>\n<div class=\"fc-code-example\">\n<pre><code>docker compose up -d --no-deps --force-recreate --wait --wait-timeout 240 n8n task-runners\ndocker compose ps<\/code><\/pre>\n<\/div>\n<p>Log in again and repeat the production webhook request with the same key. The workflow, publication state and credential should still be available. Then observe memory both at rest and during the small sample execution:<\/p>\n<div class=\"fc-code-example\">\n<pre><code>free -h\ndocker stats --no-stream\ndocker compose ps<\/code><\/pre>\n<\/div>\n<p>This is not a load test. Large JSON arrays, files, long-running Code nodes and parallel workflows use resources differently. If memory is insufficient, first inspect restarts, OOM events and workflow data sizes. One successful small execution is not a production capacity guarantee.<\/p>\n<p>The following <code>docker stats --no-stream<\/code> values are one snapshot taken after the small sample workflow. At that point the host was using approximately 385 MiB of swap. These figures do not represent peak demand or establish production capacity for a 2 GB server.<\/p>\n<table>\n<thead>\n<tr>\n<th>Service<\/th>\n<th>RAM snapshot after the workflow<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>n8n<\/td>\n<td>443.6 MiB<\/td>\n<\/tr>\n<tr>\n<td>Task runner<\/td>\n<td>90.16 MiB<\/td>\n<\/tr>\n<tr>\n<td>PostgreSQL<\/td>\n<td>64.1 MiB<\/td>\n<\/tr>\n<tr>\n<td>Caddy<\/td>\n<td>58.86 MiB<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h2 id=\"backup-restore\">Back up the instance and restore it separately<\/h2>\n<p>A recoverable n8n backup combines PostgreSQL, the <code>n8n_data<\/code> volume, the unchanged <code>N8N_ENCRYPTION_KEY<\/code> and deployment files. Preserving Caddy certificate data also avoids unnecessary certificate requests during recovery. Exporting workflow JSON alone does not preserve all users, credentials and instance settings.<\/p>\n<p>Place <code>maintenance.py<\/code> from the downloadable bundle at <code>\/opt\/n8n\/maintenance.py<\/code>; do not overwrite your existing <code>.env<\/code> with the example file. It runs in a root shell with Python 3 and Docker access. The backup destination must be a new directory; change its date or name for later backups.<\/p>\n<p>The script stops Caddy, n8n and the runner, then takes a logical <code>pg_dump<\/code> backup while PostgreSQL stays running. It saves the n8n\/Caddy volumes and four configuration files, records hashes for eight backup files in <code>manifest.json<\/code>, then attempts to restart the original services. It does not archive the live PostgreSQL data directory. The backup contains passwords, stored credentials and certificate keys; keep it private.<\/p>\n<p>To avoid running two installations together on this small server, stop the original project again after the backup finishes. The interface and webhooks remain unavailable until the restoration check is complete, so allow a maintenance window.<\/p>\n<div class=\"fc-code-example\">\n<pre><code>cd \/opt\/n8n\npython3 maintenance.py backup \/root\/n8n-backup-20261031\ndocker compose stop<\/code><\/pre>\n<\/div>\n<p>The following restoration uses a new directory, a different project name and fresh volumes. The script verifies hashes and refuses to overwrite an existing destination, project data or volume. Stored credentials cannot be used if the encryption key is missing or does not match the database.<\/p>\n<div class=\"fc-code-example\">\n<pre><code>python3 maintenance.py restore \\\n  \/root\/n8n-backup-20261031 \\\n  \/opt\/n8n-restore \\\n  --project n8n-restore<\/code><\/pre>\n<\/div>\n<p>The copy starts only PostgreSQL, n8n and the runner. Caddy stays stopped, no host port is published and all attached Compose networks remain <code>internal<\/code>. This does not create a new public HTTPS deployment. Network isolation does not disable timers; workflows can still change the copy\u2019s own database. Use the following check only with this guide\u2019s controlled webhook workflow.<\/p>\n<p>Pass the original header file through standard input to check authentication from inside the copy. The command does not print the key or put it in process arguments. It expects rejection for missing\/incorrect keys and HTTP 200 with <code>result: 42<\/code> for the correct key:<\/p>\n<div class=\"fc-code-example\">\n<pre><code>cd \/opt\/n8n-restore\ndocker compose -f compose.yml -f restore.override.json exec -T n8n node -e &#x27;\nconst prefix = &quot;Authorization: &quot;;\nconst line = require(&quot;node:fs&quot;).readFileSync(0, &quot;utf8&quot;).trim();\nif (!line.startsWith(prefix)) throw new Error(&quot;Invalid header file&quot;);\nconst savedHeader = line.slice(prefix.length);\n(async () =&gt; {\n  for (const [name, key] of [\n    [&quot;missing&quot;, null],\n    [&quot;wrong&quot;, &quot;Bearer invalid-test-value&quot;],\n    [&quot;valid&quot;, savedHeader],\n  ]) {\n    const headers = { &quot;Content-Type&quot;: &quot;application\/json&quot; };\n    if (key) headers.Authorization = key;\n    const response = await fetch(\n      &quot;http:\/\/127.0.0.1:5678\/webhook\/fc-n8n-runner-check&quot;,\n      {\n        method: &quot;POST&quot;,\n        headers,\n        body: JSON.stringify({ value: 41, message: &quot;fibacloud-lab&quot; }),\n        signal: AbortSignal.timeout(90000),\n      },\n    );\n    const body = await response.text();\n    console.log(JSON.stringify({ case: name, status: response.status, body }));\n    if (name === &quot;valid&quot;) {\n      const result = JSON.parse(body);\n      if (response.status !== 200 || result.ok !== true ||\n          result.received !== &quot;fibacloud-lab&quot; || result.result !== 42) {\n        throw new Error(&quot;Restored webhook result did not match&quot;);\n      }\n    } else if (![401, 403].includes(response.status)) {\n      throw new Error(&quot;Unauthenticated request was not rejected&quot;);\n    }\n  }\n})().catch(error =&gt; {\n  console.error(error.message);\n  process.exitCode = 1;\n});\n&#x27; &lt; \/opt\/n8n\/secrets\/webhook-header.txt<\/code><\/pre>\n<\/div>\n<p>In the lab, the restored copy returned HTTP 403 for missing and incorrect keys, and HTTP 200 with the same JSON for the original key. A login request with the saved owner account also returned 200. The separate project, fresh volumes, absent host ports and internal networks were checked against actual Docker state. This demonstrated recovery of the database and encryption key together, beyond merely starting containers. Keep the private <code>restore-receipt.json<\/code> alongside the backup manifest.<\/p>\n<p>When the check is complete, stop the copy and restart the original installation. Include both <code>-f<\/code> files for the copy so its restoration network and service settings remain applied. If the check fails, still bring the original project back and investigate without deleting its volumes:<\/p>\n<div class=\"fc-code-example\">\n<pre><code>cd \/opt\/n8n-restore\ndocker compose -f compose.yml -f restore.override.json stop\n\ncd \/opt\/n8n\ndocker compose up -d --wait --wait-timeout 240\ndocker compose ps<\/code><\/pre>\n<\/div>\n<p>Recheck login and the authenticated production webhook on the original HTTPS address. Keep another backup copy away from the server, encrypted and with restricted access. An archive on the same disk can help recover from a bad update; it cannot by itself cover complete server or disk loss.<\/p>\n<h2 id=\"updates\">Maintain n8n and the surrounding services<\/h2>\n<p>Complete the backup and restore check first. Read the <a href=\"https:\/\/github.com\/n8n-io\/n8n\/releases\" rel=\"nofollow noopener\" target=\"_blank\">n8n release notes<\/a>, including migration instructions for a major-version change. Update both n8n and the runner references in <code>.env<\/code> to the same new application version, each with its own verified image digest.<\/p>\n<div class=\"fc-code-example\">\n<pre><code>docker compose pull\ndocker compose up -d\ndocker compose ps<\/code><\/pre>\n<\/div>\n<p>Recheck HTTPS login and the authenticated webhook. <code>docker compose restart<\/code> alone does not apply a new image or changed environment. If an update ran database migrations, starting the old image is not necessarily a valid rollback; restore the pre-update backup with compatible images when required.<\/p>\n<p>Track PostgreSQL maintenance releases within the selected major version. Do not treat PostgreSQL 17 to 18 as a routine image-tag edit: major upgrades need a data migration method. The <a href=\"https:\/\/www.postgresql.org\/support\/versioning\/\" rel=\"nofollow noopener\" target=\"_blank\">PostgreSQL version policy<\/a> explains support periods and the difference between minor and major updates. Include Caddy\u2019s maintenance releases in the same plan.<\/p>\n<p>This Compose example rotates Docker logs at 10 MB per file with three files, enables n8n execution-data pruning and sets its age threshold to 168 hours. Choose retention to fit your investigation and data requirements; saved execution data can contain customer information.<\/p>\n<h2 id=\"troubleshooting\">Common problems<\/h2>\n<table>\n<thead>\n<tr>\n<th>Symptom<\/th>\n<th>First check<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>403 during initial setup<\/td>\n<td>Does <code>BOOTSTRAP_ALLOWED_IP<\/code> match your current connection? A VPN or network change can alter your public IP.<\/td>\n<\/tr>\n<tr>\n<td>502 Bad Gateway<\/td>\n<td>Is n8n healthy, is its PostgreSQL connection established, and do Caddy and n8n share the <code>edge<\/code> network?<\/td>\n<\/tr>\n<tr>\n<td>Certificate cannot be issued<\/td>\n<td>Are A\/AAAA records correct, do 80\/443 reach Caddy, and is another service using either port?<\/td>\n<\/tr>\n<tr>\n<td>Webhook returns 404<\/td>\n<td>Are you using the correct Test or Production URL? Is its test listener active or the workflow published? Is the method POST?<\/td>\n<\/tr>\n<tr>\n<td>Authentication rejected<\/td>\n<td>Is the header named <code>Authorization<\/code>, does its value include the <code>Bearer <\/code> prefix and space, and is the correct credential selected?<\/td>\n<\/tr>\n<tr>\n<td>Code execution waits<\/td>\n<td>Is the runner running with the matching n8n version? Do the broker URI and shared token match?<\/td>\n<\/tr>\n<tr>\n<td>Data appears missing after restart<\/td>\n<td>Are you using the same Compose project name and volumes? Running from another directory may create a different project.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<div class=\"fc-code-example\">\n<pre><code>docker compose ps\ndocker compose logs --tail=80 n8n task-runners caddy\ndf -h<\/code><\/pre>\n<\/div>\n<p>Review logs for request contents and secrets before sharing them. <code>docker compose down -v<\/code> deletes persistent volumes as well; it is not a routine restart command.<\/p>\n<h2 id=\"faq\">Frequently asked questions<\/h2>\n<h3 id=\"is-n8n-free\">Is self-hosted n8n free?<\/h3>\n<p>The Community edition is available under the Sustainable Use License. Internal use where people in your organization create workflows differs from allowing external customers to build or configure workflows or access n8n as a service. A commercial licence or external API fees may apply in addition to hosting. Compare your intended use with <a href=\"https:\/\/support.n8n.io\/article\/can-i-use-your-license-for-my-use-case\" rel=\"nofollow noopener\" target=\"_blank\">n8n\u2019s current licence explanation<\/a>.<\/p>\n<h3 id=\"ram-requirement\">How much RAM does n8n need?<\/h3>\n<p>Evaluate the services you install and the amount of data each workflow handles together. The measurement in this guide\u2019s test box covers only its stated small workflow. Do not assume the same result for Assistant, local models, large files or heavy concurrency.<\/p>\n<h3 id=\"domain-https\">Do I need a domain and HTTPS?<\/h3>\n<p>Local experimentation is a different scenario. This guide uses a subdomain and a verifiable HTTPS certificate for the internet-accessible editor and webhook, so login and webhook credentials travel over an encrypted connection.<\/p>\n<h3 id=\"cpanel-plesk\">Can I use these commands with cPanel or Plesk?<\/h3>\n<p>A shared-hosting account does not replace a VPS where you can run Docker services. On a VPS with a control panel, the panel may already manage the ports and web server. Adapt its proxy configuration while preserving existing sites, or use a separate application server.<\/p>\n<p>To run your n8n workload on your own infrastructure, explore <a href=\"https:\/\/www.fibacloud.com\/products\/shared\">FibaCloud cloud server options<\/a>. Choose resources from observed workflow usage and include backup and maintenance in the deployment plan.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Install n8n on an Ubuntu VPS with Docker Compose, PostgreSQL, Caddy and an external task runner, then check HTTPS, authenticated webhooks and backup recovery.<\/p>\n","protected":false},"author":1,"featured_media":2613,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[7],"tags":[261,282,100],"class_list":["post-2611","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-tutorials-en","tag-docker","tag-n8n-en","tag-ubuntu"],"lang":"en","translations":{"en":2611,"tr":2610},"pll_sync_post":[],"_links":{"self":[{"href":"https:\/\/www.fibacloud.com\/community\/tutorials\/wp-json\/wp\/v2\/posts\/2611","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.fibacloud.com\/community\/tutorials\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.fibacloud.com\/community\/tutorials\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.fibacloud.com\/community\/tutorials\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.fibacloud.com\/community\/tutorials\/wp-json\/wp\/v2\/comments?post=2611"}],"version-history":[{"count":1,"href":"https:\/\/www.fibacloud.com\/community\/tutorials\/wp-json\/wp\/v2\/posts\/2611\/revisions"}],"predecessor-version":[{"id":2615,"href":"https:\/\/www.fibacloud.com\/community\/tutorials\/wp-json\/wp\/v2\/posts\/2611\/revisions\/2615"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.fibacloud.com\/community\/tutorials\/wp-json\/wp\/v2\/media\/2613"}],"wp:attachment":[{"href":"https:\/\/www.fibacloud.com\/community\/tutorials\/wp-json\/wp\/v2\/media?parent=2611"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.fibacloud.com\/community\/tutorials\/wp-json\/wp\/v2\/categories?post=2611"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.fibacloud.com\/community\/tutorials\/wp-json\/wp\/v2\/tags?post=2611"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}