SharePoint On-Prem URL Issue

[DeaconFrost]

Any SharePoint admins? I was tasked with setting up an on-prem SharePoint server to be able to compare Project Server on-prem with our hosted Office 365 platform. I've been able to get it working using http://servername/sites/whatever. So far, so good. AD sync is working, I was able to send invites, etc.

I decided to update the IIS bindings to use a URL and SSL certificate. I've done this hundreds of times in IIS. I left port 80, added 443, bound it to the cert. I added the URL in the hostname field, project.domain.com. All seemed good.

I was able to log in remotely from my laptop using the https://project.domain.com URL. Cert looked good. Errors all over the place, even when trying to share the site with another user. I log back in to the server via RDP, and I can't even log in to Sharepoint at all there, using the same account. My only "solution" at this point was to revert all bindings back to the defaults, with the hostname field blank. So, my question is, is there somewhere within Sharepoint itself that I need to specific the URL for the site...so instead of being servername/ it can be project.domain.com? I have no idea why adding the hostname to the IIS binding broke basic functionality, unless I missed a step in where to specify.

 

[ziorus]

Heya, not sure if you had solved your problem yet, but it seems you did not set your Alternate Access Mapping. Here is a link about how to change a SP Web App from HTTP to HTTPS.

https://griffindocs.wordpress.com/2013/03/20/sharepoint-2013-how-to-add-ssl-to-a-web-application/

 

[DeaconFrost]

Thanks for the link. I can save it now. I was only adding HTTPS and bindings in IIS. Didn't do the Extend portion in Web Applications from without Sharepoint. I have it running on the proper URL and using an SSL cert now. Thanks!