{
  "id": 14153318,
  "title": "n8n says it's 'configured to use a secure cookie'? Keep it on: four fixes instead of N8N_SECURE_COOKIE=false",
  "url": "https://urgent.news/2026/10/13/n8n-says-its-configured-to-use-a-secure-cookie-keep-it-on-four-fixes",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-10-13T08:25:16.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/munimv2/n8n-says-its-configured-to-use-a-secure-cookie-keep-it-on-four-fixes-instead-of-3lg1"
  },
  "original_language": "en",
  "account": "When you access your self-hosted n8n instance and it displays a secure cookie warning instead of the login page, a secure connection is required to log in. Some forum posts suggest disabling the secure cookie flag by setting N8N_SECURE_COOKIE=false to resolve the issue. However, doing so exposes your login session to anyone who can intercept your traffic, potentially allowing unauthorized access to sensitive data stored in n8n, such as email credentials, CRM information, databases, and AI API keys.\n\nThe recommended solution is to ensure n8n is configured to use HTTPS. If the secure cookie is only a concern on your own machine, use http://localhost:5678 in a browser, as localhost is treated as a secure origin. For home lab setups or NAS devices, Tailscale can provide HTTPS access to n8n without opening ports. Simply run tailscale serve 5678 and configure n8n to use the Tailscale hostname and HTTPS. For LAN-only usage without Tailscale, install a certificate from Caddy's local CA and point n8n to a LAN name, ensuring browsers trust the certificate. If n8n needs to be accessible from the internet, obtain a domain and set up a reverse proxy like Caddy or Nginx to serve HTTPS. Remember to set the appropriate environment variables for protocol, host, certificate, and proxy settings.\n\nAfter making these changes, restart n8n and sign in again through HTTPS. If you previously configured n8n with N8N_SECURE_COOKIE=false, remove that line, restart, and sign in with a strong password, reviewing user accounts and API keys. Also, check the n8n version, as numerous security advisories have been released recently. Follow the comprehensive self-hosted AI security checklist provided by Munim, Inc. to keep your n8n instance secure.",
  "summary": "You open your self-hosted n8n at http://192.168.1.20:5678 , or on a NAS (Unraid, QNAP, Synology), or in Safari, and get this instead of a login page: Your n8n server is configured to use a secure cookie, however you are either visiting this via an insecure URL, or using Safari. Most forum answers say to set N8N_SECURE_COOKIE=false . That makes the message go away, but the cookie it's about is…",
  "key_points": [
    "n8n requires HTTPS for secure login",
    "Use localhost for local machine access",
    "Implement HTTPS via Tailscale, Caddy, or Nginx for LAN or internet access"
  ],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}