certificate for this server is invalid

Question

My app is live. It was working fine. But somedays before we changed the certificates(for security purpose) on Server. And Now whenever I tried to run my app. It is giving error:

The certificate for this server is invalid. You might be connecting to a server that is pretending to be "DOMAIN NAME" which could put your confidential information at risk.

I am using Swift3. I want to know Is this front-end issue or server-end? How can I resolve this?

Note: I have searched a lot about the issue, but didn't get the solution. I also tried Titanium - "The certificate for this server is invalid. You might be connecting to a server that is pretending to be DOMAIN.COM” but I was already follow all the steps.

Other thing is web-app and Android-app is working Ok. But iOS app giving error.

Solution 1

Solved same issue with just setting devices' date & time to automatic.

Solution 2

You can check to see if this is a server-side problem by testing the TLS endpoint using SSL Labs (assuming this is an HTTPS connection). If the results come back invalid, the site will tell you why. If you're using a self-signed certificate, that would certainly cause this error.

If the results come back as valid from SSL Labs, then it's probably on the client side. Some client software doesn't have built-in trusted root certificates, but I doubt that Swift doesn't use the default OS root certificate store.

Solution 3

Remove https://www from ServerTrustPolicy and put just url

Solution 4

Please also check your firewall restrictions. In my case, this error occurred due to my firewall blocked the required URL. it's worked fine after removing firewall restrictions

View more solutions

Comments

[Amanpreet]

Thanks for information. I tried that and I can see there is column that shows RC4:Yes INSECURE (more info). Do you know How can we make it secure?

[Scovetta]

RC4 is a cipher enabled on the server. What kind of web-server are you using?

[Amanpreet]

I am using Apache.

[Scovetta]

Here's a link on configuring Apache with strong cipher suites. To get rid of RC4, you can either use the suggested SSLCipherSuite (from the link) or add :!RC4: to the existing SSLCipherSuite configuration directive.

[Amanpreet]

Ok.. I will check that. Is we usually face that kind of issues from certificates, Do you have any idea?

[uday augustin]

It perfectly worked for me. Thank you, Tushar. What is the underlying problem? How it is related to Date and Time?