Jump to content
Enpass Discussion Forum

WebDAV Sync Error Nextcloud


Alexxander
 Share

Recommended Posts

@Alexxander@oliwor@jero
It seems its an issue of the saved vault of a old version, so i found a quite easy workaround.
Make sure your local vault has all passwords, disable(disconnect) the sync, delete/rename the files from enpass from the nextcloud and configure the sync again.
Enpass will create a new file, after that i no more have the problem.

Its quite ugly that we have to do that, but it seems enpass dont tested the updates quite good.
 

Edited by False
Link to comment
Share on other sites

Hello,

I'm not sure if that belongs to the topic, but I'm currently migrating from Owncloud 10.5 to Nextcloud 19.0.2., and have the same problem with Enpass. The username and password are definitely correct, and I still get a 401.

However, I have found that if I bypass the HAProxy connected in front of it, the synchronization works immediately. The HAProxy is in http mode and has so far run with the Owncloud without any problems.

I'm still looking for the problem, but I'm afraid that it could be an interaction with the Nextcloud, since I'm now on the standard configuration of the HAProxy and really can't do much more.

Link to comment
Share on other sites

@insigma

On 9/8/2020 at 3:00 PM, insigma said:

The username and password are definitely correct, and I still get a 401.

Make sure that the URL you are using in Enpass is in the required format https://{host}/{path}/remote.php/dav/files/{username}  

You could PM me the demo account credentials if you still face an error with the above configuration. Also, let us know the Enpass version and the OS you are using.

Link to comment
Share on other sites

2 hours ago, Kashish said:

@insigma

Make sure that the URL you are using in Enpass is in the required format https://{host}/{path}/remote.php/dav/files/{username}  

You could PM me the demo account credentials if you still face an error with the above configuration. Also, let us know the Enpass version and the OS you are using.

Hi @Kashish

that wasn't the problem. The problem was a option called "trusted_proxies". After adding everything worked perfectly. Tested with Windows, Linux (Manjaro), OSX and IOS as well as IPadOS.

 

Edited by insigma
  • Thanks 1
Link to comment
Share on other sites

  • 2 months later...
On 9/10/2020 at 9:57 AM, insigma said:

Hi @Kashish

that wasn't the problem. The problem was a option called "trusted_proxies". After adding everything worked perfectly. Tested with Windows, Linux (Manjaro), OSX and IOS as well as IPadOS.

 

Hi.

Sorry to disturb, it seems I have a very similar problem after migrating my Owncloud server.

What do you mean by "an option called trusted-proxies" ? Is it an Apache option ? A Nextcloud option ? An Enpass option ? Where can I edit this please ? Thanks

Link to comment
Share on other sites

On 11/28/2020 at 5:10 PM, Byb said:

Hi.

Sorry to disturb, it seems I have a very similar problem after migrating my Owncloud server.

What do you mean by "an option called trusted-proxies" ? Is it an Apache option ? A Nextcloud option ? An Enpass option ? Where can I edit this please ? Thanks

This is a config option in Nextcloud (and newer version of Owncloud i think). Just add

Quote

'trusted_proxies' => '<YOUR PROXY IP>',

to the config.php of your Nextcloud config if you use a reverse proxy in front. This config.php should be in the config directory of your Nextcloud installation.

Link to comment
Share on other sites

On 11/30/2020 at 7:29 AM, insigma said:

This is a config option in Nextcloud (and newer version of Owncloud i think). Just add

to the config.php of your Nextcloud config if you use a reverse proxy in front. This config.php should be in the config directory of your Nextcloud installation.

Ok I see this, you're right.

But this option seems not to apply to my problem : I don't use any proxy right there ¬¬

This is a strange behaviour : the sync is working on the iOS app, on the Windows 10 app on one machine, but no longer on another Windows 10 app (error 908500).

I have at the moment no idea how to resolve it.

Thanks for replying, by the way.

Link to comment
Share on other sites

  • 2 weeks later...

took a while... but finally it works on my mac (work before on windows - but not win)

What i did in config.pho

 'trusted_domains' => 
  [
   'nextcloud.domain.info',
   '192.168.0.7:81'
  ],
  'trusted_proxies' => 
  [
   '192.168.0.8',
   '172.17.0.7'
  ],
  'ServerName' => 'nextcloud.domain.info',
  'overwritehost' => 'nextcloud.domain.info',
  'overwrite.cli.url' => 'https://nextcloud.domain.info',
  'overwriteprotocol' => 'https',

------

the 192.1680.7 is the internal docker host, the 172.17.0.7 the docker internal IP, the 192.168.0.8 is the reverse proxy

 

May this helps someone - for me it does :-)

Best

Thorsten

 

  • Thanks 1
Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...