Yes, I brought it to live while using an own supdomain for the app. That works.

Plesk only supports the proxy-configuration for subfolders. So I had to change the nginx.conf file by my self, which is originally generated by Plesk. Unfortunately everytime I make some changes on the subdomain, I have manually reconfigure this file again because Plesk overwrites it.

Nice to hear this! congrats and yes in such cases plesk or other admin tools like webmin (my favorite) are at their limits. For direct editing I am using mc / mcedit instead of vi or other editors... hounting shadows of my past MSDOS and Norton Commander times ;-)

I'll bring up this thread cause I've spend my weekend and monday on similar problem bringing my OnlyOffice App Server to work behind Apache2 reverse proxy. Finally the trick was to use on both ends https encryption. Regardless if it's a private or public cert. The combination of http in the intranet and https to the world may cause headaches.

@Patrick L Having said that, I am struggling with trying to do the same as you (instead of connecting directly to a port other than 80 or 443).I always get the Xojo "Server disconnected" text (but without any images). It's like Xojo loads the framework but is then unable to talk to it.

I am having the exact same issue. I have multiple web app instances running on a server. I want to use relative paths to route traffic to different webapps depending on the path.

Perhaps the xojo app is sending data that has URLs in it that are not coded for your app directory proxy setup. For instance, when someone hits https://yourserver.com/manage the server includes responses with links like this "/framework/some.file" or the like. Paths that don't include the "/manage/" part - so those requests are being routed elsewhere. That may explain why the bare root path works and the subfolder root path does not.

So you might need nginx to rewrite URLs in the RESPONSES from the xojo app to correct the directory.

This will require some playing around to get just right, but I think you understand the basic problem. The output from the app contains root-based links that do not include your /app/ directory. Note, the substitutions module may or may not be enabled by default in your nginx installation.

OK so I did a little testing and I was not able to make Xojo (2018r3) NOT compress the response, even with the most bare request or with Accept-Encoding removed, set to blank, identity or gzip;q=0 or multiple other variations.

@John J So if you can't prevent it you will need to unzip it in nginx, do the substitutions, then return the modified response.

Thanks John, appreciate your help! I did try gunzip the other day but I don't think I have the correct module installed. I was just hoping there was another option. I'll figure out how to install it and report back.

I was finally able to get Xojo Web to work behind a reverse proxy using a path. Thank you community! This is useful for hosting two differnet xojo web instances on one server. WebApp1 can redirect you two WebApp2 using a relative path regardless of the server or client IP/DNS name. In my case, I need WebApp1 to show WebApp2 in an iframe.

I could see from running nginx -V the module was already installed. Apparently it is installed on nginx-full and nginx-extra by default. You need to run gzip_disable "."; to make it actually work though.

It was a bit painful, and this will probably break when the framework updates, but this works for me. This could also break if you use some parts of XojoWeb that my app doesn't use.