Https redirection is not triggerring the FQDN but the @IP instead. Exemple : https://84.39.xx.xxx/jenkins/view/All/job/ClusterUpgradeWebcomwsWithStopAndStart/
SInce my Jenkins setup user identification is retrieved from HTTP Header by reverse proxy, https redirection is blocked for security alert i.e. the redirect https URL based on public @IP is not matching the FQDN based built LetsEncrypt certificate.
Why don't you trigger the former Jenkins URL based on FQDN. Exemple : https://ip-84-39-xx-xxx.rev.cloudwatt.com/jenkins/view/All/job/ClusterUpgradeWebcomwsWithStopAndStart/
Thanks for your help.
Best Regards. Richard