Trilium Notes - Unable to upload images

[albotroz]

I installed Trilium using the Proxmox helper script.
https://community-scripts.github.io/ProxmoxVE/scripts?id=trilium
Trilium Notes v0.95.0LXC

Proxmox Virtual Environment 9.0.11
Cloudflared 2025.10.0

I use Trilium Notes with Cloudflare (also via helper scripts).

Unfortunately, I am unable to add an image to a note or upload one from a client.

When I access Trilium via local IP and try to upload an image to a note, I get the message “Upload failed.”

When I access Trilium via subdomain and try to upload an image to a note I get the message

502 PUT notes/K0xw8IoGYL4e/data Bad gateway 

Error code 502 

Visit cloudflare.com for more information.

In Cloudflared (/etc/cloudflared/config.yml), I have the following for Trilium:

ingress:
  - hostname: my.subdomain-for-trilium.org
    service: http://192.168.***.***:8080

Does anyone have any idea how I can fix this?
As you can see, Proxmox Script community has been referred here.

[dosubot[bot]]

Hi @albotroz! I'm Dosu and I’m helping the Trilium team.

The image upload issue in Trilium Notes running in a Proxmox LXC container with Cloudflared is likely caused by one or more of the following:

• Image compression settings or missing dependencies: Upload failures can happen if the image compression function (using the JIMP library) is misconfigured or if dependencies are missing. Leaving the "Image quality" field blank in Trilium's image settings can also break uploads. Double-check your image settings and try setting a valid JPEG quality value (e.g., 80) if it's blank. If you recently changed these settings, try reverting or reinstalling Trilium to restore defaults. See details

• File system permissions in the LXC container: Trilium needs write access to its data directory. Make sure the container user has permission to write files where Trilium stores notes and attachments.

• Reverse proxy or Cloudflared misconfiguration: 502 errors often mean the proxy isn't forwarding PUT requests or large uploads correctly. In your Cloudflared config, ensure all HTTP methods (GET, POST, PUT, DELETE) are allowed and forwarded, and that there are no path rewrites or restrictions. See proxy troubleshooting

• CSRF/cookie issues: Trilium uses SameSite=strict cookies, so always use the same hostname and protocol (http/https) everywhere. Mixing local IP and subdomain access can cause uploads to fail due to missing cookies or CSRF token errors. See explanation

• Browser-specific issues: Sometimes, stricter cookie or CORS handling in browsers like Chrome can block uploads. Try clearing cookies or testing in another browser.

Troubleshooting steps:

1. Check Trilium logs in the container for errors when you attempt an upload.
2. Verify image compression settings and dependencies (especially JIMP).
3. Confirm file system permissions for Trilium's data directory.
4. Review Cloudflared and proxy configs to ensure PUT requests and large uploads are allowed.
5. Use the same hostname/protocol for all access, and avoid mixing local and remote addresses.

If you fix the settings or permissions and still see issues, a fresh reinstall of Trilium (with a backup restore) has resolved similar problems for other users.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}