Symptoms:
Example:

Config file:
<secureticketauthorityurls>
<location path="http://connector.domain.local:8090/scripts/ctxsta.dll"
staValidationEnabled="off" staValidationSecret="" />
<location path="http://connector2.domain.local:8090/scripts/ctxsta.dll"
staValidationEnabled="off" staValidationSecret="" />
</secureticketauthorityurls>
<cloudGatewayConfig>
<clear />
<add url="http://connector.domain.local:8090/Control/GatewayConfig/v1" />
<add url="http://connector2.domain.local:8090/Control/GatewayConfig/v1" />
</cloudGatewayConfig>
In 2407 release, cloudGatewayConfig URL was configured with port 8090. Secureticketauthorityurls URL did not have the port configured.
<secureticketauthorityurls>
<location path="http://cloudconnector.local/scripts/ctxsta.dll"
staValidationEnabled="off" staValidationSecret="" />
</secureticketauthorityurls>
<cloudGatewayConfig>
<clear />
<add url="http://cloudconnector.local:8090/Control/GatewayConfig/v1" />
</cloudGatewayConfig>
There was a change added to the 2503 version of Storefront. The purpose of the change was to have both URLs with the same port (secureticketauthorityurls and cloudGatewayConfig).
Remove port 8090 from the Cloud Connector URL.
The purpose of this article is to describe an issue which might occur after upgrade from an older version of Storefront.
Customers should not encounter this issue during further upgrades.
The issue does not occur when a new Citrix Gateway is configured in Storefront after upgrade.