Skip to content
View in the app

A better way to browse. Learn more.

Enpass Discussion Forum

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Cannot sync with NextCloud (non-SSL)

Featured Replies

I'm running 5.3.0 on linux.  Installed an internal nextcloud (the fork of owncloud) server.  That server seems to work through its web interface.  Tried to sync enpass with that server.  Used the url: http://<my internal server>/nextcloud/remote.php/webdav/ with the right username and password.  It says it is "connecting" incessantly.  I noticed on a different thread reporting similar symptoms that appears to be an SSL problem.  But I am not using SSL.  How can I diagnose this?

I should add that I can use a webdav client to access the above-referenced URL successfully.

Adding to this post: I created a webdav server using apache2 (not nextcloud).  I could sync just fine.  Only doesn't work with nextcloud.

Edited by Steve Brandli
Add comment about webdav without nextcloud.

  • 3 weeks later...
On 9/19/2016 at 0:26 AM, Steve Brandli said:

 

I'm running 5.3.0 on linux.  Installed an internal nextcloud (the fork of owncloud) server.  That server seems to work through its web interface.  Tried to sync enpass with that server.  Used the url: http://<my internal server>/nextcloud/remote.php/webdav/

 

Hi, just a guess, but when you installed nextcloud, did you perhaps configure it using http://localhost/nextcloud, instead of http://<your-internal-server>/nextcloud? nextcloud (and also ownCloud) has a security feature where you can only access it from URLs that have been previously approved by the nextcloud administrator. So if you configured it using http://localhost/nextcloud, you need to surf to http://<your-internal-server>/nextcloud and enable that URL before nextcloud will accept connections to http://<your-internal-server>/nextcloud. Also you should really use https and not http to connect to that nextcloud, even if you only use a self-signed certificate, to not send your nextcloud credentials readable for everyone on your internal network.

Refer to this part of the nextcloud documentation for more info on trusted domains: https://docs.nextcloud.com/server/10/admin_manual/installation/installation_wizard.html#trusted-domains-label

Edited by niemalsnever
Added link to nextcloud documentation on trusted domains

  • 1 month later...

stupid question while we are at it, can enpass sync with self-signed HTTPS webdav on all clients?

Create an account or sign in to comment

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.