the iOS app is attempting to connect, assuming that OC is running in the root, regardless of what the server URL is set to. It also corrupts the URL when connecting; see the extra "/p/webdav" in the webdav URLs above. This does not happen if owncloud is running in the root.
I have the same problem. See separate issue.
From my point of view, its a problem from the iPhone App Owncloud Version 3.5.1 and not from the owncloud-server settings, because i dont receive the error message by using iPad or Safari by desktop.
The error occurred in another account. We just tested it here and it only occurred in the other account. We compared both accounts and I noticed as a difference, that one account had a capital first letter firstname and lastname. So we changed that in the test account and the error was reproducible there. We wanted to make sure it was really the cause, so we changed back to the older full name and the error was gone. Sadly after changing again to capital letter firstname/lastname the error did not occurr again.
So I wanted to let you login into the account where the error occurs, so we moved all files from that account and changed the password, so we can let you access it, but after that the error was gone. And of course whatever we do, now the error does not occur again.
So the problem seems to be not reproducible with my server anymore and I have no clue, what could possibly cause it.
I dont know, if oi undestand you right. I cant change existing usernames!?? But its right, all accounts have a capital first letter firstname and lastname. by using a new Test user with Username "tester", i still receive the problem!
From my point of view, we do not have a problem with usernames, because everybody are able to login. The error came by choosing / open a folder. Another point is, that the app runs perfect by using iphone 5 with <v10 and with iPad or other devices.
Perhaps the following point will help you to fin the problem:
it seems that users with iPhone >v10 are able to login but the folder structure are old! the structure will not refresh. by choosing a folder or by manualy refresh the folder view the error is coming.
@denisblum I did not change the username, but on the webinterface at least the Adminstrator has the option to specify real names of the user. Changing that real name on the server did shortly cause that error, but not reproducible.
Also deleting all files of the affected user on the server using the webinterface, did remove the error for that user.
@jesmrec I have forwarded that question to my frined. I myself don't have an apple device and the error occurred on the device of my friend. He has installed the app from the appstore and says that he did not install any updates, but I did update the version of owncloud on the server.
@daviel The error ist not reproducible anymore for me, but the error should be in this part of the archived logs: http://pastebin.com/LVrdXj7N (access.log and error.log)
The important webserver settings are:
Alias /owncloud "/var/www/owncloud/"
@nasli I think the information from my friend was wrong, sorry for that. I just searched through my messenger archive and can reconstruct the following chain of events:
He reported the app isn't working anymore (i presume after installing an update of the app)
I tried to figure out, what was wrong and found out I did not have the latest version of owncloud installed, because owncloud moved to another repository and I had it installed from the old one
I assumed the error in the app was caused by an incompatibility between newest app and old owncloud-server-software
Please notice the suspicious "ebdav/" in the URLs, It feels like a string manipulation gone wrong; Finally: My ownCloud is installed in a /cloud path prefix. Which has exactly the same amount of characters (6) as ebdav/. The OP has duplicated "p/webdav/" prefixes in his URLs. Suspicious enough for me. --Thanks!
@kuking, what URL did you enter in your account? Did you include the /cloud path in it?
Is it feasible for you to delete the account in the device and create it again? If your server is redirected in some way, there is a chance that the URL was wrongly stored in a previous version and that the error persists even after upgrading to 3.5.3.