We have a site with multiple domains defined over it. Say, erp.myerp.com 192.168.10.10 erp.myerp.xy erp.myerp.com.xy . The root url is set to https://erp.myerp.com.xy
If you have a download or a new document referenced via a javascript prompt, the reference link is created using the root url . However, the user is accessing via 192.168.10.10 or other domain. You can test it in Exchange Rate Revaluation. Create an Exchange Rate Revaluation while accessing the site over a domain other than the root url’s. Then, create the Journal Entry and try clicking on the new Journal Entry reference. The link will direct you to the root url domain.
This is a serious issue when the erp is hosted locally and need to be accessed via local IP.
You may have internal routing issue if you have problem locally.
If you use multitenent function than it should only establish connection using domain name.
Look into how the nginx is configured.
No idea why you need multiple domain names. … Plus you need to remove ip address and only use domain name instead and install a dns controller locally to resolve dns for local servers.
You also need to check which finding domain is assigned to which site.
We have no IP routing issue as we are able to use the entire site until a URL is created by ErpNext or Frappe.
I don’t think it is even slightly related with a basic component or infrastructure issue. The nginx is working fine until such a link is created and presented to the user via code.
The multiple domains setup is working fine for several years and is not the problem.