Thanks for the workaround suggestion.

In our case, this workaround is problematic because the affected Manage/Profile Picture UI is inside the ABP Pro package and we don’t have practical source-level access to patch that page directly in a maintainable way.

For this reason, we would strongly prefer an official bug fix in the module instead of a local workaround.

Could you please confirm this as a product bug in Volo.Abp.Account.Pro.Public.Web.

Hello ABP team,

I checked the docs/samples/search before opening this request.

We are using ABP Commercial and hosting the server as an IIS sub-application under /server (not at site root). We found that the Account Manage/Profile Picture UI generates an image URL without the app pathbase, which breaks under sub-application hosting.

We validated this on package version Volo.Abp.Account.Pro.Public.Web 10.1.1 (same behavior as 10.0.2).

Environment

• ABP Commercial
• Server: ASP.NET Core on IIS
• Hosted under subpath: https://<host>/server/
• Frontend under subpath: https://<host>/web/
• Package: Volo.Abp.Account.Pro.Public.Web 10.1.1

Exception message and full stack trace:

No server exception is thrown. This is a client-side URL generation issue resulting in 404 for profile picture image requests under https://<host>/server/Account/Manage (please note this is not web but server side app)

Steps to reproduce the issue:

1. Create/use ABP Commercial solution with Account Pro module.
2. Deploy server as IIS sub-application (e.g., /server) and web as /web.
3. Ensure app pathbase/base href is correctly set (/server/).
4. Login and open Account Manage page (https://<host>/server/Account/Manage).
5. Go to Profile Picture section.
6. Observe generated HTML/request for current profile image:

• Actual request URL: https://<host>/api/account/profile-picture-file/{id} (missing /server)
• Expected URL: https://<host>/server/api/account/profile-picture-file/{id}

Observed behavior

• <img id="CurrentProfilePicture" ...> points to root-relative /api/account/profile-picture-file/{id}.
• Under sub-application hosting, this causes 404.

Expected behavior

• Generated URL should respect app pathbase (e.g., /server) or use ~/api/... / pathbase-aware URL generation.

Additional notes

• abp.appPath and <base href> are correctly set to /server/.
• Other assets became pathbase-correct after our config changes.
• The profile-picture image URL remains root-relative.

Please advise whether this is a known issue and if there is an official fix/workaround planned.