Amandeep Kumar

To investigate this issue further and assist you more effectively, please raise a support ticket by emailing us at support@enpass.io.
Kindly include the link to this forum post in your email so our team can quickly review the context and get back to you as soon as possible.

We look forward to helping you resolve this promptly.

To investigate this further, could you please install Enpass from the Mac App Store and check if you experience the same issue there?
This will help us identify whether the behavior is specific to the website version or system-related.

Let me know how it goes, happy to help further!

You can disable the “Autofill with Enpass” popup on specific apps or websites without turning it off completely.

To manage this, you can use the Inline Autofill Popup Menu blocklist inside the Enpass browser extension settings:

How to disable the autofill popup for specific sites

1. Right-click the Enpass extension icon in your browser’s toolbar.

2. Select Settings.

3. Use the Show Inline Autofill Popup Menu toggle to enable/disable the popup globally.

4. To hide the popup only on certain websites:

   • Scroll to Inline Autofill Popup Menu blocklist

   • Enter the website URL you want to block in the Add URL field

   • Click Add

   • (To remove a site later, click the ✖ next to the URL.)

Now the popup will be suppressed only for the websites you add to this blocklist.

I’ve noted your feedback and forwarded it to the development team as a feature request for native Wayland support and improved UI scaling. This will help us prioritize it appropriately.

In the meantime, if you experience any specific reproducible behaviors or crashes related to Enpass, feel free to share them.

@KOTB Thank you for following up.

We’ve reviewed the details of ticket ECS-59044, and I can confirm that this issue is already with our development team. They are actively working on a permanent fix. We did share a workaround earlier, but since it only helped temporarily in your case, the team is focusing on addressing the root cause.

We truly appreciate your patience, and we will update you as soon as we have further progress or a fixed build available.

I understand how inconvenient it is to log in multiple times a day, especially when you’ve already extended the auto-lock timers.

If Enpass is still locking even with System Inactive and Enpass Idle both set to 9999 minutes, it’s likely that a system-level trigger is forcing the lock. A few common causes where windows/macOS may lock secure storage when:

• The system goes to sleep

• The screen locks

• You switch between user accounts

• The device restarts

Any of these events will force Enpass to lock regardless of your in-app settings.

To help identify the exact cause, could you please share the following:

• Your OS (Windows/macOS/Linux)

• Enpass app version

• Whether you’re using the Enpass browser extension (Chrome/Firefox/Edge)

• When the lock typically happens (after sleep, after screen lock, or randomly)

Once I have this information, I can guide you more precisely on what’s triggering the lock and how to prevent it.

Thanks for the details.

This issue happens when Chrome doesn’t fully use the Autofill Framework for certain sites, which leads to the “contents can’t be autofilled” message. Since accessibility autofill is disabled, Enpass can’t fall back to it.

Please try enabling Accessibility Autofill, as this can help on sites where Chrome’s native framework isn’t working properly.

I’ve also noted this as a compatibility issue for our team to review. If you see this on more sites, feel free to share them.

We understand how inconvenient it can be when Enpass doesn’t automatically restart after Update while other apps do. I’ve noted this as a feature request and shared it with our product team for consideration in future updates.

If you have any additional suggestions, feel free to share.

#SI-4577

Since the issue is not currently reproducible on your side after recreating the items, it may have been a temporary data inconsistency or corruption within the affected items. However, if the problem occurs again, please do share steps or your observations you notice, it will greatly help us pinpoint the root cause.

We appreciate your cooperation and the time you’ve taken to assist with troubleshooting.
If you experience anything unusual again, feel free to update the thread and we’ll be ready to help.

Thanks again for your support.

Yes, Enpass can differentiate and autofill based on full URL matching, including the port number.

To make sure Enpass selects the correct login for each Docker instance, please add the complete URL (including the port) in the Website field of each item. For example:

• http://myserver:8001

• http://myserver:8002

When full URL matching is enabled, Enpass will autofill the correct item based on the exact URL + port.

You can find the detailed steps here:
https://support.enpass.io/app/extension/autofill_using_browser_extension.htm?rhhlterm=web&rhsearch=web%20form#autofill-web-forms

If you need any help adjusting your items or settings, feel free to reach out.

From your description, it seems the issue may be related to a corrupted attachment block within the affected items, which is why deleting and recreating the items on the working device resolved the problem. Since it has happened more than once, we absolutely want to investigate this further.

To help us diagnose the root cause, could you please share the following details:

• The platforms and app versions where this issue occurred (Windows Store version, website version, and their version numbers).

• The cloud service you are using for sync.

• A sample item (with test/dummy files, not real data) where you can reproduce the issue, if possible.

• A short screen recording of the error happening on the affected device.

In the meantime, a few suggestions to help avoid this issue on single-device setups:

• Ensure the vault is fully synced and up to date before attaching or saving files.

• Check that the attachment file path does not contain special characters or unsupported formats.

• Try temporarily disabling any antivirus or third-party security software that may interfere with file read/write operations.

• Make sure your local disk has full write permissions for the Enpass data directory.

Thank you again for reporting this. We truly appreciate users who help us improve Enpass, and we’re here to help you until the issue is fully resolved.

Thanks for sharing your experience. I’m sorry to hear the issue persisted to the point that you had to switch solutions. Reliability is a priority for us, and feedback like yours helps us identify where improvements are needed.

If you’re open to it, I’d be happy to document the details of what you encountered so we can review it internally and prevent similar cases in the future.

Thank you for the clarification and for sharing your experience with Syncthing.

We’ve forwarded your feedback to our product team for further evaluation. Your input is valuable, and it helps us explore improvements for future releases.

If there’s anything else you’d like us to pass along, feel free to let me know.

Yes, this limitation still exists. Due to certain platform-level restrictions and security obligations on Android, Enpass cannot perform real-time background syncing. 

Thanks for the follow-up! Could you please email us at support@enpass.io along with a short screen recording showing where the option to “Connect with a different cloud account” is missing on your iPad? That’ll help our technical team check what’s going wrong. (While recording, please make sure to hide any sensitive information such as passwords or personal data.)

Here’s what you can try in the meantime:

1. Open Enpass → Settings → Vaults.

2. Select your vault → tap Disconnect from the current cloud.

3. Then choose Set up Sync → iCloud (or another preferred service) — this is where you’ll see the option to sign in with a different cloud account.

Regarding your question, Box and NextCloud are also secure options, but since you already use iCloud, you can definitely continue with it once the sync setup is refreshed.

Thank you for the update and for sharing these details.

To help us better understand what’s happening, could you please send an email to support@enpass.io along with a short screen recording showing the issue occurring on your device? (While recording, please make sure to hide any sensitive information such as passwords or personal data). This will help our Technical Team analyze the behavior more accurately and identify the cause.

We appreciate your cooperation and look forward to resolving this for you soon.

I’ll quickly ask our Technical Team to investigate this behavior and share their findings with you. I’ll keep you updated on any developments, and if we require additional details, I’ll reach out via this ticket.

Enpass sincerely appreciates your support and patience regarding this issue.
#SI-4560

I discussed this with our technical team, and unfortunately, Enpass does not currently support disabling the password save prompt for specific apps. We appreciate you bringing this to our attention.

I’ve shared this as a feature request with our development team, and it may be considered for a future update. Please note that such changes depend on multiple technical and design considerations.
#SI-4558

Thanks for sharing this issue. Could you please mention a few websites where the autosubmit feature isn’t working? This will help us test it on our end.

Also, please check whether the “Autosubmit Login” option is enabled for those particular items in Enpass. You can find this by opening the item → and verifying if Autosubmit is turned on.

Let us know your findings so we can assist you further!

Enpass on Android supports autofill through the following three methods. For the best experience, please ensure all of them are enabled. If they’re already active, try toggling them off and back on:

• Using Autofill on Android

• Android Autofill Framework

• Android Accessibility

• Enpass Keyboard

Enpass works seamlessly with most major browsers that support Android’s Autofill Framework, including:

• Google Chrome

• Mozilla Firefox (Android version)

• Microsoft Edge

• Other mainstream Android browsers that support the standard autofill service

To clarify:

• Your first understanding is incorrect - you can create multiple vaults with the same Enpass account, but each cloud account can sync only one vault. The Primary vault can also be shared.

• Your second understanding is correct - for sharing, all users must use the same cloud account credentials and the vault password. Enpass does not support shared folders within a cloud provider.

To share a vault:

1. Create a new vault in Enpass and sync it with a separate cloud account (can be Dropbox, Google Drive, or OneDrive).

2. Share that cloud login and vault password with your wife.

3. She can then add the vault in Enpass → Settings → Vaults → Add new vault → Restore from cloud.

About 2FA:
Each user will need to complete 2FA once when first signing in. After Enpass is authorized, 2FA won’t be required again unless the connection is reset.

We understand it’s not as simple as expected, and we appreciate your honest feedback. Please let me know if you’d like help setting up the shared vault step-by-step.

Thank you for sharing the screenshot. However, we’ll need a screenshot that shows the iCloud account being used on both devices.

Please make sure that both devices are signed in with the same iCloud account. If they’re not, then while connecting the vault to the cloud on your wife’s device, please select “Connect with a different cloud account.”

Once you’ve verified this, please share the screenshots so we can proceed with further checks.

I discussed this with our technical team, and unfortunately, Enpass does not currently have an option to disable the large blue dropdown from the browser plugin. We truly appreciate you bringing this concern to our attention.

I have submitted this as a feature request to our technical team for consideration in future updates. Please understand that several factors need to be considered before any changes can be implemented.

Thank you again for your understanding and patience.
#SI-4546