[BUG] Issue with accessing Flowise UI via Apache Reverse Proxy

[jeme95]

I have deployed Flowise on a Windows Server 2019 remote VM, where it runs on port 3000 and works fine when accessed directly via localhost:3000 with Remote Desktop Connection

To make it accessible externally, I am using an Apache HTTP Server as a reverse proxy. I added the following proxy rules in the httpd.conf file:

ProxyPass /flowise http://localhost:3000  
ProxyPassReverse /flowise http://localhost:3000  

Now, when I access https://my-domain.com/flowise, I get a 200 OK status, but the UI does not load correctly. Instead, the browser console shows errors indicating that some assets are being requested from https://my-domain.com/assets/some-asset-file.js instead of being resolved under /flowise

• Flowise Version 2.2.4