You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Starting with last evening all REST API calls to a harbor.status.im/wakuorg/go-waku:latest node return 200 with empty response string ''
To Reproduce
Steps to reproduce the behavior:
Start a node and do any REST API request ex:
curl -v -X GET "http://127.0.0.1:31600/debug/v1/info" -H "Content-Type: application/json"
Note: Unnecessary use of -X or --request, GET is already inferred.
* Trying 127.0.0.1:31600...
* Connected to 127.0.0.1 (127.0.0.1) port 31600 (#0)
> GET /debug/v1/info HTTP/1.1
> Host: 127.0.0.1:31600
> User-Agent: curl/7.81.0
> Accept: */*
> Content-Type: application/json
>
* Mark bundle as not supporting multiuse
< HTTP/1.1 200 OK
< Access-Control-Allow-Origin: *
< Cache-Control: no-cache, no-store, no-transform, must-revalidate, private, max-age=0
< Expires: Thu, 01 Jan 1970 00:00:00 UTC
< Pragma: no-cache
< X-Accel-Expires: 0
< Date: Wed, 27 Mar 2024 07:03:30 GMT
< Content-Length: 0
<
* Connection #0 to host 127.0.0.1 left intact
(.venv) fbarbu15@florin-dell-pc:~/WORK_DIR/waku-interop-tests$
Describe the bug
Starting with last evening all REST API calls to a
harbor.status.im/wakuorg/go-waku:latest
node return 200 with empty response string ''To Reproduce
Steps to reproduce the behavior:
docker_log.log
The text was updated successfully, but these errors were encountered: