Preload problems when using different https admin url

  • Resolved Kona Macphee

    (@kona)


    10 years, 1 month ago

    I have a number of sites, running on the same VPS, that don’t individually need a secure cert for anything except website admin.

    Rather than buying certs for each site, I therefore use the host shared cert to administer all of them.

    Thus, for example, the site:
    http://www.mysite.com

    might be administered via:
    https://vps.hostco.com/~siteuser/wp-admin/

    (Made-up domain names – but in other words, the admin domain is different and the website’s CPanel account name is included in the admin URL.)

    I’m finding that cache preload fails completely under these circumstances (but if I fall back to using the “real” domain and no https for admin, cache preload works fine.)

    Any suggestions for getting cache preload working in these circumstances?

    Thanks!

    https://wordpress.org/plugins/wp-super-cache/

Viewing 3 replies - 1 through 3 (of 3 total)
  • Thread Starter Kona Macphee

    (@kona)

    10 years, 1 month ago

    PS I’m using the wordpress-https plugin to manage the secure admin redirection.

    Thread Starter Kona Macphee

    (@kona)

    10 years, 1 month ago

    PPS By “fails completely”, I mean that no cache files are generated, and the preload request seems to disappear – I don’t, for example, get a status message on the Preload page telling me that a preload is currently active or where it’s up to in terms of file count, which I *do* see when logging in without HTTPS and domain redirect.

    Thread Starter Kona Macphee

    (@kona)

    10 years, 1 month ago

    Ok, after a full reinstall it seems to be working with https now.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Preload problems when using different https admin url’ is closed to new replies.