I have a web database that worked well for several years on dedicated a Win 2008 Server, with file-based WC, Apache 2.2 and an SSL domain.

Now I found a cheaper VPS hosting, with Win 2012R2 Server, and copied everything from the old server to the new one and changed the DNS over etc.

The system runs fine on the new server ON PORT 80, but as soon as I try https://... I'm getting the error This site can’t be reached ... took too long to respond.

The only thing different in my mind is the new IP address and Win2012 instead of Win2008. The Win Firewall IS opened for httpd.exe for all ports.

Do I need to re-request the SSL certificate from the SSL-place by re-generating a CSR from the new server with its different IP address? But I thought the SSL cert is IP-address agnostic?

Any other suggestions?

THANKS so much in advance! 😃 Hermann

That just sounds like your certificate is not installed or available. I think when you move your site you need to reimport the certificate, but I don't know how that works in Apache.

First thing to do always is see what happens when you access a plain, static HTML page. What does the server do with that?

+++ Rick ---

Hello Rick! Yes, the server runs just fine with HTTP. Only the HTTPS gives the connection timeout. I opened the firewall, etc. but I just don't have any idea how to debug that. The c:\apache22 folder is copied identical from an Win 2008 server to the Win2012R2, and normally that's all one really needed to to in the past, plus running the httpd.exe -k to make it into a service. Could I buy some consulting time from you and we'll try to tackle it in a Teamviewer session? 😃 Hermann P.S.: I don't have a must-have on Apache, if you can make IIS work on that Win2012R2 machine with my file-based app, that would also be perfectly fine.

I can take a look but I know next to nothing on how to configure Apache, so not sure how much help that is.

If Http works and https doesn't it's almost certainly an issue with the certificate not being installed properly or the bindings not being correct. There's nothing on the Web Connection end that changes and for the server nothing should really change either except for the site bindings to port 443 and the certificate set up.

+++ Rick ---