Jump to content

plinss

Members
  • Content count

    6
  • Joined

  • Last visited

Community Reputation

1 Neutral

About plinss

  • Rank
    Newbie
  1. plinss

    Sync failed with Nextcloud 13

    This appears to be resolved by an update to V1.0.4 of Nextcloud's end-to-end encryption module.
  2. plinss

    Sync failed with Nextcloud 13

    Hi Akash, further testing shows that the problem appears to be related to the new end-to-end encryption module. When I disable end-to-end encryption the sync starts working again, re-enabling the module causes sync to start failing with the error "Error getting file. Please try after sometime (Error code: -119)" on iOS and "There went something wrong while synchronizing. (Error code: -116)" on macOS desktop. Note that I haven't actually enabled end-to-end encryption on any folders, just turning the end-to-end module on causes the problem. At this point I have end-to-end turned off on my instance, but I can turn it on and create a test account if you need one, but please give me a time window when you'd be able to take a look so I don't have to keep it on (and break my syncing) for too long.
  3. plinss

    Sync failed with Nextcloud 13

    Running Enpass v5.6.3 (139) on macOS desktop and v5.5.6 on iOS. I have been successfully syncing to a Nextcloud instance for quite some time. I just upgraded the Nextcloud instance to V13 (from V12) and Enpass sync no longer works. No useful error messages and nothing relevant in the Nextcloud logs, the Nginx access log lists: "PROPFIND /remote.php/webdav/ HTTP/1.1" 207 5488 "PROPFIND /remote.php/webdav/Enpass/ HTTP/1.1" 207 848 and nothing else related to Enpass. All other Nextcloud functions, including WebDAV file sync with the Nextcloud client are working normally.
  4. Rearranging the username and email fields does help for the initial login, but then I run into the same problem with the two-factor prompt. Tried moving the TOTP field first and changing its name, but nothing seemed to work
  5. When logging in to a Mastodon instance (example https://mastodon.cloud/ ) the autofill always puts the 'username' into the 'email' field (also replacing existing content, which is annoying). My Enpass entry has both 'username' and 'email' entries and the form element has the following html: <input aria-label="E-mail address" class="string email required" autofocus="autofocus" placeholder="E-mail address" type="email" value="" name="user[email]" id="user_email" /> I'm guessing the either name "user" or the id "user_email" is keying it to the username field. Perhaps the type attribute can be used as a filter (or better trigger?) It would also be useful if the autofill didn't replace existing contents (maybe a per-item preference?) (Firefox extension OSX v 5.5.2 (82))
  6. plinss

    Enpass grills my MacBook at/after Standby :( :(

    Same problem, Enpass 5.3.1 (60) on a MacBook Pro (macOS Sierra 10.12.1) syncing to ownCloud 9.1.1. I'm willing to make a test account on my ownCloud server if you need one.
×