Bug: after remove acc,new acc can't connect to server

[owncloud]

Bug: after remove acc,new acc can't connect to server

[davivel]

Could you give us a test account in your server, and the current URL? Thanks

[AndryXY]

Yes but only via eMail ;) But I think it's not the server, as I sad every other webdav-tool works absolutely fine. I can reinstall ownCloud to test if it's working then. Because if there is a problem on my server you can't look for it, so it will not help I think or what do you think?
The problem starts after clicking in Android-ownCloud-App remove account.

[davivel]

Sorry, but I can't provide a public email address for support.

Try this URL in a web browser, and tell us if user and password are required:

http(s)://[your.owncloud.url]/[your.subdir]/status.php

Currently, that URL should not be protected.

[AndryXY]

No there isn't any status.php ...
Because I already posted my ownCloud URL in an other place, here it is: http://cloud.*********.de/data/*****/status.php

Maybe it's the same problem like here owncloud/core#723 (comment) ? (I can't share folders to external users)

[MTRichards]

feel free to use [email protected] if you would like an email for assistance.

[davivel]

Mmm, sorry @AndryXY , I'm not sure what's the state of your problem now. Did you change the URL to workaround the problem causing this is issue?

Anyway, the URL to input in the login view to access that server should be http://************* ; just that.

[AndryXY]

Sry, I misunderstood http(s)://[your.owncloud.url]/[your.subdir]/status.php ... I am not using any subdir (I thought you mean the profile-dirs with "your.subdir") ... http://cloud.*******.de/status.php works but how does this help finding the problem of "why Android Jelly Beans can't find the server"?

[davivel]

That URL is checked before allowing the connection to retrieve information about the server. When we try to create a new account in the Android app using 'http://***************', the check is passed, so the problem is not there.

Let me see if I understood : your changed the server-address, removed the account in settings, the created a new account with the new URL, and you can't access your account; is that?

[itstueben]

I had the same Problem. My solution was to go to "Settings"->"Apps"->"Owncloud" on my Phone and clear Data and Chache Data. Then force stopping owncloud app. After that the owncloud works fine with my owncloud 4.5.4 installation.
I have a Sony Xperia S with CM10 (Jelly Bean).
I hope I could help you.

PS: Sorry for my bad English ;)

[AndryXY]

@davivel Yes, that's it. I changed the Server URL from
http://www.********.de/cloud/remote.php/webdav/
to
http://cloud.*********.de/remote.php/webdav/

Now both addresses do not work in the reinstalled ownCloud app... I get an error by typing this URLs (unknown error) Before deleting the acc the first URL worked fine (I changed nothing in ownClod on my Server)
Every other webDav client/app has no problems. As you see when clicking on URL you get a login site.

@itstueben thanks, I already do that. Unfortunately that does not help :(

[davivel]

Probably you already knew this, but the right URL to input in the ownCloud Android app does not include the "remote.php/webdav/" suffix. So, for your previous configuration it would be http://****_, and now it should be http://_* .

Do you get the error before or after clicking the "Connect" button?

If you could provide us a temporal test account in your server to [email protected] we could help better. Please, include the words 'Android' and 'issue #44' in the subject.

Could you explain how did you exactly changed the server to get the new URL?

[AndryXY]

Oh no, that's really embarrassing now... I am so sorry wasting your time... I used the wrong URL... I was sure the whole time that the app uses webDav (and you already wrote that it not... oh dear, my english is realy bad...)
Sorry, everything works fine...

PS: Could you mask the domain to my server in your posts please?

EDIT: @davivel Thank you and sorry again...

[davivel]

Don't worry, this is not the first time somebody has problems with the suffix in the URL. We are aware of it and it's in our backlog.

Domain masked.