Unable to log in to owncloud hosted on private NAS

Bug #1523261 reported by Laryllan
24
This bug affects 5 people
Affects Status Importance Assigned to Milestone
Oxide
New
Undecided
Unassigned
webbrowser-app (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Hi there,

I'm trying to access my owncloud hosted on my private NAS.

WHAT I EXPECT:
I can accept the certificate and access my OwnCloud.

WHAT HAPPENS:
I cannot access my OwnCloud.
It shows the login prompt, but doesn't allow me to log in.
As if the login button doesn't work.

Revision history for this message
Laryllan (laryllan) wrote :
Revision history for this message
Olivier Tilloy (osomon) wrote :

This is unlikely to be because of the self-signed certificate. Self-signed certificates are correctly handled in webbrowser-app, when accessing a site using one of those you should see a warning screen, with two buttons: [back to safety] [proceed anyway]. If you choose to proceed anyway, the browser will let you browse the site, and will display a broken red lock in the address bar (as shown in your screenshot).

Can you please reproduce the issue and attach the log file for webbrowser-app. You will find it on your device at:

    /home/phablet/.cache/upstart/application-legacy-webbrowser-app-.log

Changed in webbrowser-app (Ubuntu):
status: New → Incomplete
summary: - Unable to access sites using a self-signed SSL certificate
+ Unable to log in to owncloud hosted on private NAS
Revision history for this message
Laryllan (laryllan) wrote :

I attached the log you requested.
Please note that the screenshot is taken from the browser-app in 15.10 as it shows the same behaviour as the phone app.

Thanks for your support.

Revision history for this message
Olivier Tilloy (osomon) wrote :

The following messages on the javascript console look suspicious:

(https://*******.spdns.de/owncloud/core/vendor/jquery-ui/ui/jquery-ui.custom.js?v=96c6637dd73906ebc167790a0e192a44:319) Uncaught ReferenceError: jQuery is not defined
(https://*******.spdns.de/owncloud/core/js/jquery.avatar.js?v=96c6637dd73906ebc167790a0e192a44:108) Uncaught ReferenceError: jQuery is not defined
(https://*******.spdns.de/owncloud/core/js/backgroundjobs.js?v=96c6637dd73906ebc167790a0e192a44:23) Uncaught ReferenceError: $ is not defined
(https://*******.spdns.de/owncloud/apps/files_sharing/js/external.js?v=96c6637dd73906ebc167790a0e192a44:20) Uncaught ReferenceError: OCA is not defined
(https://*******.spdns.de/owncloud/apps/files_videoviewer/js/viewer.js?v=96c6637dd73906ebc167790a0e192a44:100) Uncaught ReferenceError: $ is not defined
(https://*******.spdns.de/owncloud/core/js/lostpassword.js?v=96c6637dd73906ebc167790a0e192a44:2) Uncaught ReferenceError: OC is not defined

Could it be that your owncloud setup is incomplete, thus preventing you from logging in? Can you log in to it from another browser?

Revision history for this message
Laryllan (laryllan) wrote :

Hi Olivier,

I can log in normally using Firefox.
It even works when I use an unencrypted connection.

This is why I first tought of a certificate issue in the first place.
(Firefox is asking me to accept the certificate, webbrowser-app does not)

Revision history for this message
Olivier Tilloy (osomon) wrote :

This is weird. You’re saying webbrowser-app is not warning you about the self-signed certificate?

Do you get a warning when you browse to https://self-signed.badssl.com/ ?

Revision history for this message
Olivier Tilloy (osomon) wrote :

Thanks Laryllan for providing a test account/server, I’ve managed to reproduce the issue. When visiting the owncloud web interface, I am getting the self-signed certificate warning page as expected, and if I choose to proceed anyway, the page loads, but a lot of its subresources are not loading correctly.

I’m seeing e.g.:

GET https://*******.spdns.de/owncloud/core/css/mobile.css?v=xxxxxxx net::ERR_INSECURE_RESPONSE
GET https://*******.spdns.de/owncloud/core/vendor/jquery-ui/themes/base/jquery-ui.css?v=xxxxxxx net::ERR_INSECURE_RESPONSE
GET https://*******.spdns.de/owncloud/index.php/core/js/oc.js?v=xxxxxxx net::ERR_INSECURE_RESPONSE

…among many other errors, which in turn trigger errors like:

  Uncaught ReferenceError: jQuery is not defined
  Uncaught ReferenceError: OC is not defined

It looks like accepting the self-signed certificate doesn’t make oxide trust it for loading subresources. Need to investigate whether it’s a bug in oxide, or in the way webbrowser-app uses it.

Changed in webbrowser-app (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Olivier Tilloy (osomon) wrote :

Ha, this is in fact a known bug in oxide: bug #1503035. I’m going to mark this one a duplicate, and will bump the importance of the other one.

Revision history for this message
Laryllan (laryllan) wrote :

Thank you Olivier.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.