Do more on the web, with a fast and secure browser!

Download Opera browser with:

  • built-in ad blocker
  • battery saver
  • free VPN
Download Opera

How to access NOAA sites with Opera 10?

  • I need to access the following two sites with Opera 10

    I want to know HOW to make it happen, not that it cannot be done.

    Opera 10.10
    Build 1893
    Opera/9.80 (Windows NT 6.1; U; en) Presto/2.2.15 Version/10.10

  • Have you tried accessing the https version of both sites ( and )? You may also want to make sure JavaScript is enabled.

  • You tried to access the address, which is currently unavailable. Please make sure that the Web address (URL) is correctly spelled and punctuated, then try reloading the page.

    Secure connection: fatal error (40) from server.

    Failed to connect to server. The reason may be that the encryption methods supported by the server are not enabled in the security preferences.

    Please note that some encryption methods are no longer supported, and that access will not be possible until the Web site has been upgraded to use strong encryption.

  • In "Alt + P -> Advanced -> Security -> Security Protocols" in Opera, is TLS 1.1 and 1.2 enabled? If not, enable them. If they're enabled, try disabling 1.2 to see if it makes a difference.

    There were some TLS fixes in the last couple builds of Opera 12 (like 12.18) I think that may be required for the site to work. Don't remember though.

    Chrome says the following for the site:

    The connection to this site is encrypted and authenticated using TLS 1.2 (a strong protocol), ECDHE_RSA with P-256 (a strong key exchange), and AES_128_GCM (a strong cipher).

    Opera 10 would have to be able to handle that probably.

  • Is opera:config#SecurityPrefs|OCSPValidateCertificates available in Opera 10? If so, try disabling it.

  • Olde Opera 12.18 (with all four of its security protocols enabled) is able to access both sites using the https site address prefixes, but the connections are listed by the browser as insecure: "The connection is not secure. The server attempted to apply security measures but failed". However, in attempting to access them via the http address prefixes you listed, the nhc site fails by opening a nearly blank CloudFront "301 Moved Permanently" error page (both with and without the browser's redirect function enabled); the http spc site at first appears to "open", but is somehow actually being auto-redirected to the https address, even with the browser's redirect function disabled... and, again, the resulting https connection is listed by the browser as insecure. With a modern browser, both sites auto-redirect properly, establish https connections, and the sites appear correctly.

    From what I'm seeing, I believe that both websites are applying forms of server redirection (though apparently in different ways for each) to try to force incoming http requests over to https site versions. However, those https servers seem to be requiring encryption protocols not available on 12.18-vintage browsers. Such a situation can only be worse for a browser as old as Opera 10.

  • None of that seems to work. Tried 1.2 enabled and not. Tried "OCSP Validate Certificates" checked and unchecked. Nada.

    Didn't try restarting after each change though if that matters.

    I didn't like the new Opera. I prefer this version. It was the last of the real Opera before the assimilation.

    There is no reason for 'security' to view a weather site. It's stupid. Seems like I read that this is all about the Evil Googler trying to force the entire web world to do things their way and I despise them.

  • @y0y0 said in How to access NOAA sites with Opera 10?:

    I prefer this version. It was the last of the real Opera before the assimilation.

    12.18 was the last presto-based Opera. You don't like it?

    Maybe you'll like this Opera 12 clone:

  • @y0y0 said in How to access NOAA sites with Opera 10?:

    ... There is no reason for 'security' to view a weather site. ...

    While I agree with you, the problem is that for whatever reason, there remains an apparent steady migration of the site universe to https and other technical protocols. In some cases, it's for consistency by site operators across their whole range of site offerings, some of which might actually need the https security or other kinds of protocols. Regardless, it is the way it is, and we users either have to maintain browser compatibility as this unfolds or face increasing numbers of sites that just won't work with an older browser, frustrating as all that might be.