|
Thanks, Matt! That was exactly the issue that needed to be fixed. A simple one line addition in the admin page and everything is up and running. Now, however, I have to start looking at other bits and pieces like anyplace where "http:" is hardcoded and some other issues with IP addresses. But the server is up and running with SSL! Thanks for everyone's help! Joe > From: Matt.Haas@xxxxxxxxxxx > > Joe, > > You need to modify your virtual host so it listens on port 443. By > default, it listens on port 80 and a couple of other ports that were set > up when the instance was generated.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
