I noticed this http://10.1.200.93/auth/auth/verify and it gives plugin-check gpg error.
If I run curl http://10.1.200.93/auth/verify.json I get the following. {"header":{"id":"49cadf37-0eaf-3689-a8f7-430b02908cac","status":"success","title":"app_auth_verify_success","servertime":1509704089,"message":null,"controller":"Auth","action":"verify"},"body":{"fingerprint":"12165C90BB8584E58E4DAF19B2C4B036B252BB7B","keydata":"-----BEGIN...
Server is CentOS v7/ Nginx 1.12 / php-7.1
This is only log entries that I get from nginx access.log file
172.16.10.2 - - [03/Nov/2017:17:00:02 +0530] "GET / HTTP/1.1" 302 5 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.100 Safari/537.36" "-"
172.16.10.2 - - [03/Nov/2017:17:00:02 +0530] "GET /auth/login HTTP/1.1" 200 1730 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.100 Safari/537.36" "-"
172.16.10.2 - - [03/Nov/2017:17:00:03 +0530] "POST /auth/verify.json HTTP/1.1" 200 2 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.100 Safari/537.36" "-"
@hirantha which error message do you get and on which step? The initial github ticket is not clear.
Can you check in the browser logs if there are any network errors / error code on some specific calls?
Can you go to chrome://extensions/ and click on “inspect view” for the login page, that will show the extension log. Let’s see if there are information there.
If I catch the GnuPG entry while fast refresh the browser, I can see it tries to connect http://10.1.200.93/auth/auth/verify which is not exist. I assume this is nginx rewrite rule issue but still I can’t get this sorted even check the CackePHP nginx guides.
The “There is no user associated with this key” is more interesting it means that when the client is sending the user fingerprint the server cannot find the key and/or the user associated with it.
How did you perform the setup? Did you import and existing key or generate a new one?
Can you try creating a new user and following the setup again to see if you get the same error?