Mobile connect account

Installation Issues
1

Checklist
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

Hello.

I have install the mobile app
I have scan the QRcode
I enter my passphrase

and I get “credentials are invalide”

I’m pretty sure the issue is a time sync issue because time.is show me delay.
But I have no idea how to solve this issue ??
My phone don’t let me set NTP server …

log passbolt docker

172.18.0.4 - - [15/Dec/2022:13:59:32 +0000] “GET /auth/verify.json HTTP/1.1” 200 2852 “-” “okhttp/4.9.3”
2022-12-15 13:59:32,610 INFO reaped unknown pid 1308 (exit status 0)
2022-12-15 13:59:32,611 INFO reaped unknown pid 1310 (exit status 0)
172.18.0.4 - - [15/Dec/2022:13:59:32 +0000] “GET /auth/jwt/rsa.json HTTP/1.1” 200 1088 “-” “okhttp/4.9.3”
2022-12-15 13:59:32,755 INFO reaped unknown pid 1313 (exit status 0)
2022-12-15 13:59:32,755 INFO reaped unknown pid 1315 (exit status 0)
172.18.0.4 - - [15/Dec/2022:13:59:33 +0000] “POST /auth/jwt/login.json HTTP/1.1” 400 250 “-” “okhttp/4.9.3”
2022-12-15 13:59:33,438 INFO reaped unknown pid 1318 (exit status 0)
2022-12-15 13:59:33,439 INFO reaped unknown pid 1320 (exit status 0)
2022-12-15 13:59:33,439 INFO reaped unknown pid 1323 (exit status 0)
2022-12-15 13:59:33,440 INFO reaped unknown pid 1325 (exit status 0)
2022-12-15 13:59:33,440 INFO reaped unknown pid 1328 (exit status 0)
2022-12-15 13:59:33,440 INFO reaped unknown pid 1330 (exit status 0)
2022-12-15 13:59:33,440 INFO reaped unknown pid 1332 (exit status 0)
2022-12-15 13:59:33,441 INFO reaped unknown pid 1334 (exit status 0)

best regards

2

Hi @none1 Thanks for posting and welcome to the forum! We recently had another user with a similar problem. Mobile App - "invalid password"

Can you also post your mobile debug log?

3

Hello, thank you for your reply

here is the log

Device: samsung SM-G781B
Android 12 (31)
Passbolt 1.11.0-14

14:28:29 There was an error during unlockKey
go.Universe$proxyerror: gopenpgp: error in unlocking key: openpgp: invalid data: private key checksum failure
	at com.proton.Gopenpgp.crypto.Key.unlock(Native Method)
	at com.passbolt.mobile.android.gopenpgp.OpenPgp$unlockKey$2.invokeSuspend(OpenPgp.kt:98)
	at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
	at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:106)
	at kotlinx.coroutines.internal.LimitedDispatcher.run(LimitedDispatcher.kt:42)
	at kotlinx.coroutines.scheduling.TaskImpl.run(Tasks.kt:95)
	at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:570)
	at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:750)
	at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:677)
	at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:664)

go.Universe$proxyerror: gopenpgp: error in unlocking key: openpgp: invalid data: private key checksum failure
	at com.proton.Gopenpgp.crypto.Key.unlock(Native Method)
	at com.passbolt.mobile.android.gopenpgp.OpenPgp$unlockKey$2.invokeSuspend(OpenPgp.kt:98)
	at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
	at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:106)
	at kotlinx.coroutines.internal.LimitedDispatcher.run(LimitedDispatcher.kt:42)
	at kotlinx.coroutines.scheduling.TaskImpl.run(Tasks.kt:95)
	at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:570)
	at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:750)
	at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:677)
	at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:664)
14:28:29 gopenpgp: error in unlocking key: openpgp: invalid data: private key checksum failure
14:39:08 File logging tree planted
14:39:46 --> PUT https://passboltxxxxx/mobile/transfers/8d5d8b56-6291-4202-9b9b-eff8306e2bd1/27adc4c8-0390-417b-9271-a290e1a13d1e.json h2 (41-byte body)
14:39:46 <-- 200 https://passboltxxxxx/mobile/transfers/8d5d8b56-6291-4202-9b9b-eff8306e2bd1/27adc4c8-0390-417b-9271-a290e1a13d1e.json (151ms, unknown-length body)
14:39:48 --> PUT https://passboltxxxxx/mobile/transfers/8d5d8b56-6291-4202-9b9b-eff8306e2bd1/27adc4c8-0390-417b-9271-a290e1a13d1e.json h2 (41-byte body)
14:39:48 <-- 200 https://passboltxxxxx/mobile/transfers/8d5d8b56-6291-4202-9b9b-eff8306e2bd1/27adc4c8-0390-417b-9271-a290e1a13d1e.json (136ms, unknown-length body)
14:39:49 --> PUT https://passboltxxxxx/mobile/transfers/8d5d8b56-6291-4202-9b9b-eff8306e2bd1/27adc4c8-0390-417b-9271-a290e1a13d1e.json h2 (41-byte body)
14:39:49 <-- 200 https://passboltxxxxx/mobile/transfers/8d5d8b56-6291-4202-9b9b-eff8306e2bd1/27adc4c8-0390-417b-9271-a290e1a13d1e.json (171ms, unknown-length body)
14:39:50 --> PUT https://passboltxxxxx/mobile/transfers/8d5d8b56-6291-4202-9b9b-eff8306e2bd1/27adc4c8-0390-417b-9271-a290e1a13d1e.json h2 (41-byte body)
14:39:50 <-- 200 https://passboltxxxxx/mobile/transfers/8d5d8b56-6291-4202-9b9b-eff8306e2bd1/27adc4c8-0390-417b-9271-a290e1a13d1e.json (212ms, unknown-length body)
14:39:51 Saving private key.
14:39:51 --> PUT https://passboltxxxxx/mobile/transfers/8d5d8b56-6291-4202-9b9b-eff8306e2bd1/27adc4c8-0390-417b-9271-a290e1a13d1e.json?contain%5Buser.profile%5D=1 h2 (38-byte body)
14:39:51 <-- 200 https://passboltxxxxx/mobile/transfers/8d5d8b56-6291-4202-9b9b-eff8306e2bd1/27adc4c8-0390-417b-9271-a290e1a13d1e.json?contain%5Buser.profile%5D=1 (184ms, unknown-length body)
14:39:54 Checking biometry state
14:40:20 There was an error during unlockKey
go.Universe$proxyerror: gopenpgp: error in unlocking key: openpgp: invalid data: private key checksum failure
	at com.proton.Gopenpgp.crypto.Key.unlock(Native Method)
	at com.passbolt.mobile.android.gopenpgp.OpenPgp$unlockKey$2.invokeSuspend(OpenPgp.kt:98)
	at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
	at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:106)
	at kotlinx.coroutines.internal.LimitedDispatcher.run(LimitedDispatcher.kt:42)
	at kotlinx.coroutines.scheduling.TaskImpl.run(Tasks.kt:95)
	at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:570)
	at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:750)
	at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:677)
	at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:664)

go.Universe$proxyerror: gopenpgp: error in unlocking key: openpgp: invalid data: private key checksum failure
	at com.proton.Gopenpgp.crypto.Key.unlock(Native Method)
	at com.passbolt.mobile.android.gopenpgp.OpenPgp$unlockKey$2.invokeSuspend(OpenPgp.kt:98)
	at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
	at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:106)
	at kotlinx.coroutines.internal.LimitedDispatcher.run(LimitedDispatcher.kt:42)
	at kotlinx.coroutines.scheduling.TaskImpl.run(Tasks.kt:95)
	at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:570)
	at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:750)
	at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:677)
	at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:664)
14:40:20 gopenpgp: error in unlocking key: openpgp: invalid data: private key checksum failure
14:45:57 --> PUT https://passboltxxxxx/mobile/transfers/1c7d062e-6a80-41f8-84d6-3e2f9067cc48/82266921-6eb4-49e9-8429-34a1e00a3f06.json h2 (41-byte body)
14:45:57 <-- 200 https://passboltxxxxx/mobile/transfers/1c7d062e-6a80-41f8-84d6-3e2f9067cc48/82266921-6eb4-49e9-8429-34a1e00a3f06.json (126ms, unknown-length body)
14:45:57 --> PUT https://passboltxxxxx/mobile/transfers/1c7d062e-6a80-41f8-84d6-3e2f9067cc48/82266921-6eb4-49e9-8429-34a1e00a3f06.json h2 (41-byte body)
14:45:58 <-- 200 https://passboltxxxxx/mobile/transfers/1c7d062e-6a80-41f8-84d6-3e2f9067cc48/82266921-6eb4-49e9-8429-34a1e00a3f06.json (156ms, unknown-length body)
14:45:58 --> PUT https://passboltxxxxx/mobile/transfers/1c7d062e-6a80-41f8-84d6-3e2f9067cc48/82266921-6eb4-49e9-8429-34a1e00a3f06.json h2 (41-byte body)
14:45:58 <-- 200 https://passboltxxxxx/mobile/transfers/1c7d062e-6a80-41f8-84d6-3e2f9067cc48/82266921-6eb4-49e9-8429-34a1e00a3f06.json (166ms, unknown-length body)
14:45:59 --> PUT https://passboltxxxxx/mobile/transfers/1c7d062e-6a80-41f8-84d6-3e2f9067cc48/82266921-6eb4-49e9-8429-34a1e00a3f06.json h2 (41-byte body)
14:45:59 <-- 200 https://passboltxxxxx/mobile/transfers/1c7d062e-6a80-41f8-84d6-3e2f9067cc48/82266921-6eb4-49e9-8429-34a1e00a3f06.json (134ms, unknown-length body)
14:45:59 Saving private key.
14:45:59 --> PUT https://passboltxxxxx/mobile/transfers/1c7d062e-6a80-41f8-84d6-3e2f9067cc48/82266921-6eb4-49e9-8429-34a1e00a3f06.json?contain%5Buser.profile%5D=1 h2 (38-byte body)
14:46:00 <-- 200 https://passboltxxxxx/mobile/transfers/1c7d062e-6a80-41f8-84d6-3e2f9067cc48/82266921-6eb4-49e9-8429-34a1e00a3f06.json?contain%5Buser.profile%5D=1 (203ms, unknown-length body)
14:46:01 Checking biometry state
14:46:11 Passphrase cache cleared
14:46:11 Passphrase cached
14:46:11 Getting server pgp and rsa keys
14:46:11 --> GET https://passboltxxxxx/auth/verify.json h2
14:46:11 <-- 200 https://passboltxxxxx/auth/verify.json (183ms, unknown-length body)
14:46:11 --> GET https://passboltxxxxx/auth/jwt/rsa.json h2
14:46:12 <-- 200 https://passboltxxxxx/auth/jwt/rsa.json (121ms, unknown-length body)
14:46:12 Getting server pgp and rsa keys succeeded
14:46:12 Verifying server fingerprint
14:46:12 Server key fingerprint is valid
14:46:12 Preparing sign in challenge
14:46:12 Prepared sign in challenge
14:46:12 Signing in
14:46:12 --> POST https://passboltxxxxx/auth/jwt/login.json h2 (1642-byte body)
14:46:12 <-- 400 https://passboltxxxxx/auth/jwt/login.json (264ms, unknown-length body)
14:46:12 Failure during sign in: The credentials are invalid.
14:46:18 App went background
14:46:18 Passphrase cache cleared
14:52:59 Passphrase cache cleared
14:52:59 Passphrase cached
14:52:59 Getting server pgp and rsa keys
14:53:00 --> GET https://passboltxxxxx/auth/verify.json h2
14:53:00 <-- 200 https://passboltxxxxx/auth/verify.json (164ms, unknown-length body)
14:53:00 --> GET https://passboltxxxxx/auth/jwt/rsa.json h2
14:53:00 <-- 200 https://passboltxxxxx/auth/jwt/rsa.json (113ms, unknown-length body)
14:53:00 Getting server pgp and rsa keys succeeded
14:53:00 Verifying server fingerprint
14:53:00 Server key fingerprint is valid
14:53:00 Preparing sign in challenge
14:53:00 Prepared sign in challenge
14:53:00 Signing in
14:53:00 --> POST https://passboltxxxxx/auth/jwt/login.json h2 (1642-byte body)
14:53:01 <-- 400 https://passboltxxxxx/auth/jwt/login.json (243ms, unknown-length body)
14:53:01 Failure during sign in: The credentials are invalid.
14:53:07 Passphrase cache cleared
14:53:07 Passphrase cached
14:53:07 Getting server pgp and rsa keys
14:53:07 --> GET https://passboltxxxxx/auth/verify.json h2
14:53:07 <-- 200 https://passboltxxxxx/auth/verify.json (149ms, unknown-length body)
14:53:07 --> GET https://passboltxxxxx/auth/jwt/rsa.json h2
14:53:07 <-- 200 https://passboltxxxxx/auth/jwt/rsa.json (120ms, unknown-length body)
14:53:07 Getting server pgp and rsa keys succeeded
14:53:07 Verifying server fingerprint
14:53:07 Server key fingerprint is valid
14:53:07 Preparing sign in challenge
14:53:08 Prepared sign in challenge
14:53:08 Signing in
14:53:08 --> POST https://passboltxxxxx/auth/jwt/login.json h2 (1642-byte body)
14:53:08 <-- 400 https://passboltxxxxx/auth/jwt/login.json (270ms, unknown-length body)
14:53:08 Failure during sign in: The credentials are invalid.
14:53:14 Passphrase cache cleared
14:53:14 Passphrase cached
14:53:14 Getting server pgp and rsa keys
14:53:14 --> GET https://passboltxxxxx/auth/verify.json h2
14:53:14 <-- 200 https://passboltxxxxx/auth/verify.json (158ms, unknown-length body)
14:53:14 --> GET https://passboltxxxxx/auth/jwt/rsa.json h2
14:53:14 <-- 200 https://passboltxxxxx/auth/jwt/rsa.json (130ms, unknown-length body)
14:53:14 Getting server pgp and rsa keys succeeded
14:53:14 Verifying server fingerprint
14:53:14 Server key fingerprint is valid
14:53:14 Preparing sign in challenge
14:53:15 Prepared sign in challenge
14:53:15 Signing in
14:53:15 --> POST https://passboltxxxxx/auth/jwt/login.json h2 (1642-byte body)
14:53:15 <-- 400 https://passboltxxxxx/auth/jwt/login.json (314ms, unknown-length body)
14:53:15 Failure during sign in: The credentials are invalid.
14:53:45 App went background
14:53:45 Passphrase cache cleared
14:59:31 Passphrase cache cleared
14:59:31 Passphrase cached
14:59:31 Getting server pgp and rsa keys
14:59:31 --> GET https://passboltxxxxx/auth/verify.json h2
14:59:31 <-- 200 https://passboltxxxxx/auth/verify.json (115ms, unknown-length body)
14:59:31 --> GET https://passboltxxxxx/auth/jwt/rsa.json h2
14:59:31 <-- 200 https://passboltxxxxx/auth/jwt/rsa.json (107ms, unknown-length body)
14:59:31 Getting server pgp and rsa keys succeeded
14:59:31 Verifying server fingerprint
14:59:31 Server key fingerprint is valid
14:59:31 Preparing sign in challenge
14:59:32 Prepared sign in challenge
14:59:32 Signing in
14:59:32 --> POST https://passboltxxxxx/auth/jwt/login.json h2 (1642-byte body)
14:59:32 <-- 400 https://passboltxxxxx/auth/jwt/login.json (279ms, unknown-length body)
14:59:32 Failure during sign in: The credentials are invalid.
15:00:02 App went background
15:00:02 Passphrase cache cleared
17:55:01 Passphrase cache cleared
17:55:01 Passphrase cached
17:55:01 Getting server pgp and rsa keys
17:55:02 --> GET https://passboltxxxxx/auth/verify.json h2
17:55:02 <-- 200 https://passboltxxxxx/auth/verify.json (240ms, unknown-length body)
17:55:02 --> GET https://passboltxxxxx/auth/jwt/rsa.json h2
17:55:02 <-- 200 https://passboltxxxxx/auth/jwt/rsa.json (145ms, unknown-length body)
17:55:02 Getting server pgp and rsa keys succeeded
17:55:02 Verifying server fingerprint
17:55:02 Server key fingerprint is valid
17:55:02 Preparing sign in challenge
17:55:02 Prepared sign in challenge
17:55:02 Signing in
17:55:02 --> POST https://passboltxxxxx/auth/jwt/login.json h2 (1642-byte body)
17:55:03 <-- 400 https://passboltxxxxx/auth/jwt/login.json (317ms, unknown-length body)
17:55:03 Failure during sign in: The credentials are invalid.
11:21:02 File logging tree planted
11:22:48 --> PUT https://passboltxxxxx/mobile/transfers/f3648cb9-1db1-4975-92d1-027347527951/ee61a830-731c-44f4-a42b-d1cce100c3bb.json h2 (41-byte body)
11:22:49 <-- 200 https://passboltxxxxx/mobile/transfers/f3648cb9-1db1-4975-92d1-027347527951/ee61a830-731c-44f4-a42b-d1cce100c3bb.json (130ms, unknown-length body)
11:22:49 --> PUT https://passboltxxxxx/mobile/transfers/f3648cb9-1db1-4975-92d1-027347527951/ee61a830-731c-44f4-a42b-d1cce100c3bb.json h2 (41-byte body)
11:22:49 <-- 200 https://passboltxxxxx/mobile/transfers/f3648cb9-1db1-4975-92d1-027347527951/ee61a830-731c-44f4-a42b-d1cce100c3bb.json (131ms, unknown-length body)
11:22:50 --> PUT https://passboltxxxxx/mobile/transfers/f3648cb9-1db1-4975-92d1-027347527951/ee61a830-731c-44f4-a42b-d1cce100c3bb.json h2 (41-byte body)
11:22:50 <-- 200 https://passboltxxxxx/mobile/transfers/f3648cb9-1db1-4975-92d1-027347527951/ee61a830-731c-44f4-a42b-d1cce100c3bb.json (141ms, unknown-length body)
11:22:51 --> PUT https://passboltxxxxx/mobile/transfers/f3648cb9-1db1-4975-92d1-027347527951/ee61a830-731c-44f4-a42b-d1cce100c3bb.json h2 (41-byte body)
11:22:51 <-- 200 https://passboltxxxxx/mobile/transfers/f3648cb9-1db1-4975-92d1-027347527951/ee61a830-731c-44f4-a42b-d1cce100c3bb.json (184ms, unknown-length body)
11:22:52 Saving private key.
11:22:52 --> PUT https://passboltxxxxx/mobile/transfers/f3648cb9-1db1-4975-92d1-027347527951/ee61a830-731c-44f4-a42b-d1cce100c3bb.json?contain%5Buser.profile%5D=1 h2 (38-byte body)
11:22:52 <-- 200 https://passboltxxxxx/mobile/transfers/f3648cb9-1db1-4975-92d1-027347527951/ee61a830-731c-44f4-a42b-d1cce100c3bb.json?contain%5Buser.profile%5D=1 (158ms, unknown-length body)
11:22:54 Checking biometry state
11:23:08 Passphrase cache cleared
11:23:08 Passphrase cached
11:23:08 Getting server pgp and rsa keys
11:23:08 --> GET https://passboltxxxxx/auth/verify.json h2
11:23:08 <-- 200 https://passboltxxxxx/auth/verify.json (172ms, unknown-length body)
11:23:09 --> GET https://passboltxxxxx/auth/jwt/rsa.json h2
11:23:09 <-- 200 https://passboltxxxxx/auth/jwt/rsa.json (142ms, unknown-length body)
11:23:09 Getting server pgp and rsa keys succeeded
11:23:09 Verifying server fingerprint
11:23:09 Server key fingerprint is valid
11:23:09 Preparing sign in challenge
11:23:09 Prepared sign in challenge
11:23:09 Signing in
11:23:09 --> POST https://passboltxxxxx/auth/jwt/login.json h2 (1642-byte body)
11:23:09 <-- 400 https://passboltxxxxx/auth/jwt/login.json (215ms, unknown-length body)
11:23:09 Failure during sign in: The credentials are invalid.
11:23:24 App went background
11:23:24 Passphrase cache cleared
4

Thank you for posting the logs. You could attempt to manually set the time on your phone using the Clock. Use the server time as a reference as that would be the goal. However, network connections provide the time to your phone and if it gets reset back to auto you’ll have the same issues. Hopefully you can figure out why that is happening as well.

5

hello, thank

It is not possible to set time perfectly manually. This issue is really blocking for the connection.
The samsung NTP (I didn’t find ^^) or GPS time is not the same as server NTP (ubuntu or other).

Why do we need to have exact same time ? is it a security need ?
What is the max time delay ? because I get 1 sec after.

Just check on another android and get the same delay
but on 2 Iphone the time is exact.

best regards

6

Hello

Maybe the issue is my server/phone is GMT+1 and the docker UTC ?

maybe …

7

I once had the right time but wrong timezone. Something like this would also cause the issue.

8

hello

what is a “right” timezone :smiley: ?

9

I believe a fresh Windows install set the timezone to PST and because there was no internet connection at the time and I was in EST, the time was way off. I changed the time (and only the time) without thinking. This required disabling the automatic time adjustment so when the internet connection was fixed it didn’t change. By moving it 3 hours forward with the wrong timezone, I was actually in the future. It was that way for weeks and then my passbolt install wouldn’t work…because although the time seemed right, I was in the wrong timezone.