Hello,I have an application developed on outsystems.company.com/myapp (on-prem) and I want the users to access the application using newname.company.com/myapp.Steps I did so far:1. Configured DNS by creating a CNAME DNS record of newname.company.com pointing to outsystems.company.com. 2. I have the Common Name certificate for outsystems.company.com and a Subject Alternative Name for newname.company.com within the same certificate.3. Created a Site Rule with the Base URL of newname.company.com and root application as myapp.When I try to reach newname.company.com/myapp I get a 404 error and myapp is still accessible from outsystems.company.com/myapp.What other settings do I have to do?
Hello.
That should be it.
Yes, I have installed ISAPI filters in IIS and enabled them. I have also waited (I have this issue for several days). I don't have other SEO rules in place.One other thing that I've noticed is: When accessing only newname.company.com (without /myapp) I am being redirected to newname.company.com/servicecenter (which also gives back a 404 error). Accessing outsystems.company.com/servicecenter works fine.
Ok, so newname.company.com DNS settings are working.
Then it is failing because the SEO Rule is wrong (or iSAPI fails, or IIS settings are wrong...).
Can you check the logs in IIS?
- OsISAPI logs:#31184 2025-10-21 11:53:02 [INFO] - Number of Redirect/Site Rules loaded: 1, Number of Alias Rules loaded: 67, Number of Page Rules loaded: 0
#46748 2025-10-21 11:53:28 [INFO] - Number of Redirect/Site Rules loaded: 1, Number of Alias Rules loaded: 67, Number of Page Rules loaded: 0
#50720 2025-10-21 11:53:29 [INFO] - Number of Redirect/Site Rules loaded: 1, Number of Alias Rules loaded: 67, Number of Page Rules loaded: 0These are the logs on both production instances (server1 and server2). They look the same on both. Same information can be found in Event Viewer as well on both instances.- IIS logs:
2025-10-21 06:48:10 Server_IP GET /myapp- 443 - Server_IP Mozilla/5.0+(Windows+NT+10.0;+Win64;+x64)+AppleWebKit/537.36+(KHTML,+like+Gecko)+Chrome/141.0.0.0+Safari/537.36 https://newname.company.com/ 301 0 0 1 2025-10-21 06:48:Server_IP GET /myapp/ - 443 - Server_IP Mozilla/5.0+(Windows+NT+10.0;+Win64;+x64)+AppleWebKit/537.36+(KHTML,+like+Gecko)+Chrome/141.0.0.0+Safari/537.36 https://newname.company.com/ 200 0 0 3
I have to mention that the IIS logs are old. I've re-made the IIS configuration using the steps from https://success.outsystems.com/documentation/11/building_apps/search_engine_optimization_in_apps/seo_for_outsystems_reactive_web_apps_vs_traditional_web_apps/seo_friendly_urls_for_traditional_web_apps/#installing-isapi-filters-and-logging because I missed the steps 7-10, and there aren't any new logs that contain newname.company.com.I think the logs are from when I tried the Redirect Rule List option, which I deleted afterwards. No new logs following correctly configuring the ISAPI filters.
That is the right URL. But take a look at
https://success.outsystems.com/documentation/11/building_apps/search_engine_optimization_in_apps/seo_for_outsystems_reactive_web_apps_vs_traditional_web_apps/site_rules_for_seo_friendly_urls/
(site rules)
I always did as the documentation says and never had issues. It is that simple. That's why I suspect ISAPI has something wrong.
My settings look like this: Note that instead of App, the Root Application is "myapp" as per my example.
Any suggestions on what I should check or how I should debug to find the root cause?
Found a similar doubt.
TLDR: check Windows Event Viewer. If everything looks fine, contact support so they look at the logs.