Hi!
We installed a staging environment for DVLS following this guide: https://docs.devolutions.net/server/kb/how-to-articles/create-server-staging-instance/
However, we have the production instance running at the root URL (https://dvls.example.com/ rather than https://dvls.example.com/dvls)
The staging instance is now a nested application within the production instance, at https://dvls.example.com/staging.
While installing and updating the staging instance, I got some errors in the log:
Dateiname: \\?\C:\inetpub\wwwroot\staging\web.config
Zeilennummer: 60
Fehler: Doppelter Auflistungseintrag vom Typ "add" mit auf "aspNetCore" festgelegtem eindeutigen Schlüsselattribut "name" kann nicht hinzugefügt werden.
Unable to configure feature delegation. Please ensure the feature delegation is set to Read/Write for these features:
- Authentication - Windows
- Handler Mappings
- Modules
That German error translates to: Cannot add duplicate collection entry of type 'add' with unique key attribute 'name' set to 'aspNetCore'
After I added <remove name="aspNetCore"/> before that line in web.config and restarted the application pool, everything worked.
I was just wondering if this can be considered a bug, and if you can add fixes that would allow nested instances without errors and manual editing of the web.config file. Maybe you can disable inheritance of those settings in nested application directory.
Otherwise you could update documentation and/or create a check during install, to state that creating nested instances is not supported. In that case, an alternative way could be to create another IIS site and use a different host name or port for the staging instance.
Also, we are using the stable version, so this might be different in 2025.3, but I didn't test that. (production was 2025.1, staging was 2025.2)
Thank you!
Best regards,
Daniel