Outdated SHA algorithm on chrome

General Discussion
  • #1

    I am getting a red and crossed out https when visiting NodeBB or the NodeBB Community. Here are some screenshots:

    NodeBB SSL Error Main Domain.png

    NodeBB SSL Error Main Domain Dropdown.png

    Google Chrome's explanation on why it is displaying this error is pretty spare - actually there is zero explanation. So I am not very sure if that is the real cause, but my guess is that this is due to the SHA1 signature of your certificate, I tried searching for a solution but there is none except requesting a new certificate at your CA.

    Some helping links:

    And the same links as comparison for (my) working domain:

  • #2

    Yup, seems like you should update nginx' cipher set a bit 😉

  • #3

    I don't think this is caused by NGINX' cipher suite as the SHA1 signature is kind of "embedded" in the certificate. But if it is possible to fix this in NGINX itself, here is my configuration for SSL, maybe compare it with your configuration.

    # SSL
    ssl_protocols             TLSv1 TLSv1.1 TLSv1.2;
    ssl_session_cache         shared:SSL:10m;
    ssl_session_timeout       10m;
    ssl_prefer_server_ciphers on;
    ssl_ciphers               'HIGH:!aNULL:!eNULL:!EXPORT:!DES:!MD5:!PSK:!RC4';
    ssl_buffer_size           1400;

    Oh and FYI: You'll drop support for all operations systems <Windows XP with:

    ssl_ciphers 'HIGH:!aNULL:!eNULL:!EXPORT:!DES:!MD5:!PSK:!RC4';

    If you don't want that you should use:


    Also, just out of interest: Is that occurring on your machine too @Moritz-Friedrich?

  • GNU/Linux

    Hey guys, I just noticed this as well.

    I recently updated our certs, but not sure if that's the reason, of whether it's just a new check from Chrome.

    either way, gh#3054

Suggested Topics

| | | |