Will Master's Bloghttps://ecaps.wordpress.com
Simply LifeTue, 23 Jan 2018 22:39:45 +0000enhourly1http://wordpress.com/https://s2.wp.com/i/buttonw-com.pngWill Master's Bloghttps://ecaps.wordpress.com
How to install missing ifconfig command on CentOS 7https://ecaps.wordpress.com/2018/01/23/how-to-install-missing-ifconfig-command-on-centos-7/
https://ecaps.wordpress.com/2018/01/23/how-to-install-missing-ifconfig-command-on-centos-7/#respondTue, 23 Jan 2018 22:37:39 +0000http://ecaps.wordpress.com/?p=603yum install net-tools
]]>https://ecaps.wordpress.com/2018/01/23/how-to-install-missing-ifconfig-command-on-centos-7/feed/0ecapsForce HTTPS On All Pages Of Your Website and WordPress Sitehttps://ecaps.wordpress.com/2017/12/08/force-https-on-all-pages-of-your-wordpress-site/
https://ecaps.wordpress.com/2017/12/08/force-https-on-all-pages-of-your-wordpress-site/#respondFri, 08 Dec 2017 02:45:16 +0000http://ecaps.wordpress.com/?p=597This is the thing that got me when I was making the full transition to HTTPS for my blog. After changing the site name, all my CSS and JavaScript assets were still coming in with the HTTP URL path rather than HTTPS. This caused my site to appear broken in pretty much every browser.

These site asset files can easily be corrected by fixing the rewrite rules in your .htaccess file found at the root of your WordPress application.

Notice the highlighted lines in the above code. We’re saying that if the current port isn’t 443, then rewrite the URL to use HTTPS with a 301 redirect. The rest of the above code should already exist in your WordPress .htaccess file. Usually it will be found at the bottom of the file.

—– For non-Wordpress site ——

If you want to force a given website or path to use https, redirected from http, you can create an .htaccess file in the DocumentRoot for that domain or hostname, and add the following code:

which will redirect any non-https connections to https using the same request and GET variables.

If your site is running through CloudFlare, your https requests to it may actually hit your server in plaintext (http), which is confusing.
For that case, you might need something like this for an http to https redirect:

]]>https://ecaps.wordpress.com/2017/12/08/force-https-on-all-pages-of-your-wordpress-site/feed/0ecapsForcing FTP SolusVM backups to run on a SolusVM slavehttps://ecaps.wordpress.com/2017/11/23/forcing-ftp-solusvm-backups-to-run-on-a-solusvm-slave/
https://ecaps.wordpress.com/2017/11/23/forcing-ftp-solusvm-backups-to-run-on-a-solusvm-slave/#respondThu, 23 Nov 2017 23:43:48 +0000http://ecaps.wordpress.com/?p=595TP SolusVM backups can get stuck on a SolusVM slave. The way SolusVM backups run is it creates an image of the server whilst it’s still running then places that image into a dump file where it stays whilst it is uploaded to your backup server. If the upload is interrupted then the image will stay in the dump file and take up space. You should remove this file and follow the below to restart the SolusVM backups.

Alternatively, “./build update_versions” can be used as well. The newest version of CustomBuild 2.0 is only available on files1.directadmin.com and files2.directadmin.com fileservers at the moment, other mirrors might take up to 24 hours to update.

2. Backing up the Original Database

You can backup your original SolusVM master database by entering the admin area and selecting System Tools > Database and clicking Send to Email or by downloading it directly.

3. Replacing the Encryption Key

Parts of your database are encoded using a unique encryption key stored in /usr/local/solusvm/includes/solusvm.conf. You need to make a copy of the encryption key on the original master and replace it on the new master.

The format of the solusvm.conf is as follows:

example: <DATABASENAME>:<USER>:<PASSWORD>:<HOST>:<the key is the last entry>

Icon

If you miss this step, non of your passwords or slave connections will work.

4. Restoring the Database

Upload the database backup to the new master server.

You can get the new database details from /usr/local/solusvm/includes/solusvm.conf, they are seperated with ” :”.

example: <DATABASENAME>:<USER>:<PASSWORD>:<HOST>:<the key is the last entry>