Skip to main content

Although I am starting to like MeWe, I get annoyed with this error, and it often pops up, depending on what I do,...


Although I am starting to like MeWe, I get annoyed with this error, and it often pops up, depending on what I do, and if the Internet connection to the network service fails and I need to restart. (Please see that attached picture file below.)

Regardless of whether I use Google Chrome, or Firefox, the result is the same.
Interestingly, Windows Explorer seems to be able to go to the log-in screen at least.

Anyways, does anyone have any suggestions for improving this?

Sometimes, even Google+ fails like this, and my only recourse is usually to wait and then try again later.

#ConnectionNotPrivate #SocialMediaNetworks #lac

Comments

  1. Same here, i solved it by using Firefox and disabling the error message. You can read about it here: https://www.digicert.com/ssl-support/disabling-browser-support-ssl-v3.htm

    ReplyDelete
  2. Wait, are you implying that mewe is using ssl v3?

    ReplyDelete
  3. Not MeWe, but your (or the post author's) browser.

    ReplyDelete
  4. The error would suggest you are being presented with a certificate for some URL other than MeWe.com.

    It would be interesting to see what the certificate details are when that happens again, but sounds like something is trying to hijack your connection.

    ReplyDelete
  5. No, my browser doesn't support SSL v3, because of course it doesn't. SSL v3 is completely obsolete. I'm also not the person connecting to the site. The only way someone with a browser version made in the last five years would connect over SSL v3 is if the server was forcing it...

    ReplyDelete
  6. Interesting. I mostly use the Android app, sometimes Chromium on Linux, but have never seen that error.

    ReplyDelete
  7. Don't think this is a MeWe issue. Never seen this error or heard of others having such trouble.

    ReplyDelete
  8. Maybe you're getting served a misconfigured connection from MeWe's Content Delivery Network? The 'common name invalid' error does indeed seem to suggest you're getting a connection from a domain that doesn't match any of the domain names listed in the SSL certificate.

    ReplyDelete
  9. I’ve never seen this error (though I usually use the iOS app). I don’t think this is a MeWe problem.

    ReplyDelete
  10. Lowell Aaron Court Change your dns to something normal.. like opendns or googledns.. then fully reboot this machine and check if the issue happened again.

    BTW.. Chrome/Chromium does not use CN's anymore since (if I am not wrong) 2015. That same as most of the other modern browsers like FF, Safari etc.

    ReplyDelete
  11. Yeap.. I forgot about cloudflare. They are best choice :)

    ReplyDelete
  12. Mr. McNoname Excellent -- thanks very much the detailed way of approaching this problem.

    ReplyDelete
  13. Martina Neumayer I'm already using OpenDNS with CISCO RV130 VPN Router. However, thanks for the suggestions -- I hadn't heard about cloudflare before.

    ReplyDelete
  14. Filip H.F. Slagter Thanks very much for the medium blog link. I'll probably look into it's solution if the other suggestions don't work.

    ReplyDelete
  15. Thanks everyone else who have contributed. It's been a great learning and sharing experience here. You are all very generous with your comments.

    ReplyDelete
  16. Nathan Woodford Unfortunately, I'm using a computer, so this isn't an option. Thanks for suggesting this though.

    ReplyDelete

Post a Comment

New comments on this blog are moderated. If you do not have a Google identity, you are welcome to post anonymously. Your comments will appear here after they have been reviewed. Comments with vulgarity will be rejected.

”go"