We are upgrading our Mozy Community! The new community will have new features, a much improved user interface and will work on your mobile devices. You will be able to access the community during the upgrade but you won’t be able to post until we’ve migrated every user to our new platform. Please see this link for further support options that are always available to you.

We apologize for the inconvenience this may cause.

/t5/Mozy-App-for-Mobile/iphone-ipad-app-issue-The-server-did-not-respond/m-p/31817

ForumTopicPage

Click to close the image preview

Showing results for 
Search instead for 
Do you mean 
Labels
Announcements
Latest from the Blog: Restoring files from an earlier date
One of the handiest features of Mozy is being able to restore from an earlier date in your backup history. Learn more in today's blog!
djdaedalus
Assassin
(4)
Solved (Go to Solution)

iphone/ipad app issue - The server did not respond

When i attempt to access multiple directories via the iphone/ipad app it fails with the follow error:

 

The server did not respond. Please try again.

 

i've seen another message pertaining to this but the issue appears server side.

 

has a fix been devised?

 

0 Reps

Re: iphone/ipad app issue - The server did not respond

I am having the same issue - I have a personal account where there is not a problem.  The issue only comes up with our business account where we have  roughly 25 gb of documents/pdfs organized in multiple layers of folders and subfolders.  The issue only arises when using the Iphone to explore the backed-up folders/files.

0 Reps
djdaedalus
Assassin
(4)
Solution

Re: iphone/ipad app issue - The server did not respond

look at this link -

 

http://community.mozy.com/t5/Mozy-app-for-iOS-iPhone-iPad/app-doesn-t-like-quot-amp-quot-in-folder-n...

 

i had & in my folder names... removing them fixed the problem for me.

Highlighted
Mobilator3
Elite Level 1
(5)

Re: iphone/ipad app issue - The server did not respond

We had the ampersand issue (fixed in 1.2) and also a server deployment issue (also fixed) around this. So hopefully this is no longer an issue.

 

0 Reps