November 28, 2017 at 11:48 am
Hi,
Can any one tell me how to change my web portal URL for my SSL site? When I import my certificate it populates my URL for the site, but it is using the FQDN.
This URL works
https://servername.domain_name/Reports
This gives a 404 error
https://servername/Reports
I can see in the reportserver.config that its got the URL as the FQDN. If I change it here and remove the domain_name part, it of course breaks the portal.
Why does the ULR have to be FQDN?
I'm thinking its how the certificate got made .
The certificate has a friendly name of the server_name
and in the subject Alternative names it has both servername and servername.domain_name So why does the config manager make the URL FQDN?
I'm thinking that the SSRS config manager gets the FQDN from the Subject area of the cert that is set to CN=Servername.Domain_name but I'm not sure and maybe SSRS SSL requires the URL to be FQDN? Has anyone run in to this problem or know why? I searched the Kbase but didn't find any thing and searches on line show examples of SSL that are not FQDN.
Thanks,
November 28, 2017 at 9:49 pm
scribesjeff - Tuesday, November 28, 2017 11:48 AMHi,
Can any one tell me how to change my web portal URL for my SSL site? When I import my certificate it populates my URL for the site, but it is using the FQDN.
This URL works
https://servername.domain_name/Reports
This gives a 404 error
https://servername/Reports
I can see in the reportserver.config that its got the URL as the FQDN. If I change it here and remove the domain_name part, it of course breaks the portal.
Why does the ULR have to be FQDN?
I'm thinking its how the certificate got made .
The certificate has a friendly name of the server_name
and in the subject Alternative names it has both servername and servername.domain_name So why does the config manager make the URL FQDN?
I'm thinking that the SSRS config manager gets the FQDN from the Subject area of the cert that is set to CN=Servername.Domain_name but I'm not sure and maybe SSRS SSL requires the URL to be FQDN? Has anyone run in to this problem or know why? I searched the Kbase but didn't find any thing and searches on line show examples of SSL that are not FQDN.
Thanks,
check in report config manager to change the same, if it is not possible check with DNS team for why only FQDN has issues while connecting.
Regards
Durai Nagarajan
November 29, 2017 at 4:02 pm
Hi,
The answer is ......Its the certificate. I had a new one made and didn't use and FQDN in any of the fields. and now it auto populates with the friendly name not the FQDN. On the down side if you try to connect to the server with the FQDN it now fails. I'm no certificate expert so there maybe a way to configure the cert with both names but for now it seems you either go FQDN or friendly name.
Thanks!
Jeff
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply