Mess errors out when Foundry is run behind reverse proxy in a subdirectory

[gaggle331]

I just setup my nginx reverse proxy on top of foundry with foundry set up in a subdirectory of my domain. Now the Mess module is broken because it's trying to access the file at systems/dnd5e/module/pixi/ability-template.js but which nginx is sending to https://MYHOST.THISISBROKEN/systems/dnd5e/module/pixi/ability-template.js instead of https://MYHOST.THISISBROKEN/foundry/systems/dnd5e/module/pixi/ability-template.js.

I believe this is a very simple fix, if you just change the import on line 102 in /scripts/modify-templates.js to be a relative import like

const importedJS = (await import(/* webpackIgnore: true */ '../../../systems/dnd5e/module/pixi/ability-template.js'))

Then everything should work a bit smoother.

[harbinger1080]

I have same issue with several modules and systems in Foundry VTT. I think you're right on the real fix.

In the meantime, I added a temporary workaround to my nginx conf to force things to work for the time being. Just redirecting:

        location /systems {
                return 301 $scheme://$host/foundryvtt/$request_uri;
        }

        location /modules {
                return 301 $scheme://$host/foundryvtt/$request_uri;
        }

        location /ui {
                return 301 $scheme://$host/foundryvtt/$request_uri;
        }

        location /icons {
                return 301 $scheme://$host/foundryvtt/$request_uri;
        }