Sign in

A Forum Install After The HTTPS Move: A Broken Padlock, Culprit Unknown

Solvedhttpsmixed-contentssl9 replies · 341 views · started
Reply
Accepted solution by Milan Weber — oh ive been there lol for WordPress, old URLs live in the database :) use WP CLI: wp search replace 'http://example.com'…
  1. Kofi Banerjee
    @kofi_tensor

    not gonna lie this is driving me nuts client called me upset cuz their browser shows a broken padlock on a forum install since teh HTTPS switch.

    i checked quickly and the stylesheet are requested with http:// URLs... some come from teh database content, some i cant trace. id rather fix it properly at teh source than install another plugin... any systematic approach you recommned? happy to dig into code or the database, i just need a sensible plan. seriously need help here 😭

    6
  2. Fenna Walsh
    @fenna_proxy

    Use protocol-correct embeds for third-party content. Old video or map embed codes often have http:// in the iframe src. replace them with the current https embed code from the provider.

    thumbsup

    1 0 helpful
  3. Milan Weber
    @milan_socket-1yz

    ok so open DevTools > Console. Each mixed content warning names teh exact insecure URL: Mixed Content: The page at 'https://...' was loaded over HTTPS, but requested an insecure resource 'http://...'... collect those URLs; the domain and path usually tell u whether its theme code, uploaded content or a third-party embed. hope that helps :)

    5 2 helpful
  4. Juno Olsen
    @juno_copper

    uhh which version are you on?. pro tip: write down what u chagne. i didnt and had to redo stylesheet from scratch

    0 5 helpful
  5. Kenji Park
    @kenji.park

    hmmm this. sooo much this worked for me anyway 🤷

    8 0 helpful
  6. Fenna Walsh
    @fenna_proxy

    reading this at 2am instead of sleeping, no regrets. wait does this also apply to broken?

    cry

    9 0 helpful
  9. Milan Weber
    @milan_socket-1yz
    Accepted solution

    oh ive been there lol for WordPress, old URLs live in the database :) use WP-CLI: wp search-replace 'http://example.com' 'https://example.com' --all-tables --dry-run, check the count, then run it without --dry-run. it handles serialized data safely, unlike a raw SQL replace.. lol take a database backup first.

    9 4 helpful

Reply to this topic

Sign in or create an account to reply.