Title: non-secure site (http) became secure site (https) after migration
Last modified: August 30, 2016

---

# non-secure site (http) became secure site (https) after migration

 *  Resolved [unique5555](https://wordpress.org/support/users/unique5555/)
 * (@unique5555)
 * [10 years, 10 months ago](https://wordpress.org/support/topic/non-secure-site-http-became-secure-site-https-after-migration/)
 * I created this site on my local MacbookPro as a non-secure site. Then I used 
   the Duplicator plugin to create an archive and installer. I FTP’ed it to my host
   server and installed it. When I then tried to view the site, it would only appear
   as a secure site (https) indicating there was a certificate required and it wouldn’t
   display content images.
 * I went into settings/general and discovered that the URL settings had changed.
   I managed to correct the problem manually, but for future reference, I’d like
   to know what happened and why.
 * [http://www.wellsorganization.com](http://www.wellsorganization.com)
 * [https://wordpress.org/plugins/duplicator/](https://wordpress.org/plugins/duplicator/)

Viewing 3 replies - 1 through 3 (of 3 total)

 *  [Cory Lamle](https://wordpress.org/support/users/corylamleorg/)
 * (@corylamleorg)
 * [10 years, 10 months ago](https://wordpress.org/support/topic/non-secure-site-http-became-secure-site-https-after-migration/#post-6391882)
 * Hey Unique,
 * In the settings page where both values set as SSL?
 * > WordPress Address (URL)
   >  Site Address (URL)
 * On step 2 of the installer there are two separate entries for each of these values.
   One of them is under Advanced options. This is the only place where the plugin
   pulls from to update the DB values for those entries, when your site is copied.
 * If you entered http in both but still got https then something may be setup in
   an htaccess, htconfig or possible another plugin (sometimes security plugins 
   will update these files and the DB). Those are the most prevalent reason that
   I can think of for this situation. If those aren’t the underlying reasons, I’m
   100% sure as no one has ever reported that issue before…
 * Hope that helps!
 *  Thread Starter [unique5555](https://wordpress.org/support/users/unique5555/)
 * (@unique5555)
 * [10 years, 10 months ago](https://wordpress.org/support/topic/non-secure-site-http-became-secure-site-https-after-migration/#post-6391883)
 * Cory:
 * Thanks for the help. I was starting to think there was no solution. I’m in the
   middle of another project at the moment, but I’ll check this out in the next 
   couple of days and let you know if that was the problem.
 * Thanks again for taking the time.
 *  [Cory Lamle](https://wordpress.org/support/users/corylamleorg/)
 * (@corylamleorg)
 * [10 years, 10 months ago](https://wordpress.org/support/topic/non-secure-site-http-became-secure-site-https-after-migration/#post-6391919)
 * Sounds good! Thxs for the udpate….

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘non-secure site (http) became secure site (https) after migration’ is
closed to new replies.

 * ![](https://ps.w.org/duplicator/assets/icon-256x256.png?rev=2906985)
 * [Duplicator - Backups & Migration Plugin - Cloud Backups, Scheduled Backups, & More](https://wordpress.org/plugins/duplicator/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/duplicator/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/duplicator/)
 * [Active Topics](https://wordpress.org/support/plugin/duplicator/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/duplicator/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/duplicator/reviews/)

 * 3 replies
 * 2 participants
 * Last reply from: [Cory Lamle](https://wordpress.org/support/users/corylamleorg/)
 * Last activity: [10 years, 10 months ago](https://wordpress.org/support/topic/non-secure-site-http-became-secure-site-https-after-migration/#post-6391919)
 * Status: resolved