[{"data":1,"prerenderedAt":156},["ShallowReactive",2],{"seo-verification":3,"blog-how-to-host-flowise-on-a-vps-ma-en":6,"promo-bar-likely":147},{"google":4,"bing":5},"EycwPY2XMyTkVzas3n1ygeNJFGAH513qrMjfDljzsMQ","",{"key":7,"data":8},"blog-how-to-host-flowise-on-a-vps-ma-en",{"id":9,"slug":10,"slugs":11,"title":15,"excerpt":16,"readTime":9,"views":17,"isPinned":18,"noindex":18,"publishedAt":19,"updatedAt":20,"category":21,"categories":26,"featuredImage":28,"bgImage":29,"posterImage":30,"relatedSolution":31,"intro":34,"sections":35,"ctaTitle":97,"ctaBody":98,"ctaButton":99,"ctaUrl":100,"relatedPosts":101},8,"how-to-host-flowise-on-a-vps",{"fr":12,"en":10,"ar":13,"es":14},"heberger-flowise-vps","كيفية-استضافة-flowise-على-خادم-vps","como-alojar-flowise-en-un-vps","How to Host Flowise on a VPS","Deploy Flowise on your VPS: build no-code AI agents and chatbots with Docker and SSL. Environment variables, RAG with Ollama, updates and troubleshooting.",1,false,"2026-06-12T00:00:00+00:00","2026-09-19T02:00:43+00:00",{"id":17,"name":22,"slug":23,"color":24,"icon":25},"Artificial Intelligence","intelligence-artificielle","bg-purple-500\u002F10 text-purple-400","ia",[27],{"id":17,"name":22,"slug":23,"color":24,"icon":25},null,"\u002Fblog\u002Fcovers\u002Fbg.svg","\u002Fblog\u002Fcovers\u002Fheberger-flowise-vps-poster.svg",{"categorySlug":32,"appSlug":33},"artificial-intelligence","flowise","Flowise is a visual LLM app builder: you assemble LangChain flows by drag-and-drop, without writing a single line of code. Hosted on your own VPS, it becomes a private AI-agent platform, with no leak of your prompts to a third-party SaaS. This guide covers the full installation with Docker, the reverse proxy, HTTPS, key environment variables, updating and common errors.",[36,40,51,54,79,82,85,88,91,94],{"type":37,"title":38,"body":39},"h2","Why self-host Flowise on a VPS","Flowise handles sensitive data: OpenAI\u002FAnthropic API keys, vectorised internal documents, conversation history, the business logic of your agents. On the shared cloud version, these elements pass through infrastructure you do not control. On a dedicated VPS, the Flowise canvas, the database and the embeddings all stay with you. You keep control of versions (flows evolve fast between releases), of the connectors you enable, and of model billing since you plug in your own keys. A VPS also lets you expose flows as a REST API to integrate them into your own applications, with no quota imposed by a vendor.\n\nAnother practical reason: Flowise Cloud plans limit the number of active flows, monthly executions and access to advanced nodes. On your VPS, none of these limits apply — you define the allocated resources yourself.",{"type":41,"title":42,"items":43},"ul","The concrete benefits of a self-hosted Flowise",[44,45,46,47,48,49,50],"Full confidentiality of prompts, API keys and indexed documents, which never leave your server.","Inference endpoints exposed as a REST API with no third-party rate limit.","Free choice of model (OpenAI, Anthropic, Mistral, or a local LLM via Ollama on the same network).","Controlled persistence of flows and vector stores in Docker volumes that you back up.","Update when you decide, without suffering a forced canvas migration.","Predictable cost: a single monthly VPS price, no pricing per flow or per execution.","Advanced nodes without restriction: full access to all LangChain integrations, agent tools and vector store connectors.",{"type":37,"title":52,"body":53},"Hardware and software requirements","Flowise itself is lightweight, but real-world usage depends on embeddings and vector stores. Budget at least 2 vCPUs and 2 GB of RAM for testing, and 4 vCPUs \u002F 4 to 8 GB of RAM if you index large documents or run several concurrent flows. Plan for 20 GB of disk for the containers, vector stores and any local models.\n\nOn the software side: Docker and Docker Compose installed, a domain or subdomain (e.g. `flowise.your-domain.com`) pointing to the VPS IP, and port 443 open. If you plan to run a local LLM via Ollama, increase RAM to at least 8 GB (16 GB for 7B+ models at 4-bit quantisation). Prepare the API keys of the LLM providers you intend to use ahead of time.",{"type":55,"title":56,"steps":57},"steps","Deploy Flowise with Docker and HTTPS",[58,61,64,67,70,73,76],{"title":59,"body":60},"Prepare the VPS and Docker","Connect via SSH, update the system then install Docker with `curl -fsSL https:\u002F\u002Fget.docker.com | sh`. Check with `docker compose version`. Create a dedicated folder:\n\n```bash\nmkdir -p \u002Fopt\u002Fflowise && cd \u002Fopt\u002Fflowise\n```",{"title":62,"body":63},"Write the docker-compose.yml","Define the service with the official `flowiseai\u002Fflowise` image, internal port `3000`, a named volume for persistence, and the essential environment variables:\n\n```bash\nFLOWISE_USERNAME=admin\nFLOWISE_PASSWORD=strong_password\nFLOWISE_SECRETKEY_OVERWRITE=a_random_32_char_string\nDATABASE_PATH=\u002Froot\u002F.flowise\nSECRET_ENCRYPTION_KEY=another_random_32_char_string\n```\n\nThe `flowise_data` volume must point to `\u002Froot\u002F.flowise` inside the container so that the SQLite database and vector stores survive restarts.",{"title":65,"body":66},"Start the container","Run `docker compose up -d` then `docker compose logs -f` to confirm that Flowise is listening. At this stage it responds locally on `127.0.0.1:3000`, not exposed publicly, which is deliberate.",{"title":68,"body":69},"Configure the reverse proxy","Install Caddy or Nginx Proxy Manager. With Caddy, a single line in the Caddyfile is enough:\n\n```bash\nflowise.your-domain.com {\n    reverse_proxy localhost:3000\n}\n```\n\nCaddy obtains and renews the Let's Encrypt certificate automatically. If you prefer nginx, make sure to enable WebSockets (`proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection upgrade;`) — Flowise needs them for real-time canvas updates.",{"title":71,"body":72},"Secure access and keys","Harden authentication, restrict port 3000 to the loopback in the firewall (`ufw deny 3000`), and add your LLM API keys directly in the Flowise interface (Credentials section) rather than in clear text in the compose file. The `FLOWISE_SECRETKEY_OVERWRITE` variable encrypts these credentials in the database; without it, they are stored in plain text.",{"title":74,"body":75},"Test a flow and the API","Create a simple chatflow, publish it, then call its endpoint:\n\n```bash\ncurl -X POST https:\u002F\u002Fflowise.your-domain.com\u002Fapi\u002Fv1\u002Fprediction\u002F\u003Cid> \\\n  -H 'Content-Type: application\u002Fjson' \\\n  -d '{\"question\":\"test\"}'\n```\n\nTo protect a chatflow endpoint with an API key, enable **API Key Auth** in the flow settings — each call must then carry `Authorization: Bearer \u003Cyour_key>`.",{"title":77,"body":78},"Logging in for the first time","When you first open the URL, Flowise displays a setup screen that has you create the administrator account (email + password) before it gives access to the dashboard. Open it immediately after the installation.",{"type":37,"title":80,"body":81},"Connect Flowise to Ollama for a fully local AI stack","For high-performance RAG flows with no external API cost, connect Flowise to an Ollama container running on the same VPS through the internal Docker network (`http:\u002F\u002Follama:11434`). You thus combine embeddings and generation locally: no data leaves the server, and latency drops since everything travels over the host's private network.\n\nIn your `docker-compose.yml`, add the Ollama service on the same Docker network as Flowise:\n\n```bash\nservices:\n  ollama:\n    image: ollama\u002Follama\n    volumes:\n      - ollama_data:\u002Froot\u002F.ollama\n    networks:\n      - flowise_net\n\n  flowise:\n    image: flowiseai\u002Fflowise\n    networks:\n      - flowise_net\n    ...\n```\n\nIn Flowise, when you add an **Ollama** node (Chat Model or Embeddings), enter `http:\u002F\u002Follama:11434` as the base URL. Pull a model from inside the container: `docker exec -it \u003Collama_id> ollama pull llama3.2`. For embeddings, `nomic-embed-text` is a good starting point on 4 GB of RAM.",{"type":37,"title":83,"body":84},"Useful environment variables","Flowise exposes around twenty configuration variables. The most useful ones in production:\n\n`FLOWISE_USERNAME` and `FLOWISE_PASSWORD` — authentication for the admin interface. Mandatory as soon as the public port is open.\n\n`FLOWISE_SECRETKEY_OVERWRITE` — encryption key for credentials stored in the database. If you change this value after first startup, existing credentials become unreadable.\n\n`DATABASE_TYPE` — defaults to `sqlite`. For heavier load or a redundant deployment, switch to `postgres` and fill in `DATABASE_HOST`, `DATABASE_PORT`, `DATABASE_USER`, `DATABASE_PASSWORD`, `DATABASE_NAME`.\n\n`CORS_ORIGINS` — list of origins allowed to call the prediction API from a browser. Example: `https:\u002F\u002Fyour-app.com`. Without this variable, CORS calls from another origin will be blocked.\n\n`BLOB_STORAGE_PATH` — storage path for uploaded files (RAG documents). Defaults to `~\u002F.flowise\u002Fstorage`; mount a dedicated volume if you index large corpora.\n\n`LOG_LEVEL` — values: `error`, `warn`, `info`, `verbose`, `debug`. In production, `warn` is enough to keep logs manageable.",{"type":37,"title":86,"body":87},"Updating Flowise without losing flows","Flowise releases regular updates that add nodes and fix flow behaviour. The update is non-destructive if your data is in a named volume.\n\n```bash\ndocker compose pull\ndocker compose up -d\n```\n\nFlowise automatically migrates the SQLite database on startup. Before each update, export your important flows via the canvas **Export** button (JSON file) — it is the simplest safety net.\n\nIf you use PostgreSQL, check the release notes before pulling the image: some versions introduce irreversible schema migrations. Keep a database backup (`pg_dump`) before updating.",{"type":37,"title":89,"body":90},"Troubleshooting common errors","**The canvas does not load or nodes disappear.** Check that your reverse proxy properly passes WebSockets. With nginx, the `Upgrade` and `Connection` headers must be present. With Caddy, they are set automatically.\n\n**`Error: FLOWISE_SECRETKEY_OVERWRITE is required`.** This variable was not required in earlier versions but has become so. Add it to your compose and restart — credentials already entered remain valid as long as the value matches the one used when they were stored.\n\n**The vector store loses its documents after restart.** Check that the Docker volume path matches both `BLOB_STORAGE_PATH` and `DATABASE_PATH`. A misconfigured bind-mount stores data in an ephemeral container folder.\n\n**Calls to Ollama fail with `ECONNREFUSED`.** The Ollama service must be on the same Docker network as Flowise. If Ollama runs outside Compose (systemd service, for instance), use the Docker gateway IP (`172.17.0.1:11434`) rather than `localhost`.\n\n**OpenAI\u002FAnthropic credentials are rejected after migration.** If `FLOWISE_SECRETKEY_OVERWRITE` changed between two deployments, secrets encrypted with the old key can no longer be decrypted. Delete and re-enter the credentials in the interface.",{"type":92,"body":93},"tip","For a secure team deployment, enable authentication on each chatflow (the flow's **API Key** section) and create one key per external integration. That way, each application consuming a Flowise endpoint has its own revocable key without affecting the others.",{"type":92,"title":95,"body":96},"The official documentation","For advanced configuration and tool-specific options, refer to the \u003Ca href=\"https:\u002F\u002Fdocs.flowiseai.com\" target=\"_blank\" rel=\"noopener noreferrer\">official Flowise documentation\u003C\u002Fa>. This guide covers going live on a VPS; the vendor docs remain the reference for fine-tuning, major updates and specific use cases.","Deploy Flowise on a ServOrbit Cloud VPS in minutes","With a ServOrbit Cloud VPS shipping preconfigured Docker and scalable resources, you install Flowise and your AI flows without friction. Scale RAM and vCPU as your agents grow.","Launch my Cloud VPS","\u002Fvps-cloud",[102,119,137],{"id":17,"slug":103,"slugs":104,"title":108,"excerpt":109,"readTime":110,"views":17,"isPinned":18,"noindex":18,"publishedAt":111,"updatedAt":112,"category":113,"categories":114,"featuredImage":28,"bgImage":29,"posterImage":116,"relatedSolution":117},"how-to-host-open-webui-on-a-vps",{"fr":105,"en":103,"ar":106,"es":107},"heberger-open-webui","كيفية-استضافة-open-webui-على-خادم-vps","como-alojar-open-webui-en-un-vps","How to Host Open WebUI on a VPS","A complete guide to deploying Open WebUI on your own VPS. Keep control of your data, avoid cloud API costs, and access your LLMs from a clean web interface.",9,"2026-06-01T00:00:00+00:00","2026-11-09T20:55:18+00:00",{"id":17,"name":22,"slug":23,"color":24,"icon":25},[115],{"id":17,"name":22,"slug":23,"color":24,"icon":25},"\u002Fblog\u002Fcovers\u002Fheberger-open-webui-poster.svg",{"categorySlug":32,"appSlug":118},"open-webui",{"id":120,"slug":121,"slugs":122,"title":126,"excerpt":127,"readTime":128,"views":17,"isPinned":18,"noindex":18,"publishedAt":129,"updatedAt":130,"category":131,"categories":132,"featuredImage":28,"bgImage":29,"posterImage":134,"relatedSolution":135},2,"deploying-dify-on-a-vps-ai-workflows-under-control",{"fr":123,"en":121,"ar":124,"es":125},"deployer-dify-vps","نشر-dify-على-vps-سير-عمل-الذكاء-الاصطناعي-تحت-السيطرة","desplegar-dify-en-un-vps","Deploy Dify on a VPS: Complete Guide from Installation to Plugins","Install Dify on a ServOrbit VPS: requirements, Docker Compose, offline plugins, known Docker limits, backup before upgrading, and troubleshooting.",15,"2026-02-11T00:00:00+00:00","2026-10-29T03:10:23+00:00",{"id":17,"name":22,"slug":23,"color":24,"icon":25},[133],{"id":17,"name":22,"slug":23,"color":24,"icon":25},"\u002Fblog\u002Fcovers\u002Fdeployer-dify-vps-poster.svg",{"categorySlug":23,"appSlug":136},"dify",{"id":138,"slug":139,"slugs":140,"title":144,"excerpt":145,"readTime":146,"views":17,"isPinned":18,"noindex":147,"publishedAt":148,"updatedAt":149,"category":150,"categories":151,"featuredImage":28,"bgImage":29,"posterImage":153,"relatedSolution":154},121,"hosting-openclaw-on-a-vps",{"fr":141,"en":139,"ar":142,"es":143},"heberger-openclaw-vps","استضافة-openclaw-على-خادم-vps","alojar-openclaw-en-un-vps","Hosting OpenClaw on a VPS","Host OpenClaw on your VPS: the open source personal AI assistant reachable from WhatsApp, Telegram, Discord and 50+ messaging apps. Docker, LLM setup and HTTPS.",4,true,"2026-02-23T00:00:00+00:00","2026-11-09T20:55:19+00:00",{"id":17,"name":22,"slug":23,"color":24,"icon":25},[152],{"id":17,"name":22,"slug":23,"color":24,"icon":25},"\u002Fblog\u002Fcovers\u002Fheberger-openclaw-vps-poster.svg",{"categorySlug":32,"appSlug":155},"openclaw",1794270422775]