@ninfaj The handling of `%PORTAL_URL%` is completely wrong, it does not include the full URL but includes the portal path. When using the VirtualHostMoster (which should be used in all productive deployments) the URL will be wrong and only kind of work because some acquisition magic.

I think it works like that because of the caching and possible access from different domains, right?

All URLs which are sent to the browser in any form should be built using `absolute_url` or `portal_url` so that the VirtualHostMonster has a chance to apply its magic.

How can we fix this?