NetApp OnCommand System Manager 500 Connection Refused

By | January 23, 2015

I recently upgraded my NetApp OnCommand System Manager and upon trying to login I was presented with the error: “500 Connection Refused”.

500_Refused

This can occur if TLS is not enabled in DataONTAP.  In this particular scenario, the only SSL protocol available was SSLv3, which most browsers now have disabled by default, or if your SSL certificate on the filer has expired.

To enable TLS in DataONTAP, login to the filer via SSH and issue the following command:

options tls.enable on

If you have a high availability setup with multiple controllers, ensure that you issue the command on both nodes.

17 thoughts on “NetApp OnCommand System Manager 500 Connection Refused

  1. shabnam

    Thanks for the post. After running around all over google with suggestions, this one worked. And it wasn’t do this and do that, it told you WHY you do this or that….

    Reply
  2. Zeeshan Kamil

    I recently upgraded my NetApp OnCommand System Manager and upon trying to login I was presented with the error: “500 Connection Refused”.

    thanks this problems have been solved by this command in data on tap options tls.enable on

    Reply
  3. BEST

    I have checked the options tls it is on my controller but still having the same problem.
    Please what other fix do I apply ..please help out.

    Reply
    1. Cody Post author

      Did you check the certificate the filer is presenting? It will give the same error if it is expired.

      Reply
  4. PM

    This has been worked after enabling httpd.admin – options httpd.admin.enable on

    Reply
  5. Shane Taylor

    Thanks, it worked! I had to do it on both our controllers and regenerate a 2048 bit self signed certificate.

    Reply
  6. Grateful Admin

    Running both commands options “options tls.enable on” and “httpd.admin.enable on” (no quotes) in SSH (Putty) worked like a champ! Thanks guys!!!

    Reply
  7. Brian K

    I usually don’t have time to leave comments, but this one deserved it! Thank You!

    Reply
  8. Jimmychou

    Running both CMD “options tls.enable on” and “httpd.admin.enable on” it worked!
    Thanks!

    Reply
  9. Sid

    [* Shield plugin marked this comment as “0”. Reason: Human SPAM filter found “s http” in “comment_content” *]
    Its not working yet.
    I tried different options but with no luck. Below are my ssl and tls settings.

    ntap-7m> options ssl
    ssl.enable on
    ssl.v2.enable off
    ssl.v3.enable off

    ntap-7m> options tls
    tls.enable on

    ntap-7m> options httpd.admin.enable on

    Reply
    1. Cody Post author

      If you open your browser’s developer tools via F12, using the network inspector, it may give you some more insight into the issue you are having. It should tell you if it is trying to negotiate SSLv3, TLSv1, etc. That’s what I would look at next to get more details. Good Luck!

      Reply

Leave a Reply

Your email address will not be published. Required fields are marked *