Flowise AI Platform & Data · Flowise 3.1.4 Launch on AWS

Configuration¶

This page shows where Flowise's settings live and how to make the common changes. Make every change as root, then restart the affected service.

Where things live¶

Path	What it is
`/etc/systemd/system/flowise.service`	The service, including Flowise's settings as `Environment=` lines.
`/etc/nginx/sites-available/flowise.conf`	The HTTPS proxy on port 8443.
`/etc/flowise/tls/cert.pem`	TLS certificate. Readable by all users.
`/etc/flowise/tls/key.pem`	TLS private key. Root only.
`/etc/flowise/admin.password`	The owner password created on first boot. Root only.
`/var/lib/flowise/database/`	SQLite database: flows, credentials, users and settings.
`/var/lib/flowise/secrets/`	The key Flowise uses to encrypt stored credentials.
`/var/lib/flowise/storage/`	Uploaded files.
`/var/lib/flowise/logs/`	Flowise's own log files.

Default settings¶

The service sets these:

Setting	Value
`HOST`	`127.0.0.1`
`PORT`	`3000`
`APP_URL`	`https://127.0.0.1:8443`
`DATABASE_PATH`	`/var/lib/flowise/database`
`SECRETKEY_PATH`	`/var/lib/flowise/secrets`
`BLOB_STORAGE_PATH`	`/var/lib/flowise/storage`
`LOG_PATH`	`/var/lib/flowise/logs`
`DISABLE_FLOWISE_TELEMETRY`	`true`

Change a Flowise setting¶

Use a systemd drop-in rather than editing the unit file, so your changes are easy to find and keep:

sudo systemctl edit flowise

Add your settings in the editor, for example:

[Service]
Environment=LOG_LEVEL=debug

Save, then restart:

sudo systemctl restart flowise

Flowise takes a few minutes to answer again after a restart. See the Flowise environment variables for what you can set. Keep HOST=127.0.0.1.

The service may write only under /var/lib/flowise. Keep data paths there.

Raise the upload limit¶

nginx accepts request bodies up to 50 MB. To upload larger documents, raise client_max_body_size in /etc/nginx/sites-available/flowise.conf, then check and reload nginx:

sudo nginx -t
sudo systemctl reload nginx

Replace the TLS certificate¶

The certificate created on first boot is valid for 825 days. To create a new one, remove both files and let the first-boot service recreate them:

sudo rm /etc/flowise/tls/cert.pem /etc/flowise/tls/key.pem
sudo systemctl restart sushi-flowise-firstboot
sudo systemctl restart nginx

To use your own certificate instead, replace both files with the same ownership and permissions (cert.pem mode 0644, key.pem mode 0600, both root:root) and restart nginx.

Reach the builder from other machines¶

Flowise and nginx listen on loopback only. Choose one of these:

Session Manager port forwarding for each user, see Open the builder.
Expose nginx on the private network: add a listen <private-ip>:8443 ssl; line to flowise.conf, use a certificate your users trust for that name, update APP_URL to match, and in the security group allow port 8443 only from your own address ranges.

Keep it private

Do not open port 8443 or 3000 to the internet, and never change HOST away from 127.0.0.1. Flowise flows can run code and call your model providers with your credentials.

Things to leave alone¶

Do not delete /var/lib/flowise/secrets/. Without it, Flowise cannot decrypt the credentials you stored.
Do not turn off Flowise authentication.
Do not upgrade Flowise or Node.js with npm. A new Flowise version comes as a new version of the image.

Last updated October 13, 2026 · Suggest an improvement