Title: Problem jetpack changing http to https for WP reader so saying site not connecte
Last modified: May 19, 2018

---

# Problem jetpack changing http to https for WP reader so saying site not connecte

 *  Resolved [lafren](https://wordpress.org/support/users/lafren/)
 * (@lafren)
 * [8 years ago](https://wordpress.org/support/topic/problem-jetpack-changing-http-to-https-for-wp-reader-so-saying-site-not-connecte/)
 * it is happening randomly. I have several sites connected through jetpack to WordPress
   reader. My https site does not have a problem. my http blogs have a problem because
   jetpack randomly adds an s so https to the site address — I have checked this
   by clicking on view site. When this happens, people in wordpress reader cannot
   access my site in reader (clicking on post link or the like). I don’t know if
   I am losing stats when this happens — maybe because Google Analytics always shows
   more hits but that might be because Google is more accurate recording hits.
 * This has been going on for several months — a few followers have switched from
   using reader to get to my site and just go directly. There is no problem using
   direct links as http always works. it’s taken awhile to find out that is only
   happening if they try to access my site from reader and is random, not all the
   time. I thought at first I needed to update something so when I first saw it,
   I would just go to the site to update but that was not the problem. Took awhile
   to figure it out because I had to be on when someone complained to check if it
   was the site going down– which it wasn’t. Some checking after that narrowed it
   down to only people trying to visit my site from the reader. It is only a problem
   with my .org — hosted sites. It is not a problem with my wp.com blog — that one
   always seems to be connected into the reader correctly. It seems to only happen
   about 10% of the time if that but it’s still a problem.
 * The problem is jetpack usually doing http for the http site and then randomly
   for hours at a time suddenly doing https even though that is not the site address
   and never has been. Since there is no https site, browser come back with an error
   code of site not found. There needs to be a way to fix jetpack so that it only
   goes to the address as inputted which is http and not randomly change it to https.
 * It just cleared itself again. The only way to see it happening easily is to be
   in reader, on the stats page, if the red circle is up “can’t connect to site”,
   then it is happening.

Viewing 1 replies (of 1 total)

 *  [Gemma Evans](https://wordpress.org/support/users/gemmaevans/)
 * (@gemmaevans)
 * [8 years ago](https://wordpress.org/support/topic/problem-jetpack-changing-http-to-https-for-wp-reader-so-saying-site-not-connecte/#post-10304254)
 * Hi [@lafren](https://wordpress.org/support/users/lafren/),
 * Can you post your site URL here, so I can take a look?
 * If you want that information to remain private, you can also contact us via this
   contact form:
 * [https://jetpack.com/contact-support/?rel=support](https://jetpack.com/contact-support/?rel=support)
 * Thanks!

Viewing 1 replies (of 1 total)

The topic ‘Problem jetpack changing http to https for WP reader so saying site not
connecte’ is closed to new replies.

 * ![](https://ps.w.org/jetpack/assets/icon.svg?rev=2819237)
 * [Jetpack - WP Security, Backup, Speed, & Growth](https://wordpress.org/plugins/jetpack/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/jetpack/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/jetpack/)
 * [Active Topics](https://wordpress.org/support/plugin/jetpack/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/jetpack/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/jetpack/reviews/)

 * 1 reply
 * 2 participants
 * Last reply from: [Gemma Evans](https://wordpress.org/support/users/gemmaevans/)
 * Last activity: [8 years ago](https://wordpress.org/support/topic/problem-jetpack-changing-http-to-https-for-wp-reader-so-saying-site-not-connecte/#post-10304254)
 * Status: resolved