search

input-output-hk / smash

Stakepool Metadata Aggregation Server
36 stars 7 forks source link

Returning 403/404 error with no data for some pools #175

Open yushih opened 3 years ago

yushih commented 3 years ago

As of now:

$ curl -v https://smash.cardano-mainnet.iohk.io/api/v1/metadata/c73186434c6fc6676bd67304d34518fc6fd7d5eaddaf78641b1e7dcf/26bc325d205e6714965ca6ba336ecbf29333c7af9b76b21b59bad2c4ed59bf52
*   Trying 18.158.166.36...
* Connected to smash.cardano-mainnet.iohk.io (18.158.166.36) port 443 (#0)
...
> GET /api/v1/metadata/c73186434c6fc6676bd67304d34518fc6fd7d5eaddaf78641b1e7dcf/26bc325d205e6714965ca6ba336ecbf29333c7af9b76b21b59bad2c4ed59bf52 HTTP/1.1
> Host: smash.cardano-mainnet.iohk.io
> User-Agent: curl/7.47.0
> Accept: */*
> 
< HTTP/1.1 403 Forbidden
< Server: nginx
< Date: Mon, 12 Jul 2021 11:26:23 GMT
< Content-Length: 0
< Connection: keep-alive
< X-Varnish: 207569092 458783
< Age: 329423
< Via: 1.1 varnish (Varnish/6.5)
< x-cache: hit cached
< Vary: Origin
< Access-Control-Allow-Methods: GET, PATCH, OPTIONS
< Access-Control-Allow-Headers: User-Agent,X-Requested-With,Content-Type
< 
$ curl -v https://smash.cardano-mainnet.iohk.io/api/v1/metadata/d264ba622976fe65ed0d194175afe80927e379ac23de5e6c3d42febb/e75a2bf2d6fa50bcc8cf6523592316b9ec582cc6e3a7f4bb47a831c287d165ef
*   Trying 18.158.166.36...
* Connected to smash.cardano-mainnet.iohk.io (18.158.166.36) port 443 (#0)
...
> GET /api/v1/metadata/d264ba622976fe65ed0d194175afe80927e379ac23de5e6c3d42febb/e75a2bf2d6fa50bcc8cf6523592316b9ec582cc6e3a7f4bb47a831c287d165ef HTTP/1.1
> Host: smash.cardano-mainnet.iohk.io
> User-Agent: curl/7.47.0
> Accept: */*
> 
< HTTP/1.1 404 Not Found
< Server: nginx
< Date: Mon, 12 Jul 2021 11:34:16 GMT
< Content-Length: 0
< Connection: keep-alive
< X-Varnish: 207084453 208312326
< Age: 1425
< Via: 1.1 varnish (Varnish/6.5)
< x-cache: hit cached
< Vary: Origin
< Access-Control-Allow-Methods: GET, PATCH, OPTIONS
< Access-Control-Allow-Headers: User-Agent,X-Requested-With,Content-Type
<

But the metadata are correctly registered: https://cardanoscan.io/pool/c73186434c6fc6676bd67304d34518fc6fd7d5eaddaf78641b1e7dcf?tab=metadata https://cardanoscan.io/pool/d264ba622976fe65ed0d194175afe80927e379ac23de5e6c3d42febb?tab=metadata

The issue https://github.com/Emurgo/yoroi-frontend/issues/2164 is likely caused by the same problem occurring on Yoroi's SMASH server instance.

jbgi commented 3 years ago

For the second one (d264ba622976fe65ed0d194175afe80927e379ac23de5e6c3d42febb) the issue seems to be that the metadata url is offline: https://cardanoswiss.ch/wp-content/uploads/2021/02/metadata.json

Investigating the first one.

woltere commented 3 years ago

I'm experiencing this issue too daedalus does not show the pool anymore or as unknown

The transaction contains the correct value which not seem to be picked up by smash.

https://cardanoscan.io/transaction/b6d49750a194d494752c98612420cfce50425eca490edb8a7c81f68ac0cc8ede?tab=poolcertificates

This URL give a 404 where I expected the metadata to be returned https://smash.cardano-mainnet.iohk.io/api/v1/metadata/277b4daf3e85094412cb9471891ac0495a158794518bc82b38dca607/613270c8660972262b94074ea3c8e1eeaef4bbf9927c3d7c1ee455d370155acc

The old hash still returns the metadata old metadata https://smash.cardano-mainnet.iohk.io/api/v1/metadata/277b4daf3e85094412cb9471891ac0495a158794518bc82b38dca607/a5979cdc12985f7fbad55f2eef54785a5353dd19902fdf429a3c467cc8f56ccb

vsubhuman commented 3 years ago

@jbgi , any news for this?