Error-Untrusted server certificate on Touch; Mobicip will not open

  • expresslube
Posted: Wed, 02/25/2009 - 08:34

When loading Mobicip on my sons' touch, getting the message "Error untrusted server certificate; dismss" and can go no futher. 

Landscape mode disables Bookmarks ›

I am having the same problem

  • Guest
  • Thu, 02/04/2010 - 11:56
  • Copy comment link

Hello, I know the original post here is a bit old, but I didn't see the resolution posted.  I am having the same issue on my son's iTouch: Error: Untrusted Server Certificate, and can go no further.

I am not using any beta login info; I am logging in with my mobicip account info.

Re: I am having the same problem

  • mobicipc
  • 10/09/08
  • Fri, 02/05/2010 - 09:50
  • Copy comment link

Yes, there is a resolution to this problem. It is caused by an unknown issue in the iPhone OS actually. Turn off the power completely on the device. To turn off the power, press and hold the button at the top until you see a slider on the screen that asks you to confirm. Use the slider to power off. Keep it off for a minute or so, and turn in back on by pressing the button at the top.

This seems to solve this problem for most users. Let us know how this goes.

Mobicip Support

I think it is now fixed

  • Guest
  • Fri, 02/05/2010 - 19:37
  • Copy comment link

Thank you.  I followed your suggestion and the issue now appears to be fixed.  I will report back if it recurs.

Re: I think it is now fixed

  • mobicipc
  • 10/09/08
  • Sat, 02/06/2010 - 01:10
  • Copy comment link

Great! We are glad to hear that it worked for you as well.

Mobicip Support 

Hmmm, found the problem; it is fixed now...

  • Guest
  • Sat, 02/06/2010 - 13:00
  • Copy comment link
I just found out that the clock on my son's iTouch was set to January 2009.  Setting the date to the current date allowed the Mobicip browser to work again! Please accept my apologies for thinking it was the server or application causing the problem. My son's a fiddler (like his Dad), but I wonder if he may have been trying to get around the filtering somehow by trying to change the date.  I know he has a friend who thinks he can hack into anything and suggested this... I'm glad I found this issue, and I hope you will post this so others with this same issue may also benefit..

Oops I think I spoke too soon

  • Guest
  • Sat, 02/06/2010 - 11:49
  • Copy comment link
The problem is back again.  Your site shows that the iTouch was Last Reported: 23 Jan 10 04:57 PM.... I tried re-enabling the Safari broswer and I am able to surf the Internet with it.  When I go to mobicip.com, it does tell me that the mobicip.com server certificate has expired, however. So it is a problem with your site and/or the mobicip browser. What shoud I do next, reinstall the app?

Re: Oops I think I spoke too soon

  • mobicipc
  • 10/09/08
  • Mon, 02/08/2010 - 06:42
  • Copy comment link

Thanks for the confirmation. We copied your resolution as a response to this thread so that it is helpful for other users as well.

I just found out that the clock on my son's iTouch was set to January 2009.  Setting the date to the current date allowed the Mobicip browser to work again! 

Mobicip Support

why i cant login mobicip by using my username/password

  • allen_jiang
  • 11/14/08
  • Wed, 02/25/2009 - 19:31
  • Copy comment link

 how can i login successfully? still use the beta user name?

Need more info

  • mobicipc
  • 10/09/08
  • Wed, 02/25/2009 - 23:24
  • Copy comment link

Hello allen_jiang

You cannot use the beta username and password anymore. You will have to use the registered username and password you entered on this website.

We will need more information to troubleshoot the problem you are reporting. Are you having trouble logging into this website? Or is it only the app? What exact error message does it give you? Please feel free to contact us by email at support@mobicip.com or use the contact form.

Can you try again?

  • mobicipc
  • 10/09/08
  • Wed, 02/25/2009 - 18:18
  • Copy comment link

Hello expresslube

I am sorry that you are experiencing the problem. A temporary glitch on our server could have caused it. Can you try again now and confirm if the problem is occuring again?