Upgrading from v25 to v26 - Collector server not reaching to the correct license server

Hello,

We're upgrading from v25.6 to v26.6 on our dev servers. We have a collector server and a historian/Axiom server (which has the license service installed). The historian server upgraded correctly with no issues - licensed for 2026 and capturing data with no problems. The collector server threw an error when starting the installation when it tries to check the license for current year (2026). See the image below. 

 The issue I've seen is that it reports no response. The URL of the API the installer is trying to access is the one of the collector server. I've typed the same address in a browser and gave no response.  This means that it's not a service available in the collector. Wondering if it should point to the historian server (the collector knows about it, I believe, as it has the license service) - when I tried against the historian server (which has the license service) it worked correctly, even if I change parameter to 27 (responding that my license is currently only for 2026). 

 As it was a dev server, I accepted the risks and proceeded, knowing the historian server was upgraded correctly and it's licensed properly for 2026. It worked, but the message was confusing as it seems NOT to check the license correctly.