search

walt-id / waltid-walletkit

Toolkit for SSI and NFT/SBT wallets
https://docs.walt.id
Apache License 2.0
31 stars 25 forks source link

Backend delivering empty responses #7

Closed pawel-kow closed 2 years ago

pawel-kow commented 2 years ago

Build and started the backend via docker as in README 

docker build -t waltid/ssikit-wallet-backend .
docker run -it -p 8080:8080 waltid/ssikit-wallet-backend

Server is responding with empty responses

$ curl -v http://127.0.0.1:8080/api/swagger
* Expire in 0 ms for 6 (transfer 0x7fffbbb6bfb0)
*   Trying 127.0.0.1...
* TCP_NODELAY set
* Expire in 200 ms for 4 (transfer 0x7fffbbb6bfb0)
* Connected to 127.0.0.1 (127.0.0.1) port 8080 (#0)
> GET /api/swagger HTTP/1.1
> Host: 127.0.0.1:8080
> User-Agent: curl/7.64.0
> Accept: */*
>
* Empty reply from server
* Connection #0 to host 127.0.0.1 left intact
curl: (52) Empty reply from server

Same if using docker compose from the /docker folder (nginx upstream error).

YassineOuahidi commented 2 years ago

I still get the same issue

severinstampler commented 2 years ago

the problem has been solved with rev.: ce2bc1904804c24b187921bd715ec9a6d5fa57a1 The point is that the container needs to bind to the public interface 0.0.0.0, which the docker build makes sure of by setting the corresponding environment variable. if the problem persists for you, please update the image (docker pull) or update the sources (git pull) and rebuild the image.