Need Help with website security certificate

Discussion in 'other security issues & news' started by beethoven, Sep 18, 2021.

  1. beethoven

    beethoven Registered Member

    Joined:
    Dec 27, 2004
    Posts:
    1,414
    I cleared the cache in my browsers yesterday and as of this morning I am unable to access a website. The issue has the following error: This server could not prove that it is www.XXX.com.au; its security certificate is from abx.xxx.com.au. This may be caused by a misconfiguration or an attacker intercepting your connection.

    This is in principle correct. The website is www.xxx.com.au and has a proper certificate installed. This shows up on other pc accessing the same website. The error is only on my pc and abx.xxx.com.au is the mail server which is not covered by the website certificate. Somehow on my pc the linkage is corrupted and wonder how I can reset this?

    Just to be clear, nothing was changed on the website I wish to access with respect to the certificate which is valid.
     
  2. ronjor

    ronjor Global Moderator

    Joined:
    Jul 21, 2003
    Posts:
    178,210
    Location:
    Texas
  3. beethoven

    beethoven Registered Member

    Joined:
    Dec 27, 2004
    Posts:
    1,414
    Hi Ronjor - thanks for that. Had forgotten about this and tried this immediately. Unfortunately no effect - all my browsers are still telling me that the certificate they check against is not valid. I am using Eset AV and noticed that they use their own filter but irrespective of that, if I deactivate that and "go direct" the mismatch is still thrown up.
     
  4. stapp

    stapp Global Moderator

    Joined:
    Jan 12, 2006
    Posts:
    27,442
    Location:
    UK
    Your link is to an HTTP site which is considered to be insecure.
    A lot of browsers will only go to HTTPS sites now.
     
  5. beethoven

    beethoven Registered Member

    Joined:
    Dec 27, 2004
    Posts:
    1,414
    Stapp - yes that is correct in principle. I did not provide full links but the connection is the same https in both cases - that was not the issue. Anyway, I used an image to roll back 24 hours and can connect as usual before. Whatever I changed yesterday without intention, has now been fixed back to the original setting. I am still curious to understand how clearing the cache in browser could have caused this, but I needed to work on this and could not wait any longer.
     
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.