Scenario:
We have Mautic installed in an AWS VPC with no public IPs; all public traffic is handled via AWS Application Load Balancers. The load balancer has a specific set of rules to route any requests for news.mautic.mydomain.com with paths matching
^/(email/.|r/.|mtracking.gif|mtc(.js)?|media/.|s/.)$
to Mautic.
Users who manage emails and campaigns access Mautic via admin.mautic.mydomain.com, which is handled by an internal load balancer.
This setup is intentional for security reasons, to prevent any access to the admin interface from outside the company network.
However, this creates a problem when configuring Mautic to use news.mautic.mydomain.com for tracking. All tracking URLs appear to be generated using the admin-based URL (admin.mautic.mydomain.com) instead.