title: Error: Name not maching for self signed SSL certificates on Android
body: <p>I am trying to access my web application protected by SSL from an Android 2.3.4 using the built-in browser.</p>
  
  <p>The server certificate is a self-signed certificate I created using <em>MAKECERT</em> and installed on the server.
  When I try to access the page, I get an error message from the browser stating <code>The name of the site does not match name on the certificate</code>. </p>
  
  <p>I have verified and the server address is exactly maching the Common Name of my certificate (it is actually just an IP address).</p>
  
  <p>The message does not pop up when I try to access, on the Android device, other websites secured with not  self signed certificates.</p>
  
  <p>If I access the same page using IE or Chrome on a desktop - apart for the signing authority message - I get no warnings and, once I have installed the certificate in the Trusted Root CA, the certificate is smoothly accepted by the browser.</p>
  
  <p>Should I take it that the message is actually a rejection of self signed certificate by Android?</p>
  
  <p>I am a bit puzzled at this. </p>
  
  <p>I tried to install  the certificate in the Credential Storage but that does not improve the situation. and now I have no clue what I might try next. </p>
  
  <p>Questions are: Is there any particular thing I should follow creating a self-signed certificate acceptable for Android? has anyone managed to get the self-signed certs accepted by Android without this warning?</p>
  
  <p>What else could I try?</p>
  
  <p><strong>-UPDATE-</strong>
  Bruno's reply steered me in the right direction, so I managed to do one step forward: I remade the certificate adding SAN (had to abandon <code>MAKECERT</code> for <strong><code>OpenSSL</code></strong>, following there <a href="http://andyarismendi.blogspot.in/2011/09/creating-certificates-with-sans-using.html" rel="nofollow noreferrer">instructions from Andy Arismendi</a>).</p>
  
  <p>Now the message has gone but I am blocked in the 'certification autority not trusted' issue already discussed <a href="https://stackoverflow.com/questions/4461360/how-to-install-trusted-ca-certificate-on-android-device">in this SO post</a>, so I am still working to find a final solution to my issue - not having any warning popping up on the Android browser. </p>