hashlips-lab / safe-nft-metadata-provider

A safe metadata provider for your NFT collection.
MIT License
74 stars 77 forks source link

Image not showing but json is fine #43

Closed andreleo6 closed 2 years ago

andreleo6 commented 2 years ago

Hi. When I type the url for the json files of the already minted NFTs, the json files show just fine, with the image's urls. But when I try to reach the images it just gives me the 500 Internal Server Error. Any clue why this might be happening?

andreleo6 commented 2 years ago

This is the runtime log

{"message":"Matched route \"get_asset\".","context":{"route":"get_asset","route_parameters":{"_route":"get_asset","_format":"png","_controller":"App\Controller\AssetController","tokenId":"1"},"request_uri":"http://bulltest-wy44t.ondigitalocean.app/asset/1.png","method":"GET"},"level":200,"level_name":"INFO","channel":"request","datetime":"2022-04-19T13:42:02.559410+00:00","extra":{}} [metadata-provider] [2022-04-19 13:42:02] {"message":"Checking for authenticator support.","context":{"firewall_name":"main","authenticators":0},"level":100,"level_name":"DEBUG","channel":"security","datetime":"2022-04-19T13:42:02.559719+00:00","extra":{}} [metadata-provider] [2022-04-19 13:42:02] {"message":"Uncaught PHP Exception Aws\S3\Exception\S3Exception: \"Error executing \"GetObject\" on \"https://bulltest.nyc3.digitaloceanspaces.com/assets/1.png\"; AWS HTTP error: Client error: GET https://bulltest.nyc3.digitaloceanspaces.com/assets/1.png resulted in a 404 Not Found response:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>NoSuchKeybulltesttx0000000 (truncated...)\n NoSuchKey (client): - <?xml version=\"1.0\" encoding=\"UTF-8\"?>NoSuchKeybulltesttx00000000000002bbfba8e-00625ebc2a-2fd801a6-nyc3c2fd801a6-nyc3c-nyc3-zg03\" at /workspace/vendor/aws/aws-sdk-php/src/WrappedHttpHandler.php line 195","context":{"exception":{"class":"Aws\S3\Exception\S3Exception","message":"Error executing \"GetObject\" on \"https://bulltest.nyc3.digitaloceanspaces.com/assets/1.png\"; AWS HTTP error: Client error: GET https://bulltest.nyc3.digitaloceanspaces.com/assets/1.png resulted in a 404 Not Found response:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>NoSuchKeybulltesttx0000000 (truncated...)\n NoSuchKey (client): - <?xml version=\"1.0\" encoding=\"UTF-8\"?>NoSuchKeybulltesttx00000000000002bbfba8e-00625ebc2a-2fd801a6-nyc3c2fd801a6-nyc3c-nyc3-zg03","code":0,"file":"/workspace/vendor/aws/aws-sdk-php/src/WrappedHttpHandler.php:195","previous":{"class":"GuzzleHttp\Exception\ClientException","message":"Client error: GET https://bulltest.nyc3.digitaloceanspaces.com/assets/1.png resulted in a 404 Not Found response:\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>NoSuchKeybulltesttx0000000 (truncated...)\n","code":404,"file":"/workspace/vendor/guzzlehttp/guzzle/src/Exception/RequestException.php:113"}}},"level":500,"level_name":"CRITICAL","channel":"request","datetime":"2022-04-19T13:42:02.599137+00:00","extra":{}} [metadata-provider] [2022-04-19 13:42:02] 10.244.3.189 - - [19/Apr/2022:13:42:02 +0000] "GET /asset/1.png HTTP/1.1" 500 831 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/100.0.4896.88 Safari/537.36

andreleo6 commented 2 years ago

Solved it. I had the folder "assets" wrongly spelled as "asset". Just had to rename to "assets"