use aws ami ,
The data entered are not correct: The OpenPGP public key should not be empty.; The OpenPGP private key should not be empty.; The fingerprint should not be empty.
gpg --armor --export-secret-keys **@email Generate PRIVATE KEY ,Paste into the browser, next returns the above error message
I have read intro post: About the Installation Issues category
I have read the tutorials, help and searched for similar issues
I provide relevant information about my server (component names and versions, etc.)
I provide a copy of my logs and healthcheck
I describe the steps I have taken to trouble shoot the problem
I describe the steps on how to reproduce the issue
Can you explain a bit more precisely, is it the first time you are trying to log in into passbolt, was it working before? How can we reproduce this scenario?
Also, could you gives us the datacheck output
sudo su -s /bin/bash -c "/usr/share/php/passbolt/bin/cake passbolt datacheck --hide-success-details" www-data
I have read intro post: About the Installation Issues category
I have read the tutorials, help and searched for similar issues
I provide relevant information about my server (component names and versions, etc.)
I provide a copy of my logs and healthcheck
I describe the steps I have taken to trouble shoot the problem
I describe the steps on how to reproduce the issue
Does this issue is happening also if you are trying to create a gpg key from the webInstaller or is it only related to the key you are trying to import?
Yes, .txt should work, I have reproduced the installation and the creation/import process (copy/paste + import .txt) of the gpg and I am not able to get the same error.
It could be related to a time synchronization issue, can you ensure that NTP is active and running as shown here
root@ip-172-16-0-159:~# timedatectl status
Local time: Fri 2023-10-20 06:44:21 UTC
Universal time: Fri 2023-10-20 06:44:21 UTC
RTC time: Fri 2023-10-20 06:44:21
Time zone: Etc/UTC (UTC, +0000)
System clock synchronized: yes
NTP service: active
RTC in local TZ: no
AWS AMI deployment, forwarding intranet domain names through Ingress, passbolt not configured with 443, front-end checks are all HTTP requests, and configuring SSL certificates on the passbolt server to solve the problem