Jump to content
We’re on Reddit now 🎉 🎉 💬 Come and join us there!! ×
Enpass Discussion Forum

Amandeep Kumar

Enpass team member
  • Posts

    566
  • Joined

  • Days Won

    35

Everything posted by Amandeep Kumar

  1. we’re glad to hear you’re enjoying Enpass Premium! It sounds like the change in networks and the time gap may have caused a desynchronization between your devices. Let’s try to get your Wi-Fi sync working again while ensuring no data is lost. 1. Identify the Most Up-to-Date Vault Open Enpass on each device (Linux PC, laptop, iPhone, and iPad). Check which device has the most current information by reviewing your most recent entries. 2. Backup All Vaults Before proceeding, create a manual backup of each device’s vault: Go to Settings > Vaults > [Vault Name] > Backup and save the file securely. 3. Reset Wi-Fi Sync On your Linux PC (or a device that will act as the host): Ensure all devices are on the same local Wi-Fi network. Go to Settings > Vaults > [Vault Name] > Set Up Sync > Wi-Fi Sync and choose Host a Server. On other devices (iPhone, iPad, laptop): Disconnect any existing sync: Settings > Vaults > [Vault Name] > Disconnect. Reconnect to the newly hosted Wi-Fi sync server. If the sync still fails or if you encounter conflicts, please let us know—we’ll guide you through advanced troubleshooting. We’re here to help if you need further assistance!
  2. @mandebooks I have just messaged you. Please do check your direct messages (DM) and share required details there.
  3. We're sorry to hear you're encountering sync issues with Nextcloud WebDAV. The error codes you mentioned (1308413 and 1304401) typically indicate connection interruptions or authentication challenges during the sync process. To help resolve the issue, please try the following steps: Clear Sync Cache: Disconnect the sync from Enpass. Log in to your Nextcloud account and manually delete the Enpass folder if it exists. Reconnect the sync from scratch and monitor the behavior. Ensure there are no VPNs, proxies, or network restrictions affecting the WebDAV connection. If the issue persists, please contact us at support@enpass.io with a demo account for your Nextcloud WebDAV server. This will allow us to raise the concern with our product team for further investigation.
  4. I had a discussion with our technical team, and unfortunately, Enpass does not currently have this feature. We appreciate your effort in bringing this concern to our attention. I am raising this issue with our technical team as a feature request, and we may consider adding it in our future updates. However, please understand that several factors and considerations have to be taken into account. #SI-4281
  5. Windows Hello should work on both instances. If it is not working on your machine, please provide more details, including: Enpass version on both accounts Windows OS version Kindly email us at support@enpass.io so we can investigate further.
  6. Please share the URL where Enpass autofill is not working so we can investigate further. Kindly note that Enpass autofill is currently not working with desktop applications.
  7. To resolve this issue, we need to check your purchase history. Please drop us an email at support@enpass.io with your registered email address. Looking forward to your email!
  8. For security reasons, we haven’t provided an option to view the password on the Enpass login screen. However, we understand your concern and will pass this request to our product team for further review. #SI-1905
  9. Thanks for reporting this issue and for being part of the beta channel! We've addressed this in the stable release, so updating to the latest version should prevent this from happening again. If you’re still experiencing the issue after updating, please let us know—we’d be happy to investigate further.
  10. Our team is actively working on a workaround to ensure you can authenticate your application even with Zscaler installed. We appreciate your patience and will update you as soon as we have more information. #SI-3465
  11. Here’s a quick rundown addressing your points: macOS Sequoia Compatibility: Enpass 6.11.8 is fully compatible with macOS Sequoia as an application. However, for autofill functionality in browsers, Enpass relies on our secure browser extension. Since Apple's built-in Password Manager is integrated into macOS and Safari, it might appear as the default option. On macOS, the Safari extension is bundled with the Enpass desktop app and is added to Safari automatically, but it isn’t enabled by default. To enable the Enpass extension on Safari, please follow these steps: Go to Safari Preferences > Extensions > Enpass. Click the checkbox next to Enpass Extension in the sidebar. Click the Turn On button in the pop-up that appears. Once the extension is installed, connect it to the Enpass desktop app to allow access to your saved accounts, passwords, and passkeys. Click on Always Allow On Every Website. Browser Extension and Security: We understand the security concerns regarding browser extensions. Our Enpass extension is built with stringent security measures and only accesses fields necessary for autofill after your explicit permission. If you're not comfortable using the extension, you can continue using Enpass as a secure vault and manually copy credentials when needed. Using Two Password Managers: While it might seem like you're managing two systems, Apple's Password Manager and Enpass serve different purposes. For a seamless autofill experience with Enpass, we recommend activating the browser extension. This way, you can enjoy the robust features of Enpass while keeping your credentials secure. I hope this helps clarify things. If you have any further questions or need more details about our extension’s security protocols, please let me know.
  12. Thank you for sharing the details info information. This will surely be helpful for our backend team in further investigation. Please allow us some time to get back to you with more findings or solutions. We appreciate your time & patience as we work on solving this issue!
  13. It seems there might be a conflict between Enpass's entry update process and LinkedIn's passkey creation workflow. To address this, please try the following steps: Manually Save the Passkey: Instead of letting Enpass update the existing entry automatically, disable autofill temporarily in the browser and manually create or update the LinkedIn entry in Enpass with the passkey details. Check for Field Mapping: Verify that all required fields (e.g., email, password, and OTP) in the LinkedIn item within Enpass are correctly mapped and saved in the correct format. Clear Browser Cache and Cookies: Sometimes, browser cache and cookies can interfere with website workflows. Clear them and try the process again. Update Enpass Extension: Ensure the Enpass extension in Firefox is up-to-date. If the issue persists, please share any error details or screenshots (if possible) so we can investigate further.
  14. Could you please try rearranging the fields in the Enpass application for the specific item? Ensure that the Password field is positioned at the top, right after the Email field, and the 2FA field is listed below it. Once you've made these adjustments, save the changes and test the autofill functionality again. If the issue persists, please let us know so we can further investigate.
  15. Could you confirm if Zscaler or any other network firewall is installed on your device? If it is, please note that this issue might be related to Zscaler's network policies. Currently, there is no workaround available for this specific scenario. However, our team is actively working on resolving it. We will update you as soon as a fix is available. Thank you for your understanding and patience.
  16. If you are using a recent macOS version and facing issues with saving usernames and passwords to Enpass, it could be due to the default password manager settings on your Browser. Additionally, please confirm that the Enpass extension is installed and enabled in your browser. For Safari, the Enpass extension is included by default. You can check if it’s enabled by going to Safari settings. If the issue persists, please don’t hesitate to contact us at support@enpass.io.
  17. Based on your description, it seems there might be an issue with the purchase or the license being transferred to another device. To investigate and resolve this matter promptly, please drop us an email from your registered email at support@enpass.io . Our support team will review the details and assist you further to ensure Enpass functions seamlessly on your father's device.
  18. To help resolve the issue with Enpass autofill on your Android 14 device, please follow these troubleshooting steps and let us know the outcome: Ensure All Autofill Methods Are Enabled: Enpass utilizes three approaches for autofill functionality. Please ensure that all of them are enabled. If they are already enabled, try toggling them off and back on: Android Autofill Framework Android Accessibility Enpass Keyboard You can find these settings within your phone's system and Enpass app settings. Recreate the Affected Item: If the issue occurs on a specific webpage or app: Note down the credentials for this webpage/app.(Please delete it immediately after use) Remove the saved item from Enpass. Save the item again in the Enpass app. Test autofill functionality to see if the issue persists. Reinstall Enpass App: Create a manual backup of your Enpass data or ensure synchronization is enabled for your vault. Uninstall and reinstall the Enpass app. Set it up from scratch and test the autofill feature again. If the issue remains unresolved, please let us know the specifics of your device model, the affected apps/webpages, and any error messages you encounter
  19. You will be pleased to know that FIDO2 support is already part of our development roadmap and will be implemented in future versions of Enpass. I’ve also shared your comment with our dedicated development team as additional feedback.
  20. Could you please share the version of Enpass that is currently installed on your Mac? If it’s not up to date, I recommend updating to the latest version to see if that resolves the issue you're experiencing.
  21. Please download and install Enpass from a valid source, such as the official Enpass website or a trusted app store. Once installed, try again and let us know if you're still encountering the same issue. If the issue persists, kindly provide the following details to help us investigate further: Enpass version Device OS and version We look forward to your response.
  22. Could you please clarify the issue you're facing and where you are encountering this error? Is it happening in the Enpass application, or are you experiencing it when trying to log in to the forum? Once we have more details, we'll be able to assist you more effectively.
  23. Could you please explain the feature you’re requesting in a bit more detail? Are you looking for an option to configure the sync server to use a specific IP address, such as a Tailscale IP, instead of the local IP for syncing your vaults over the internet? Any additional information you can provide would help us better understand your needs and how we can improve the feature.
  24. It seems the problem is related to the "Local Network Privacy" permission settings introduced in recent versions of macOS and iOS. To resolve this, please follow the steps below: For macOS: Open System Settings > Privacy & Security > Local Network. Locate Enpass in the list and enable access. Restart the Wi-Fi sync server and Enpass app. For iOS: Go to Settings > Privacy > Local Network. Find Enpass and toggle access to "On." Restart the Enpass app. Once done, try syncing again using Wi-Fi sync to verify if the issue is resolved. Regarding the issue of Enpass choosing the IP address of the machine instead of using a hostname, we understand how this could be a challenge, especially with changing IPs. We will forward this suggestion to our product team as a feature request for future updates.
  25. In Enpass, the items displayed under the "Credit Card" category in the menu bar pop-up include: Items categorized under "Credit Card" in the main app. Items using the "Finance.BankAccount" template, regardless of their assigned category. This is because the "Bank Account" template allows you to store credit card details, which makes these items relevant to the "Credit Card" list in the menu bar. We hope this clarifies the behavior you're observing. If you have further questions or need assistance, feel free to reach out.
×
×
  • Create New...