Title: Protocol changed from HTTP to HTTPS after pulling
Last modified: August 31, 2016

---

# Protocol changed from HTTP to HTTPS after pulling

 *  [LeonardShelby](https://wordpress.org/support/users/leonardshelby/)
 * (@leonardshelby)
 * [10 years, 2 months ago](https://wordpress.org/support/topic/protocol-changed-from-http-to-https-after-pulling/)
 * I just pulled the database from my production site, which uses HTTPS, to my development
   site, which uses HTTP. Now I am unable to access my development site.
 * When I type the URL of my development site, specifically with HTTP, the URL of
   the development site changes itself to HTTPS as the protocol, with a red slash
   over the HTTPS. On the web page itself, it just says “404 Not Found”. Below that,
   it says “The server can not find the requested page: dev.greenbee-web.com/ilaimh/(
   port 443)”.
 * Is there a specific WordPress configuration file, that determines which protocol
   a website uses, that was over-written by the WP Migrate DB PRO database pull?
   Which WordPress file would it be?
 * Thank you for your help.
 * [https://wordpress.org/plugins/wp-migrate-db/](https://wordpress.org/plugins/wp-migrate-db/)

The topic ‘Protocol changed from HTTP to HTTPS after pulling’ is closed to new replies.

 * ![](https://ps.w.org/wp-migrate-db/assets/icon.svg?rev=2851356)
 * [WP Migrate Lite - Migration Made Easy](https://wordpress.org/plugins/wp-migrate-db/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/wp-migrate-db/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/wp-migrate-db/)
 * [Active Topics](https://wordpress.org/support/plugin/wp-migrate-db/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/wp-migrate-db/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/wp-migrate-db/reviews/)

 * 0 replies
 * 1 participant
 * Last reply from: [LeonardShelby](https://wordpress.org/support/users/leonardshelby/)
 * Last activity: [10 years, 2 months ago](https://wordpress.org/support/topic/protocol-changed-from-http-to-https-after-pulling/)
 * Status: not resolved