I have read all the posts I can find on this subject and I'm still struggling! A lot of what I've read was posted in 2011 etc so I'm hoping there might now be better/simpler solutions...
I currently host my website myself via V11 WAS. All was fine until we had an issue with a Ransome virus intruder coming in via an RDP port on one of our pc's. I have now installed RDPGuard and am attempting to install VPN. However, the VPN was demanding an SSL - I think - so I've purchased and installed one of those. (The intruder was logging as Administrator so we've enabled the Administrator, changed the password and then disabled it, setting password to non-changeable).
The WAS is on it's own PC/server on our network.
Meanwhile, as others have experienced, since installingb the ssl, www.myurl.com does not work; only https://www.myurl.com works.
I tried running a second instance of WAS, but it will not allow port 80 and port 443 in the other WAS.
Should I now learn how to setup IIS and redirect from port 80 there?
Or should I put some redirect html into 'Inc_logintxt.a5w' if I can find out what that means...
Or is the issue with my DNS settings at 123reg, our domain name supplier?
Or should I do something else altogether?
Or... does someone want to 'Teamviewer' onto my WAS and do the job for me?
There are simply too many options for us, i.e. WAS settings, DNS and web forwarding at 123reg as well as router settings.
I currently host my website myself via V11 WAS. All was fine until we had an issue with a Ransome virus intruder coming in via an RDP port on one of our pc's. I have now installed RDPGuard and am attempting to install VPN. However, the VPN was demanding an SSL - I think - so I've purchased and installed one of those. (The intruder was logging as Administrator so we've enabled the Administrator, changed the password and then disabled it, setting password to non-changeable).
The WAS is on it's own PC/server on our network.
Meanwhile, as others have experienced, since installingb the ssl, www.myurl.com does not work; only https://www.myurl.com works.
I tried running a second instance of WAS, but it will not allow port 80 and port 443 in the other WAS.
Should I now learn how to setup IIS and redirect from port 80 there?
Or should I put some redirect html into 'Inc_logintxt.a5w' if I can find out what that means...
Or is the issue with my DNS settings at 123reg, our domain name supplier?
Or should I do something else altogether?
Or... does someone want to 'Teamviewer' onto my WAS and do the job for me?
There are simply too many options for us, i.e. WAS settings, DNS and web forwarding at 123reg as well as router settings.