asked on DNS / SSL Error
On a winfows 2012 member server we are running IIS 8 for one application only. I have setup my SSL for the site and if I type in https://x.x.x.x/Appname i get the usual warning about SSL not matching but it all works. In IIS bindings under ssl i added the domain name to match the ssl cert. Then if I try it i get a 404 error. If I try to use https://domainname/appname I get page not found. I do have the DNS which is hosted by aplus.net point the www only to the ip address of this server. What am I missing here? I need to be careful on the aplus.net side as this domain is used only for it's ftp services and I do not wish to mess that up. We will not be using port 80 at all so on the firewall I only have 443 pointing to the server and as i said https://x.x.x.x/Appname works. I hope i've explained this correctly. Any thoughts anyone?
Microsoft IIS Web ServerSSL / HTTPSWindows Server 2012
Last Comment
Ralph Gould
so, your certificate is for server.domain.com and you are going to https://server.domain.com ?
ASKER
cert is for www.domain.com and i'm trying to go to https://www.domain.com/APPNAME. I'm not using a subdomain. created the cert request from IIS8. IIS8 has added the binding to it. It's set in IIS8. Hopefully i answered that correctly.
SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
ok. i have the www a record pointing to that address but nothing else because i want to make sure ftp.domainname.com still functions off the webhosting account as it is in use. other then that the domain is only there is for ftp use. that's why we thought we could utilize the www.domainname.com. let me double check all dns settings. do i need to add the name www.domainname.com into the IIS bindings section. as of right now i have nothing there for 80 or 443. and 443 already is pointing. if i go by straight ip address https://1.1.1.1/Appname it works once you go past the certificate warning in the web browser. i'll double check those dns settings
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
so nslookup was showing me the causing the issue. i didn't realize DNS changes where being made to a utility domain name and not the website domain name. So far still not working though. made the correct changes. nslookup is reporting the correct ip address now. May need DNS to make it's way around some more not sure. https://ipaddress/appname still does work however
ASKER
Great work guys. Thank you!