Your connection is not private page on my wordpress.com address

  • Unknown's avatar
    dove88 · Member ·

    My old blog address was http://www.christiannommesen.wordpress.com, and it now forwards to christiannommesen.blog. But when people go to the old address (usually from a mobile browser), there is a “Your connection is not private – Attackers might be trying to steal your information…” message and they don’t move forward.

    Is there any way to fix that?

    (There is no problem with the new address.)

    My old address may be bookmarked, and I don’t have an easy way to notify everyone of the new address.

    Thanks for responding to a question that has probably been asked a lot. I’ve tried installing plugins, verifying the SSL looks right, reviewing the HTML code, etc.

    The blog I need help with is: (visible only to logged in users)

  • Unknown's avatar
    guduvhenio · Member ·

    This usually happens because the old wordpress.com address is trying to load over HTTPS with a certificate mismatch or redirect issue before forwarding to the new domain.

    Since your new domain (christiannommesen.blog) works correctly, the issue is most likely related to how the old mapped address is being accessed or cached in browsers rather than a problem with your current site itself.

    A few important things to know:

    • Plugins installed on the new site generally will not affect the old wordpress.com subdomain redirect behavior.
    • If the old address is still redirecting through WordPress.com, SSL handling for that subdomain is managed on the WordPress.com side.
    • Mobile browsers are often stricter about SSL/certificate warnings and may cache old redirect behavior more aggressively.

    A few things you can try:

    1. Test both versions manually:
      • http://christiannommesen.wordpress.com
      • https://christiannommesen.wordpress.com
    2. Clear browser cache/HSTS settings on affected mobile devices or test in a private/incognito window.
    3. Confirm the Site Redirect upgrade is still active and correctly pointing to: christiannommesen.blog
    4. Check whether the old subdomain still resolves properly without mixed redirects or loops.

    From your description, this sounds less like an issue with your current blog configuration and more like an SSL/redirect handling issue tied to the old WordPress.com address itself.

    A staff member may need to inspect the redirect and SSL provisioning for the old christiannommesen.wordpress.com subdomain directly, especially if the warning only appears before the redirect occurs.

  • Unknown's avatar
    dove88 · Member ·

    Thanks for the tips!

  • staff-webwizard · Staff ·

    Thank you, @guduvhenioguduvhenio, for sharing this information with @dove88!

    Hi @dove88! I checked all the addresses associated with your site and couldn’t replicate the SSL errors, so I suspect it might be a client-side issue. How many people have reported this issue, approximately?

    These are the addresses I checked, and none of them resulted in an error:

    Best,

  • Unknown's avatar
    dove88 · Member ·

    Thanks for checking!

    The issue only seems to be on https://christiannommesen.wordpress.com/.

    My friend got this from Chrome on his phone today:

    And when I try http://www.christiannommesen.wordpress.com on chrome or IE the redirect works fine, but on firefox I get:

  • staff-happychia · Staff ·

    Thanks for adding the screenshot. They show an inconsistent state of your site and that’s very strange!

    I checked your site in Chrome, Firefox, and Edge. Since you added the domain christiannommesen.blog, the long URL in your screenshots (http://www.christiannommesen.wordpress.com) now redirects to https://christiannommesen.blog, as it should.


    Your site is also displayed without any SSL errors!

    That said, your screenshots do show SSL errors. That is commonly because some problematic data is stuck in your browser. So the best first step is to clear your browser’s data. This will help us rule out any common but pesky issues that might be at play.

    You can clear your browser’s cookies using the steps here: https://wordpress.com/support/browser-issues/#clearing-word-press-com-cookies

    If it’s still a no-go after that, try restarting your internet router. Because bad data can be cached on your router as well.

    Lastly, you also check your site on your phone that is connected to the internet using the mobile internet (4G or 5G) connection, (not WiFi), by visiting either https://christiannommesen.blog/ or http://www.christiannommesen.wordpress.com/

    Let us know how you go once you complete these steps!

    Also, since you have a paid plan subscription, you can chat with our human support team by clicking the “Need help? Get in touch” at the bottom of the Help Center.

    Looking forward to hearing from you and helping you further!

  • Unknown's avatar
    dove88 · Member ·

    Thanks for the reply. I can do those steps and maybe get the error to clear on my browsers, but the error occurs on other phones and computers of people trying to access http://www.christiannommesen.wordpress.com

    So ideally, I’d like it to be fixed so other people don’t get that error, only if possible, of course.

  • Unknown's avatar
    justjennifer · Member ·

    Hi there, not staff, but when sharing your site address, don’t include the WWW. No WordPress.com website address uses www in its URL. Here’s more on that https://wordpress.com/support/www-versus-non-www-domains/

    FWIW, when I go to http://www.christiannommesen.wordpress.com/ I am redirected to https://christiannommesen.blog/ I have not visited your site before this, so anyone who has done so in the past may have the www version stuck in their browser cache. Here’s how those folks can clear their cache .

  • staff-happychia · Staff ·

    @dove88 Since this problem is caused by something in your visitors’ browsers or computers—not by your site—you only have very limited to no control over it. Everything is set up correctly on your site. However, you can provide simple instructions to visitors on how to refresh their browser cache or their network cache.

    @justjennifer Thanks for chiming in. I just want to note that there is no harm in including or sharing URLs with the www subdomain. They simply redirect to the non-www version of the URL, as mentioned in the support guide you shared.

  • Unknown's avatar
    staartmees · Member ·

    The “www.” prefix became functionally obsolete around 2010 to 2012. While the underlying technology remains the primary way we access the internet, modern web browsers and servers are designed to automatically route users to the correct address, making www mostly unnecessary.

  • Unknown's avatar
    dove88 · Member ·

    Thanks to both of you. Sounds like I just keep on keeping on.

    If I knew who was having the issue, I’d just direct them to use the christiannommesen.blog post instead of worrying about having them clear cache, etc.

    I just wondered if there was anything I could do with the old address to fix it on our end since I don’t know which of the people with the old address are having the issue, but it sounds like that isn’t the case, so I’m all good now, and glad it is confirmed that everything on the wordpress end is good.

    I appreciate everyone confirming! Thanks again all.

  • Unknown's avatar
    dove88 · Member ·

    Closing the topic.

Log in or create an account to reply