ServiceProxyScript Not Loading in separate URL #9558

5 Answer(s)

• 

  0

  AI-Bot created 9 days ago

  Support Team ABP Agent

  • The issue is caused by the Angular frontend being hosted at the root (client.StageDomain.com) and the API (HttpApi.Host) being hosted under a sub-path (client.StageDomain.com/api). ABP's ServiceProxyScript and other dynamic endpoints (like /Abp/ServiceProxyScript and /Abp/ApplicationConfigurationScript) are expected at the root of the API application, but when hosted under /api, the Angular app tries to load them from /Abp/ServiceProxyScript instead of /api/Abp/ServiceProxyScript.

  • This results in 404/500 errors and MIME type issues, as seen in your console logs, because the requests are routed incorrectly or the server returns an HTML error page instead of the expected JavaScript.

  • ABP's official documentation and templates assume that the API is either on a separate domain/subdomain or at the root of a site, not under a sub-path like /api. Hosting the API under a sub-path is not officially supported and leads to these issues.

  • To resolve this:

    1. Host the API (HttpApi.Host) on a separate subdomain (e.g., api.StageDomain.com) or at the root of a different site.
    2. Update your Angular environment and appsettings.json to point to the correct API root URL.
    3. If you must use a sub-path, you would need to customize the Angular app and possibly the ABP backend to ensure all dynamic script and API URLs are prefixed with /api, but this is not recommended and not officially supported.

  • For more details, see the official IIS deployment documentation:

    • https://abp.io/docs/commercial/latest/startup-templates/application/deployment-iis?UI=NG&DB=EF&Tiered=No

  • In summary: Move your API to a root or subdomain, not a sub-path, for full ABP functionality.

  Sources:

  • https://abp.io/docs/commercial/latest/startup-templates/application/deployment-iis?UI=NG&DB=EF&Tiered=No

  ---

  This response was generated by AI. If it didn’t solve your problem, feel free to post a new answer — our support team will jump in to help you soon.

  Save Cancel
• 

  0

  HadiLoghman created 9 days ago

  The issue doesn't appear to be related to the ServiceProxyScript, as we’re encountering the same error locally as well. We encountered this error for Password change too. This issue happens for all Profile menu items

  Save Cancel
• 

  0

  EngincanV created 9 days ago

  Support Team .NET Developer

  Hi, do you have any specific configuration in your web.config file that causes this problem? (Also, please check: https://abp.io/docs/latest/solution-templates/layered-web-application/deployment/deployment-iis?UI=NG&DB=EF&Tiered=No#rewrite-for-getenvconfig)

  Save Cancel
• 

  0

  HadiLoghman created 8 days ago

  Hi EngincanV, thanks for reaching out. As I mentioned earlier, our application is .NET Core-based and uses appsettings.json for configuration. Our web.config is minimal and doesn’t include any specific context-related settings. The only notable difference compared to our local environment is that the SelfUrl and Authority in appsettings.json include an additional /api suffix, whereas the AngularUrl does not. This is the only configuration difference we've identified so far. Maybe this helps as well, when I try to change the layout of the website, I get some unexpected results on the staging site. Interestingly, on the first refresh, the website loads normally.

  After selecting a different layout After refreshing

  Save Cancel
• 

  0

  maliming created 5 days ago

  Support Team Fullstack Developer

  hi

  Can you try to add UsePathBase("/api") to your API website?

  app.UsePathBase("/api");
  app.UseRouting();
  

  Save Cancel