A number of potential issues have been documented here as well:
https://docs.sdl.com/LiveContent/content/en-US/SDL%20Tridion%20Sites-v2/GUID-DA9B138D-3710-424E-AEE7-9105556B33C9While going through the Addon install from a Content Delivery perspective, the following pointers were captured, they may be helpful in other circumstances as well:
Need to know:
- addonserviceurl is set eg http://localhost:83/addon
- cdenvironment is set eg staging (this should be based on environment purpose)
- should not have multiple pipelines with same id in deployer config (or else again eg in extension config) this will not work - check deployer-conf.xml
- check services are started
- which service should be provided the addon at install/register or start?
.\installService.ps1 --auto-register '-Daddonserviceurl=http://localhost:83/addon' '-Dcdenvironment=staging'
-- deployer
-- session/content
See logs for:
-- addon service properties, set debug in logback.xml of deployer-combined
-- look for/check cdenvironment
-- look for/check addonurl
-- look for extension unzipping
To deploy extension:
- upload via the GUI interface on http://localhost:83/addon/ui
- path of extension for select eg.\Tridion Sites 9.1\Content Delivery\roles\deployer\add-ons\udp-deployer-web-extension-assembly-11.1.0-1054-core.zip
- this specific extension does not have a separate -config.json
- restart deployer service from windows services
- watch for keywords "uncompressed" to see the extension unzipped in the deployer-combined log
- after check there is a folder under deployer-combined post install with the extension zipped and unzipped called deployer-web
- path of extension post install (eg C:\SDLCDinstall\roles\deployer-combined\standalone\extensions)
- in one specific instance (for a basic development environment), the addonserviceurl variable was corrected to http://localhost:83/addon
