If/when @burnout426 happens to come across this thread, he may be able to help since he seems to be something of an M2 troubleshooting expert.

@alsiavash1633 Opera's VPN functionality is specifically built into their own browser. For other browsers, you'll have to use one of the various 'independent' VPNs - either paid or free.

"Loading" in which way? Loading the browser itself or loading a particular website after the browser is already open? If a website, which one(s) as examples? What other browsers "just work fine"?

@borzyanich Perhaps it's a censorship-crackdown reaction to the antigovernment protests that occurred in Almaty and Astana (and elsewhere) on 27 February. It's not uncommon at such times in censorship states for the authorities to increase Internet blocking to interfere with further planning and conduct of protests and rallies. Kazakhstan censors already practice deep-packet inspection of Internet data flow, so such a crackdown would certainly be within their capabilities.

In some cases, anti-malware on one's own computer can interfere with the proxy nature of Opera's VPN.

However, if you live in a number of countries where there is national censorship, your ability to connect with a VPN may be interfered with or blocked by your ISP or the national Internet backbone to prevent circumvention of the censorship. This is particularly true for certain nations in the Middle East and the Orient, but can also occur in a few other nations where national politics or geopolitical tensions lead to attempting restriction of citizen access to web traffic to/from beyond the national borders. Some forum threads that relate to what may happen are:

https://forums.opera.com/post/163795
https://forums.opera.com/post/163140
https://forums.opera.com/post/162533

In some cases, your ISP (Internet Service Provider) may be blocking VPN usage (or its distinctive header protocols), either intentionally or accidentally. If there's no 'political' risks to the user, it may be useful to inquire about the problem with your ISP.

Sometimes, if censorship is involved, one can try using a stand-alone VPN service in hopes that it won't be blocked, though eventually that can happen with any VPN if the national authorities are persistent.

edited to add: If you live in Russia, you may be encountering something related to the subject of this article, which is expected to occur before 1 April 2019: https://www.bbc.com/news/technology-47198426

@pjbw127 Have you ever installed Spam Arrest on your system for filtering against eMail spam on any of your eMail accounts? From https://www.lifewire.com/spam-arrest-filtering-service-1166355: "Spam Arrest removes all mail from senders not yet approved before you download it or access it through Spam Arrest's 1 GB online web-based email service. ... Spam Arrest checks and cleans up to three POP or IMAP email accounts periodically. Works as a POP proxy service between your email client and your POP email account."

Given that Spam Arrest employs POP proxy techniques, it may somehow be getting entangled in the process of vetting https certificates - which is what your original Security Issue message seems to refer to. If you've never installed Spam Arrest and you're getting this on all visited websites, there's something else going on such as malware, etc.

@weirdo69 If you live in a number of countries where there is national censorship, your ability to connect with a VPN may be interfered with or blocked to prevent circumvention of the censorship (particularly certain nations in the Middle East and the Orient). Some forum threads that relate to what can happen are:

https://forums.opera.com/post/163795
https://forums.opera.com/post/163140
https://forums.opera.com/post/162533

There's clearly a communications problem going on here.

The first post made by @livingpharaoh was actually in a different Opera sub-forum (Opera for Computers): https://forums.opera.com/post/164596 . In that post, he specifically stated he'd just installed Opera 58, was looking for "Themes" options, and got entangled while searching in Opera's website by a referral to "Tools" for the Themes option. He then asked if that website description was out of date. @Leo responded "yes, it is". Unfortunately, that accurate moderator reply didn't address the OPs' underlying concern of where might Themes be found in Opera 58 (actually, such as it exists, under Settings > Wallpapers and/or Appearance). However, the reply did answer the OP's specific question.

The OP then posted here in the "Forums" sub-forum with a sarcastic-toned complaint towards Opera's support, regarding what he deemed the insufficiency of the reply to his original post in the Opera-for-computers forum. Subsequently (and unfortunately), it seems everyone thereafter has been essentially talking past each other here.

Several observations occur to me:

1. The Opera websites indeed can too easily lead a user (especially one new to chromium-based Opera) down some confusing rabbit holes related to Olde Opera terminology and documentation which don't apply to New Opera. This is not the first instance of this in user posts I've seen.
2. Sometimes the most relevant, underlying nature of a problem post gets missed by a reply. I too am guilty of this at times, occasionally because of misleading language/wording/interpretation and other times by a particular mindset I may bring to my first reading of the problem post.
3. Sometimes, after a single problem post that doesn't get a (to them) 'suitable' reply, posters lose patience (and their tempers) and generate a 'snarky' post. What results thereafter is often a flame war that pulls in other attackers/defenders and alienates all involved.

I believe what's needed is patience on the part of each of us, original posters and responders alike, along with a willingness to calmly ask for and respond with more information and/or clarity when requested.

I suggest you read through the following threads to gain insight into what may be happening:

https://forums.opera.com/post/163795
https://forums.opera.com/post/163140
https://forums.opera.com/post/162533

Since Dubai is part of the UAE, the threads probably have a bearing on your situation, particularly the second one (163140).

@yanta said in IP 185.26.182.103 - Opera.com: Security certificate problem?:

My question arises from this thread and from blackbird71's contribution there in particular:

@blackbird71 said in Opera sites can't be reached !!:

If you enter either of the following Opera IP numbers directly into your browser address bar, does Opera's website open? If not, what occurs?
185.26.182.103
185.26.182.104

If you enter http://opera.com into the address bar, does it behave differently, and if so, how?

Both of these techniques should cause your browser to be automatically redirected to Opera's https download site.
...

Since I'm just an ordinary user I don't know how to assess this situation.
...

As browsers evolve (including the underlying chromium engine for Opera), various kinds of security checks are increasingly made automatically in the browser. One of these, as @sgunhouse noted, is a comparison of the domain listed on a site's https certificate and the address entered into the browser's address box. If they don't match, different browsers may deal with that in different ways (or not at all).

When an IP that once used to take a user to an http site is entered directly into the address box and the browser is instead auto-redirected to an https website address, the cert that's then auto-issued by the site will carry the https URL, not the IP that was entered into the browser's address box. In mostly-http days, since there would be no cert, no 'mismatch' existed to be detected. With an auto-redirection to the https site, a cert is indeed issued and the browser suddenly has something with which to compare to the address box entry (the entered IP). It didn't used to show up this way that often, when there was far less auto-redirection and less universal employment of https site addresses... but "the times, they are a-changin'".

Nevertheless, for troubleshooting, when a site that's unable to be accessed by a user via its URL is being analyzed (as was the case in that other thread from which you're quoting), entering the IP directly (whether or not it's linked to an https cert address) should still ping the site without going through the usual DNS lookup process. Site access problems often occur either because of a problem in the DNS-lookup site that locates the listed IP for an entered URL, or from direct blocking of the website by an ISP or national censor. Entering the IP directly will still tell the user if the site can be successfully pinged by IP from the user's location (either by successfully connecting to an http site version or via the error messages noted in the case of an auto-redirection to an https site version that still confirms a site certificate was received from that IP). For either of those connection responses, the implication is that the entered IP has traced a successful Internet path to the target website domain server, so the cause of the original user URL-connection inability will thus typically lie with a problem in the DNS lookup service accessed by the user - either it's defective or being blocked/interfered..