Good evening MJ-Team!

I've just installed MJ-2.1.21 following the official site and guidelines and both administrator-site and user-site have been marked as "unsafe" as soon as I reloaded them:
pasteboard.co/GNfxQ5f.png
pasteboard.co/GNfzCT5.png
My site runs on HTTPS protocol (force-HTTPS), but as soon as MJ-2.1.21 has been installed every page I visit has turned to being "unsafe", both by PC and by Mobile.

In addition to this issue (which I tried to debug/find cause of but with no result after few hours or searching in this Forum and in the Net), GChrome DevTool window, under "Elements" tab is showing these errors:
pasteboard.co/GNfGfAK.png
Under the "Network" tab these detailes are visible:
pasteboard.co/GNfI14Z.png

These are my system information:
pasteboard.co/GNfMJgs.png

Note: all the installation requirements were met, I double-checked everything before proceeding to install MJ and I even back-up'd the whole site due working on the official template I'm using.
I never had similar issues after installing any other additional feature.


Hopefully waiting for Support since the site I'm working on has to be safe and usable 24/7.
Sincerely,
Simone

Hello Simone,

Thanks for the screenshots.

Mobile Joomla should not affect the SSL of your site.

Please send us a temporary admin login to our email This e-mail address is being protected from spambots. You need JavaScript enabled to view it and the URL of this thread so that we can further investigate the issue.

Best,

John Mark C.
Mobile Joomla! Support

john.causing wrote:

Hi Mark!
I've managed to track down and resolve the issue and it's actually MJ fault for the SSL "unsafe" warning. Two of the images you've loaded in the administrator-side interface are parsed by HTTP protocol instead of HTTPS protocol, thus leading "unsafe page" warnings on sites where HTTPS is force-on-all-site.

You need to change the URL-origin of those images (screenshot: pasteboard.co/GNxWVMF.png) from HTTP to HTTPS to prevent this. I've resolved the issue by hard-removing any code parsing/redirecting to them and everything went back to normal.


Sincerely,
Simone