Re: [webmin-l] Backup and Restore on SSL Sites

On 2/5/2017 1:42 PM, Jamie Cameron wrote:
> On 04/Feb/2017 02:50 John Hinton <[email protected]> wrote ..
>>
>> On 2/3/2017 8:29 PM, Jamie Cameron wrote:
>>> On 02/Feb/2017 09:01 John Hinton <[email protected]> wrote ..
>>>> Hi Jamie,
>>>>
>>>> Do you ever feel like telling us all to go jump in a lake? Maybe even
>>>> filled with alligators?
>>> Never! I love bug reports :-)
>> You are officially warped! Thank God. I'm not alone!
>>>> I ran a backup of a SSL site to another server. Then a restore on the
>>>> other server. It didn't pick up the apache directives. It seems to be
>>>> looking for the port 80 VirtualHost container and not seeing the port
>>>> 443 container.
>>>>
>>>> The browsers don't want mixed content, so we're rolling through
>>>> converted sites replacing all internal links and any external links that
>>>> have a https option. Once done, we're doing a permanent redirect from
>>>> http to https. From what I read, this is how it should be done... and we
>>>> know everything you read on the net it true. ;)
>>> Hmmm .. was this backup and restore done using Virtualmin? If so, it should
>>> have brought both the port 80 and 443 virtualhosts across.
>>>    
>>>
>> Yes, this was using Virtualmin.
>>
>> Here's what I'm doing:
>> 1. Create a SSL site on an existing  non-SSL Virtual Server.
>> 2. I don't see a method for killing the non-SSL version, so I manually
>> convert the port 80 entry to a permanent redirect to the port 443 site
>> manually in my apache vhost.conf file.
>> 3. Backup the Virtual Server to another system with Virtualmin.
>> 4. Restore that backup.
>>
>> I'll get around to running another one of these pretty soon and let you
>> know more about what happens.
>>
>> Or, maybe I'm doing something using a wrong method within Virtualmin?
>> Maybe Virtualmin could have a "Convert Site to SSL Only" function, which
>> would convert the port 80 side to a permanent redirect to the https
>> site? Or maybe that ability is there and I'm just dense? I've been under
>> serious sleep deprivation for the last several months. HAH!
> What I'd recommend if you want an SSL-only website is to just use the Aliases
> and Redirects feature in Virtualmin to create a redirect from the non-SSL
> site to SSL. Editing the Apache config manually will cause exactly the backup
> problem you ran into, as Virtualmin no longer be able to find it.
>
>
First, I am a fool, an idiot and someone should take away my server keys 
and license. I had forgotten to create the vhosts.conf link in the 
Apache Server configuration in Webmin. So, I created the file and cut 
and pasted those entries out of httpd.conf. Then I added vhosts.conf to 
'File or directory to add virtual server to". Doh! I didn't put in the 
complete path. So any subsequent restores were writing to 
/etc/httpd/vhostd.conf which was not an include in the main httpd.conf 
file. I didn't think Webmin would actually create the file for me. I 
have always touched it myself to start out.

Now to find that wet noodle....

And my Cloudmin replication from the old CentOS 5 box to the new CentOS 
7 box is now working as expected. :) Gosh, this is going to make this 
move easy... as long as I don't get stoooopid again.

None of these include https systems. I will work on those doing some new 
testing and see what I get. Forget all my bugs/problems for the moment 
as they were potentially self-inflicted wounds. I have noted your answer 
to that as well. I guess if I use the Redirects feature, it will convert 
the original <VirtualHost> container. I will get around to trying that.

Thanks a ton, and I am embarrassed and I apologize.

John

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
-
Forwarded by the Webmin mailing list at [email protected]
To remove yourself from this list, go to
http://lists.sourceforge.net/lists/listinfo/webadmin-list