I enable remote access on my home server 2007. When i try to access from Chrome or any modern web browsers. It won't access it. I get a message saying it not safe because home server 2007 only has HTTP:// and not HTTPS://. Is there a way for me to add certificates to have it do a secure connection? Thanks for the help i get.
windows home server 2007 web certificate
- Thread starter gwb21471
- Start date
Notice: Page may contain affiliate links for which we may earn a small commission through services like Amazon Affiliates or Skimlinks.
Unless you have a very good reason to keep this system running, the best way of upgrading the certificate is by upgrading the OS. According to wikipedia, support for WHS2007 ended in 2013. Keeping that old windows server on your network is a big liability.
Windows Home Server v1 is a derivative of Windows Server 2003/Windows XP. Please, please do not expose that thing to the internet.
Do not. 100% do not. It will not end well.
If all you're doing is just serving files from a http server, there are many other, much better ways to do it. As simple, modern web server is not that difficult to set up, even on windows.
Even if you were to generate and install certificates and enable HTTPS, a system that old will not have the new ciphers and TLS versions - Browsers will reject it anyway.
Like the others, I'd recommend moving to another system. But if you want to keep it for whatever reason, you can put it behind a firewall and reverse proxy like nginx. Then you could translate the plain HTTP back-end to modern TLS.
Edit: This is not an easy task for a semi-technical home user and you will almost certainly mess it up. If you go anywhere near that server with an ethernet jack or a WiFi signal your network is basically guaranteed to be hacked and all your data stolen, bank accounts raided, credit ruined, and the next time you reboot your PCs they will all have a screen demanding payment in BTC to get your files back. For a music server it's not worth it.
Like the others, I'd recommend moving to another system. But if you want to keep it for whatever reason, you can put it behind a firewall and reverse proxy like nginx. Then you could translate the plain HTTP back-end to modern TLS.
Edit: This is not an easy task for a semi-technical home user and you will almost certainly mess it up. If you go anywhere near that server with an ethernet jack or a WiFi signal your network is basically guaranteed to be hacked and all your data stolen, bank accounts raided, credit ruined, and the next time you reboot your PCs they will all have a screen demanding payment in BTC to get your files back. For a music server it's not worth it.
Last edited:
