Setup account on multiple machines

Checklist
[ X] I have read intro post
[ X] I have read the tutorials, help and searched for similar issues
[ X] I provide relevant information about my server (component names and versions, etc.)
I provide a copy of my logs and healthcheck
[ X] I describe the steps I have taken to trouble shoot the problem
[ X] I describe the steps on how to reproduce the issue

Hello,
I am running a self-hosted instance of Passbolt CE using the latest docker image. Went successfully through the process and there are no issues when executing the healtcheck.

My troubles are when trying to set up my already configured Passbolt account on my second laptop.
I provide the account’s email address on the landing page, but no email is coming to the mailbox.
The email functionality, nevertheless, is certainly working.
Browsing the forum I stumbled upon this (rather old) thread saying I shall use the recovery process for setting up the account on the second machine.
So far so good, but following the instructions, I am still required to provide the mail address at the recovery url <mypassbolt.address>/recover, after which no email is coming in.
I tried explicitly setting the PASSBOLT_PLUGINS_ACCOUNT_RECOVERY_ENABLED to true, but still no luck.
No clue or option for configuring recover on the administration section of the system either.

What do I miss?
Am I hitting a limitation of the CE version not allowing use of same account on multiple machines?

Well, this worked well and I was able to pass the account verification step and use recovery for setting up the browser on the second machine…
Though much easier had the email been sent as expected :roll_eyes:

Hello @ananchev, welcome to the community :slight_smile:

Configuring the browser extension on multiple device is classic and is not limited by any plugins at all.

This is not the right environment variable as it is dedicated for the account recovery feature which is not included in the community edition.

About the workaround you’ve found, this is definitely not what we would recommend since there is a dedicated CLI command that has been introduced since then. You can use this command instead from the passbolt container itself.

su -s /bin/bash -c "/usr/share/php/passbolt/bin/cake passbolt recover_user -c -u YOUR_EMAIL" www-data

Regarding the issues you are encountering, this looks like a misconfigured SMTP. Please, could you share the output of this command?

su -s /bin/bash -c "/usr/share/php/passbolt/bin/cake passbolt show_queued_emails --failed" www-data

You can censor the email address and learn more about this command here

Thanks a ton Antony for the rapid reaction!

This worked a charm and way faster than falling back to querying the DB. Thank you :beers:

Here what I get:


Looking at the timestamps and subjects these are mails from earlier when likely I had not yet configured the emailing.
I did later and mails worked.

For emailing I did the free Google email service with app password. I checked the limits for it and certainly I am well beyond, but maybe another peculiarity with gmail?

Based on the output it looks like the other emails didn’t failed or may not have been sent.

I am interested to see the output of:

su -s /bin/bash -c "/usr/share/php/passbolt/bin/cake passbolt show_queued_emails" www-data

and

ls -ail /etc/cron.d/passbolt-ce-server && service cron status

Finally, I’d like to see the output of:

su -s /bin/bash -c "/usr/share/php/passbolt/bin/cake passbolt send_test_email --recipient=YOUR_EMAIl" www-data

Here they are :slight_smile:
Posting only one screenshot allowed for me, so the output of the other commands is in a code block.

su -s /bin/bash -c "/usr/share/php/passbolt/bin/cake passbolt show_queued_emails" www-data

ls -ail /etc/cron.d/passbolt-ce-server && service cron status
root@4a92ef2d58d9:/usr/share/php/passbolt# ls -ail /etc/cron.d/passbolt-ce-server && service cron status
1227927 -rw-r--r--. 1 root root 428 Aug 14 10:30 /etc/cron.d/passbolt-ce-server
cron is running.
root@4a92ef2d58d9:/usr/share/php/passbolt#
su -s /bin/bash -c "/usr/share/php/passbolt/bin/cake passbolt send_test_email --recipient=YOUR_EMAIl" www-data
root@4a92ef2d58d9:/usr/share/php/passbolt# su -s /bin/bash -c "/usr/share/php/passbolt/bin/cake passbolt send_test_email --recipient=myvalidemail@was.here" www-data

     ____                  __          ____
    / __ \____  _____ ____/ /_  ____  / / /_
   / /_/ / __ `/ ___/ ___/ __ \/ __ \/ / __/
  / ____/ /_/ (__  |__  ) /_/ / /_/ / / /
 /_/    \__,_/____/____/_.___/\____/_/\__/

 Open source password manager for teams
-------------------------------------------------------------------------------
 Debug email shell
-------------------------------------------------------------------------------
App\Utility\OpenPGP\Backends\Gnupg::setDecryptKeyFromFingerprint(): Argument #1 ($fingerprint) must be of type string, null given, called in /usr/share/php/passbolt/plugins/PassboltCe/SmtpSettings/src/Service/SmtpSettingsGetSettingsInDbService.php on line 109
root@4a92ef2d58d9:/usr/share/php/passbolt#

I see the test email command failing, but actually when triggering this via the admin section in the UI, it is coming as expected

It looks like there might be an issues with the key fingerprint.

You can display the key(s) fingerprint with this command:

su -s /bin/bash -c "gpg --list-keys" www-data

And then add the PASSBOLT_GPG_SERVER_KEY_FINGERPRINT environent variable with the matching fingerprint in the docker-compose-ce.yaml file?

Small steps… :wink:

Setting the PASSBOLT_GPG_SERVER_KEY_FINGERPRINT environment variable worked out and now the test email via command line goes through successfully too.

Nevertheless, the root issue of not receiving the ‘recovery confirmation’ email when triggering account recovery using https://my_passbolt_url/recover was still not solved.

I do see the recovery token using the command you provided earlier and hence I am not blocked, but still something does not function just right.

Cheers,
Anton

That’s nice to hear :wink:

I have another idea regarding the recovery emails. We’ve seen similar issues in the past where these kinds of emails “Your account recovery, $name” are flagged as potential spam due to the subject of the email.

Have you check the email spam folder or anywhere else it could have been automatically moved?

If not, then I would recommend sharing a screenshot of the email notifications settings, especially the recovery part from Administration > Email Notifications

I finally figured it out, thank you again Antony!

What happened was indeed the emails were filtered out, though not landing in the junk but elsewhere.
Reason was I used Gmail’s SMTP, but sent from custom domain - a ‘trick’, that had resulted into unverified emails ultimately being blocked… :unamused:
No free lunch as they say, but some fair learning on the other hand.

Glad to hear that it was indeed the issues. We live and we learn I agree :wink:

Best regards