Information Technology was making some upgrades to the BelleAire wireless network during October 2010 (over fall break). People who use the Firefox web browser may encounter security certificate errors as a result.


    If you see the following error:

    you are running an outdated version of Firefox. Please use another web browser (Safari if you are using a Mac, Internet Explorer is you are using a computer running Windows) and download the latest version of Firefox at http://www.firefox.com/. The current version of Firefox is compatible with the new Zimbra e-mail server we implemented in June 2010.


    If you see the following error:

    you are running Firefox 3. You will have to delete the old security certificate for the BelleAire wireless network to be able to access it again.

    1. Close the Firefox window with the Secure Connection Failed error.
    2. Go to the Firefox settings.
      • Mac: Go to the Firefox menu and select Preferences....
      • Windows: Go to the Tools menu and select Options....

    3. Click on Advanced.
    4. Click on Encryption.
    5. Click on View Certificates. The Certificate Manager window will open.
    6. Click on the Servers tab.
    7. Under Perfigo, Inc. click on the listing for 147.53.100.254 once to select it.

    8. Click the Delete... button.
    9. When Firefox asks if you are sure you want to delete the server exception, click OK.
    10. In the Certificate Manager window, click OK to close the window.
    11. Open a new Firefox window (go to the File menu and select New WIndow).
    12. You will see a new Secure Connection Failed error. Click on the link Or you can add an exception....
    13. Click the Add Exception... button that appears.
    14. Click on the Get Certificate button.
    15. Make sure that the Permanently store this exception box is checked.
    16. Click on the Confirm Security Exception button.
    17. Log into the Saint Mary's College BelleAire wireless network authentication page with your username and password. You should not encounter this problem again (or at least not until there's another security certificate change).

Last Modified October 20, 2010