Welcome to the Alteryx Knowledge Base
Created/Edited -
Alteryx Service is failing to start after an upgrade from an older version to 2023.1 when using DNS Alias as Gallery URL
Alteryx Server 2023.1 +
Alteryx Service is failing to start after an upgrade from a previous version to 2023.1 when using DNS Alias as Gallery URL.
The service fails to start and provides a number of errors related to WebAPI where the Gallery service is unable to start.
2023-08-07 13:57:15.219000,DEBUG,11396,AlteryxService,,,,,,,,,"ServicePluginGallery_WaitForStartupImpl: Waiting for startup, gallery manager state <0>"
2023-08-07 13:57:15.451000,WARN,11396,AlteryxService,,,,,,,,,"WebapiDaemon_Ping_Failed: Response code <404>"
"AlteryxService_LogStartupError: There was an error starting the Alteryx Service <Gallery Service failed to start in a timely fashion, exiting.>"
Alteryx Service is failing to start after an upgrade as the older version of Alteryx doesn't have WebAPI and canonical names configuration in the Alteryx System Settings. This allows the server to pick the default localhost/WebAPI instead of the correct URL.
Consider the below example and change the relevant information as per the internal configuration
Domain name - example.com
Server hostname - Server1
FQDN of the Server - Server1.example.com
DNS Alias - Alteryx.example.com
Solution A:- When no SSL is enabled
Configure the Gallery URL as per the below screenshot [change the URL as per the organization's recommendation]
Solution B:- When SSL is enabled
Check if the Certificate is Valid
Check if the certificate has a hostname, DNS Alias, and FQDN as part of the certificate SAN
Check if the certificate is installed and bound to port 443 using "netsh http show sslcert" command
Configure the Gallery URL as per the below screenshot [change the URLs as per the organization's recommendation]