VMware NSX

 Events API Internal server error

Peter De Wachter's profile image
Peter De Wachter posted Feb 27, 2025 08:39 AM

On my NSX manager deployment I cannot get the events api endpoint. All other endpoints work fine. I make the following call

curl -u admin-k  https://10.30.133.181/api/v1/events -v

the response:

* Server certificate:
*  subject: CN=cluster-nsx-manager; OU=NSX; O=VMware Inc.; L=Palo Alto; ST=CA; C=US
*  start date: Feb 11 15:55:22 2025 GMT
*  expire date: May 17 15:55:22 2027 GMT
*  issuer: CN=cluster-nsx-manager; OU=NSX; O=VMware Inc.; L=Palo Alto; ST=CA; C=US
*  SSL certificate verify result: self signed certificate (18), continuing anyway.
* using HTTP/1.x
* Server auth using Basic with user 'admin'
> GET /api/v1/events HTTP/1.1
> Host: 10.30.133.181
> Authorization: Basic YWRtaW46RDBudFVzM1IwMHQ/
> User-Agent: curl/8.7.1
> Accept: */*
>
* Request completely sent off
< HTTP/1.1 500 Internal Server Error
< content-length: 215
< content-type: application/json
< set-cookie: JSESSIONID=696D134689DB827A2AD1C67BCD99AF25; Path=/; Secure; HttpOnly; SameSite=Lax
< x-frame-options: SAMEORIGIN
< x-content-type-options: nosniff
< content-security-policy: frame-src 'self' https://*.vmware-aws.com/ https://*.vmware.com blob:; frame-ancestors 'self' https://*.vmware-aws.com/ https://*.vmware.com
< x-xss-protection: 1;mode=block
< strict-transport-security: max-age=31536000; includeSubDomains
< date: Thu, 27 Feb 2025 13:31:11 GMT
< server: envoy
<
{"module_name":"common-service","error_code":"98","error_message":"upstream connect error or disconnect/reset before headers. reset reason: connection failure, transport failure reason: delayed connect error: 111"}

What could be causing this if all other api endpoints I test work fine?

Thanks

Stephan_Zur's profile image
Stephan_Zur

Hi Peter,

Try curl -k -v -u admin --request GET 'https://10.30.133.181/api/v1/events'

Just tested in my lab. Works fine.

Stephan

Peter De Wachter's profile image
Peter De Wachter

Solution found, it didn't work when nsx manager deployment size was "small". increase to "medium to make it work