I understand but if the web engine is running via the web server binary, you'd have to fix that binary.
If the pages are being served via IIS, spend 15 minutes and install the SSL cetificate. See what is listening on :80 right now - netstat -aon|findstr :80 On Wed, Nov 4, 2026 at 1:04 PM Ken Hohhof <[email protected]> wrote: > I believe it’s Windows Server 2012. > > > > *From:* AF <[email protected]> *On Behalf Of *Joe Novak > *Sent:* Wednesday, November 4, 2026 11:45 AM > *To:* AnimalFarm Microwave Users Group <[email protected]> > *Subject:* Re: [AFMUG] site can't be reached using Chrome > > > > If the Windows version is recent, installing SSL certificates in IIS > probably won't be too terrible. I'm sure someone has a script for Let's > Encrypt that mostly automates the process for you. If it's virtual you can > always take a snapshot before hand. > -- > AF mailing list > [email protected] > http://af.afmug.com/mailman/listinfo/af_af.afmug.com >
-- AF mailing list [email protected] http://af.afmug.com/mailman/listinfo/af_af.afmug.com
