AdminCP https problem

[mikez006]

I upgraded to 4.2.3 today from the version before.

Everything appears to be workings, however I am running into one bug I can't figure out.

In AdminCP anytime I update a setting I get a blank page after. Or if I'm viewing a user's profile on the site and click "Edit Profile" I also get a blank page.

I checked Google "inspect" and it appears there's an HTTPS problem. The error is below.


Mixed Content: The page at 'https://www.domain.com/admincp/....' was loaded over HTTPS, but requested an insecure resource 'http://www.domain.com/admincp/user.php....'. This request has been blocked; the content must be served over HTTPS.


On the Site Name URL settings page in admin, I'm using https://www.domain.com, so everything should be https.

I disabled the Plugin/Hook System and also tried changing the adminCP skin, but neither worked.

I can't figure out why these pages are loading with http only. Any ideas?

[Blutengel]

Same problem here.

use 4.2.2pl1

if we want to change a user from profile, the sidebar in admincp loaded but user.php not

Mixed Content: The page at 'https://www.host.tld/admincp/index.php?loc=user.php%3Fdo%3Dedit%26u%3D4412' was loaded over HTTPS, but requested an insecure resource 'http://www.host.tld/admincp/options.php?do=options&dogroup=address&advanced=0'. This request has been blocked; the content must be served over HTTPS.

[hugoroger]

Have you guys tried reading this: How to fix a website with blocked mixed content

Have you checked if you have any source serving http instead of https?

Change the src="http://linkToUrl.com" to

src="//linkToUrl.com/script.js"

Or did you guys try running a replacement variable to your style?

[Kane@airrifle]

There are some hardcoded HTTP links in admincp/index.php. Edit same to HTTPS.

Just the ones that call to vbulletin.com

[RichieBoy67]

While you are working on this issue you can use firefox and click on the lock icon and you can disable the https from there. I would do this only as a temporary measure.

BTW - The 4.2.5 betas work well with https://.. also search this forum because we discussed this in depth. I had many of these issues myself.