Authorization token not recieved.

[mustafa404]

I was finally able to self-host Keygen. I now moved onto test the API calls starting with the authorization token but I am not getting any response. Following is my verbose output:

curl -v -X POST https://api.keygen.localhost/v1/accounts/11de38c9-ad90-4019-b32b-232073c82b73/tokens \
>   -H 'Accept: application/vnd.api+json' \
>   -u [email protected]:mustafa
*   Trying 127.0.0.1:443...
* TCP_NODELAY set
* Connected to api.keygen.localhost (127.0.0.1) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
* TLSv1.3 (IN), TLS handshake, Certificate (11):
* TLSv1.3 (IN), TLS handshake, CERT verify (15):
* TLSv1.3 (IN), TLS handshake, Finished (20):
* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.3 (OUT), TLS handshake, Finished (20):
* SSL connection using TLSv1.3 / TLS_AES_128_GCM_SHA256
* ALPN, server accepted to use h2
* Server certificate:
*  subject: C=US; ST=CA; L=NY; O=DBS; OU=IT; CN=api.keygen.localhost; [email protected]
*  start date: Jan 31 11:42:47 2024 GMT
*  expire date: Jan 30 11:42:47 2025 GMT
*  common name: api.keygen.localhost (matched)
*  issuer: C=US; ST=CA; L=NY; O=DBS; OU=IT; CN=api.keygen.localhost; [email protected]
*  SSL certificate verify ok.
* Using HTTP2, server supports multi-use
* Connection state changed (HTTP/2 confirmed)
* Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
* Server auth using Basic with user '[email protected]'
* Using Stream ID: 1 (easy handle 0x55c331564320)
> POST /v1/accounts/11de38c9-ad90-4019-b32b-232073c82b73/tokens HTTP/2
> Host: api.keygen.localhost
> authorization: Basic bXVzdGFmYUBkcmVhbWJpZ3NlbWkuY29tOm11c3RhZmE=
> user-agent: curl/7.68.0
> accept: application/vnd.api+json
> 
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* Connection state changed (MAX_CONCURRENT_STREAMS == 250)!
< HTTP/2 200 
< server: Caddy
< content-length: 0
< date: Thu, 01 Feb 2024 07:34:35 GMT
< 
* Connection #0 to host api.keygen.localhost left intact

[ezekg]

Since you're receiving an empty response from Caddy, this looks like a reverse proxy issue. Do you see any logs on your Keygen CE instance? You should see logs when a request hits Keygen. If you don't see any logs, then the request is not making it to Keygen and this is a Caddy configuration issue. You can get help with that in Caddy's discussion forum.

[mustafa404]

I switched from Caddy V2 to Caddy V1 and it resolved the problem. Strange but it was resolved. Thanks