Run behind a reverse proxy (e.g. under https://domain.com/foo/bar)

Hi,

is it possible to run the on-prem variant behind a reverse proxy?

In the docs I couldn't find any environment variables for that yet.

The issues begin with loading the js- and css-files on startup because they are expected to be served on the root context (https://domain.com/styles~app.....js instead of https://domain.com/**foo/bar/**styles~app.....js).

I could imagine that there might be solution to inject/override nginx/nodejs web server config but I couldn't find a concrete solution in the web yet - while I also don't know the actual web server and specialties you are using in the Retool image which might make a potential solution still unfeasible (in case I would have find one).

Thankful for any advice :slight_smile:

BR Matthias

1 Like

I'm also looking for this capability.

We host all our apps behind a reverse proxy. Ideally we want to define a custom base path on our hostname to access Retool.

For example:

https://staging.mycompany.com/retool
https://staging.mycompany.com/retool/apps
https://staging.mycompany.com/retool/editor
...

1 Like

Hey Matthias, looks like this conversation was answered via chat support. Unfortunately it is not possible to do this with Retool at this time. Thanks for reaching out!

Is there any advance on this feature? Is it taken into account in roadmap?
cheers

Hey @daniel-grana, unfortunately there are no updates on this. We are tracking this request internally but don't have concrete plans to work on this in the near term. I can make sure we update this thread if that changes. Thanks!