Title: HTTPS to HTTPS – not working Last modified: February 20, 2017 --- # HTTPS to HTTPS – not working * [Georg](https://wordpress.org/support/users/revzp/) * (@revzp) * [9 years, 2 months ago](https://wordpress.org/support/topic/https-to-https-not-working/) * Hi rafasashi, first, thank you for this excellent plugin and would like to ask if is not in your code bug? I had already tested that option [http://www.domain.com](http://www.domain.com) to [http://www.domain.com/another_wp/](http://www.domain.com/another_wp/) and is OK. But now I had to switch to the installations WP on the https protocol which is fully working, but the same variation with just https does not work.( [https://www.domain.com](https://www.domain.com) to [https://www.domain.com/another_wp/](https://www.domain.com/another_wp/)) If you look through Chrome – Network – I see the error “?ussync-token = XXXXX….” blocked: mixed-content (size 0B) (I see http URL) (I have installed the latest version of the plugin version 1.3.4) * Second question: Does to be functional, among other installations WP also admin account? Or does it have to be functional only for users? * Thanks for your assistance. * Georg Viewing 8 replies - 1 through 8 (of 8 total) * Plugin Author [rafasashi](https://wordpress.org/support/users/rafasashi/) * (@rafasashi) * [9 years, 2 months ago](https://wordpress.org/support/topic/https-to-https-not-working/#post-8825452) * Hi Georg, * Thanks for using the plugin and for your feedback! * The reason why you have this error is because right now the plugin take the current protocol (from the synchronizing site) and use it to build the iframe urls. * Therefore it doesn’t support mixed protocols (part http and https). * The ability to use mix protocols might be included in the future but it is not a priority right now. * I let you know if there is any improvement on this side. * Thread Starter [Georg](https://wordpress.org/support/users/revzp/) * (@revzp) * [9 years, 2 months ago](https://wordpress.org/support/topic/https-to-https-not-working/#post-8825606) * Hi rafasashi, * OK, thank you for your very quick answer and just do not understand why you can not call also inner iframe https instead of http. This would eliminate the problem, or am I wrong? As I watched – it would help to others 😉 * Furthermore, I would have asked for the answer to the second question. 🙂 * Thank you * Georg * Thread Starter [Georg](https://wordpress.org/support/users/revzp/) * (@revzp) * [9 years, 2 months ago](https://wordpress.org/support/topic/https-to-https-not-working/#post-8826253) * Hi rafasashi, * I solved the first thing therefore mixed content (communication only via the HTTPS protocol). * _**If someone will have the same problem as I just use existing one plugin = Really Simple SSL, which solves this trouble.**_ * Now I just missing the answer to the second question. It is possible to do synchronization for admin accounts? * Thanks for your assistance * Georg * Plugin Author [rafasashi](https://wordpress.org/support/users/rafasashi/) * (@rafasashi) * [9 years, 2 months ago](https://wordpress.org/support/topic/https-to-https-not-working/#post-8826287) * Sorry I missed the 2nd question. * The synchronization is done regardless the user role. Right now the users added automatically take the default role from general settings. If you want to make one admin you will have to do it manually from a super admin session. More role management features are coming next. * [VP](https://wordpress.org/support/users/studio500/) * (@studio500) * [9 years, 2 months ago](https://wordpress.org/support/topic/https-to-https-not-working/#post-8847302) * Hi, As Google pushes more users to change to https as I have now done with all of my sites, does that mean that this plugin will no longer work in its present form? * I’m trying to link two https sites also. * The default web address that is shown in the plugins site box look like * mysite.com mysite2.com * I changed this to: * [https://mysite.com](https://mysite.com) [https://mysite2.com](https://mysite2.com) * Was this the correct move or should I have left the site address with what the plugin detected as mysite.com only, without the https prefix? * Would this have worked or is there currently no support for https? * I hope you don’t mind me adding this question onto this current topic. * Regards * Plugin Author [rafasashi](https://wordpress.org/support/users/rafasashi/) * (@rafasashi) * [9 years, 2 months ago](https://wordpress.org/support/topic/https-to-https-not-working/#post-8847324) * From 1.3.5 it should be ok to synchronize two https installations. Let me upgrade it… - This reply was modified 9 years, 2 months ago by [rafasashi](https://wordpress.org/support/users/rafasashi/). * [VP](https://wordpress.org/support/users/studio500/) * (@studio500) * [9 years, 2 months ago](https://wordpress.org/support/topic/https-to-https-not-working/#post-8848486) * Many thanks Rafasashi, I think it’s well worth doing as more websites are being urged to install SSL as part of Googles new push in relation to rankings etc. * Great job btw. * Plugin Author [rafasashi](https://wordpress.org/support/users/rafasashi/) * (@rafasashi) * [9 years, 2 months ago](https://wordpress.org/support/topic/https-to-https-not-working/#post-8848502) * You should be able now. Viewing 8 replies - 1 through 8 (of 8 total) The topic ‘HTTPS to HTTPS – not working’ is closed to new replies. * ![](https://ps.w.org/user-session-synchronizer/assets/icon-128x128.jpg?rev=1872027) * [User Session Synchronizer](https://wordpress.org/plugins/user-session-synchronizer/) * [Frequently Asked Questions](https://wordpress.org/plugins/user-session-synchronizer/#faq) * [Support Threads](https://wordpress.org/support/plugin/user-session-synchronizer/) * [Active Topics](https://wordpress.org/support/plugin/user-session-synchronizer/active/) * [Unresolved Topics](https://wordpress.org/support/plugin/user-session-synchronizer/unresolved/) * [Reviews](https://wordpress.org/support/plugin/user-session-synchronizer/reviews/) ## Tags * [HTTPS](https://wordpress.org/support/topic-tag/https/) * 8 replies * 3 participants * Last reply from: [rafasashi](https://wordpress.org/support/users/rafasashi/) * Last activity: [9 years, 2 months ago](https://wordpress.org/support/topic/https-to-https-not-working/#post-8848502) * Status: not resolved