Bitcoin Forum
November 20, 2017, 05:35:11 PM *
News: Latest stable version of Bitcoin Core: 0.15.1  [Torrent].
 
   Home   Help Search Donate Login Register  
Pages: [1]
  Print  
Author Topic: Coinbase SSL error  (Read 857 times)
mmortal03
Legendary
*
Offline Offline

Activity: 1606


View Profile
May 02, 2014, 12:49:00 PM
 #1

When I go to Coinbase right now, I'm getting an SSL error, both in Chrome and in IE.  The Chrome error is the following:

Quote
Cannot connect to the real coinbase.com

Something is currently interfering with your secure connection to coinbase.com.

Try to reload this page in a few minutes or after switching to a new network. If you have recently connected to a new Wi-Fi network, finish logging in before reloading.

If you were to visit coinbase.com right now, you might share private information with an attacker. To protect your privacy, Chrome will not load the page until it can establish a secure connection to the real coinbase.com.

and

Quote
coinbase.com normally uses encryption (SSL) to protect your information. When Chrome tried to connect to coinbase.com this time, coinbase.com returned unusual and incorrect credentials. Either an attacker is trying to pretend to be coinbase.com, or a Wi-Fi sign-in screen has interrupted the connection. Your information is still secure because Chrome stopped the connection before any data was exchanged.

Network errors and attacks are usually temporary, so this page will probably work later. You can also try switching to another network.


Technical details

coinbase.com has asked Chrome to block any certificates with errors, but the certificate that Chrome received during this connection attempt has an error.
Error type: HSTS failure
Subject: ssl2000.cloudflare.com
Issuer: GlobalSign Organization Validation CA - G2
Public key hashes: sha1/CkQHDZZBx534FurkPPOxAec+llg= sha256/9sNPN+MqPO4Sk6kmD+TrLAwXS+7NqSfy9rBv3nBmpIs= sha1/eMdNeRjaGNOIt6gkHHXLb1A363o= sha256/OqqTlivI4taTCDJE1oq61tAsdnSQ/13Ibp0QKE1H7tc= sha1/h9vUX7CSjU4d+BVn5/Krr9YrZ3U= sha256/K87oWBWM9UZfyddvDfoxL+8lpNyoUB2ptGtn0fv6G2Q=

Is anyone else getting this? Hopefully it's just a misconfiguration of their certificates that needs fixing this morning and not a hack or attack on them.
1511199311
Hero Member
*
Offline Offline

Posts: 1511199311

View Profile Personal Message (Offline)

Ignore
1511199311
Reply with quote  #2

1511199311
Report to moderator
Join ICO Now Coinlancer is Disrupting the Freelance marketplace!
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1511199311
Hero Member
*
Offline Offline

Posts: 1511199311

View Profile Personal Message (Offline)

Ignore
1511199311
Reply with quote  #2

1511199311
Report to moderator
1511199311
Hero Member
*
Offline Offline

Posts: 1511199311

View Profile Personal Message (Offline)

Ignore
1511199311
Reply with quote  #2

1511199311
Report to moderator
NLNico
Legendary
*
hacker
Offline Offline

Activity: 1512


DiceSites.com owner


View Profile WWW
May 02, 2014, 01:00:33 PM
 #2

No, I don't get that. So could be either of these situations:

- you are on public wifi and someone is trying to show you the wrong site to get your credentials

- someone is trying to DNS hijack coinbase, which could be why your ISP did change the DNS to the attacker but my ISP (or OpenDNS actually) didn't

Either way, obviously never add exemption Smiley

You could try to use OpenDNS see if that helps. Obviously delete DNS cache etc.


edit: there can definitely be more reasons too. Just 2 common ones in my experience.
edit2: there are some people reporting the same today, like: http://www.reddit.com/r/Bitcoin/comments/24j62a/coinbase_down/

mmortal03
Legendary
*
Offline Offline

Activity: 1606


View Profile
May 02, 2014, 01:08:41 PM
 #3

No, I don't get that. So could be either of these situations:

- you are on public wifi and someone is trying to show you the wrong site to get your credentials

- someone is trying to DNS hijack coinbase, which could be why your ISP did change the DNS to the attacker but my ISP (or OpenDNS actually) didn't

Either way, obviously never add exemption Smiley

You could try to use OpenDNS see if that helps. Obviously delete DNS cache etc.


edit: there can definitely be more reasons too. Just 2 common ones in my experience.
edit2: there are some people reporting the same today, like: http://www.reddit.com/r/Bitcoin/comments/24j62a/coinbase_down/

Thanks for the link from reddit. It actually seems to be working again for me. We'll see how long it stays that way. Smiley
Pages: [1]
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!