GNOME Bugzilla – Bug 719653
Support ownCloud instances running on non-standard HTTP ports
Last modified: 2015-09-17 14:47:03 UTC
Created attachment 263243 [details] Screenshot As ownCloud 6 final is just around the corner I upgraded my installation to the RC1 release. I can access the WebDAV share just fine when adding it manually, but it does not work when using the owncloud files support in gnome-online-accounts. The share shows up in Nautilus but when clicking on it I get "HTTP Error: Cannot connect to destination" (see screenshot).
Btw, as can be seen on the screenshot, docs support is also active, however the Documents app shows "Now Documents Found". There should be various text and ODT files.
(In reply to comment #1) > Btw, as can be seen on the screenshot, docs support is also active, however the > Documents app shows "Now Documents Found". There should be various text and ODT > files. What version of gvfs and gnome-online-miners do you have?
(In reply to comment #2) > What version of gvfs and gnome-online-miners do you have? Sorry I should have added this information: gvfs-1.18.3-1.fc20.x86_64 gnome-online-miners-3.10.0-1.fc20.x86_64
You need to update gnome-online-miners to 3.10.2 because of bug 715026 I will look into your original problem once I get access to a ownCloud 6 instance. Can you create a test account for me?
>> You need to update gnome-online-miners to 3.10.2 because of bug 715026 I was not even aware of this package :) But I will get the newer build from koji >> Can you create a test account for me? Sure. Check mail.
I tested GNOME versions 3.8, 3.10 and 3.12 against the 6.0.3 instance running at cloud.gnome.org. Both gnome-documents and nautilus worked as expected for me. Are you still having this problem?
Thanks for the test account, Michael. The problem here is the inabilty to specify a non-standard HTTP port.
(In reply to comment #8) > The problem here is the inabilty to > specify a non-standard HTTP port. Really? At least the contacts sync seems to be working using the non-standard port.
(In reply to comment #9) > (In reply to comment #8) > > The problem here is the inabilty to > > specify a non-standard HTTP port. > > Really? At least the contacts sync seems to be working using the non-standard > port. I am assuming that you got contacts working by adding the account directly in Evolution or some other application, because the GOA UI for adding an ownCloud account does not let you specify a non-standard port.
(In reply to comment #10) > I am assuming that you got contacts working by adding the account directly in > Evolution or some other application, because the GOA UI for adding an ownCloud > account does not let you specify a non-standard port. I used the "host:port" notation in GOA, which, at least for contacts, seemed to work.
I tried this with another ownCloud instance running on a non-standard port (ie. neither 80 nor 443). I could see the files in nautilus and the documents in gnome-documents. The CalDAV and CardDAV URLs got correctly advertised on D-Bus. I don't know if there is something specific about Michael's instance, though, and I can't check because the test account he gave me doesn't exist anymore.
I tried with GNOME 3.14 on Fedora 21.
Also works with GNOME 3.10 on Fedora 20. So, non-standard ports can obviously be specified using the "host:port" notation. I am not sure what made me write comment 8
*** Bug 731662 has been marked as a duplicate of this bug. ***
Obviously there is something wrong here, but I could configure ownCloud instances running on non-standard port and with self-signed SSL certificates. Without having access to a set-up that triggers this issue, it is hard to say what is going on. Closing as INCOMPLETE. We can open this when we have access to a sample set-up.
I am not sure what I was doing here. :/ I wish I had a more permanent test instance running on a non-standard port so that I could test things like these. Anyway, bug 752736 showed a valid bug in the URI exposed as the GoaFiles:Uri DBus property. (In reply to Debarshi Ray from comment #12) > I tried this with another ownCloud instance running on a non-standard port > (ie. neither 80 nor 443). I could see the files in nautilus and the > documents in gnome-documents. The CalDAV and CardDAV URLs got correctly > advertised on D-Bus. I can only assume that the server running the test instance that I used for testing also had ports 80 and 443 open. Nmap confirms this, but although the machine and instance are still there, I don't have an account anymore. So, who knows? *** This bug has been marked as a duplicate of bug 752736 ***