search

oceanprotocol / provider

REST API for provider of data services
Apache License 2.0
28 stars 38 forks source link

Unable to purchase computed data with mumbai testnet due to Invalid signature error #648

Closed mariacarmina closed 1 year ago

mariacarmina commented 1 year ago

Describe the bug Getting an 400 bad request when trying to purchase an compute only data set, published from the different account , from different browser. Using mumbai testnet. Algorithms , dataset refered from here ocean.py tutorial. This issue is reported from Discord.

To Reproduce Steps to reproduce the behavior:

  1. Go to ocean.py/READMEs/c2d-flow.md
  2. Publish the dataset and the algorithm assets
  3. Open Ocean Market in the browser and search for published assets.
  4. Try to purchase service and see the error

Expected behavior To purchase the services without problems.

Screenshots image

ocean_lib.exceptions.DataProviderException: Failed to get a response for request:
computeStartEndpoint=https://v4.provider.mumbai.oceanprotocol.com/api/services/compute, payload={'dataset':
{'documentId': 'did:op:443a22ebed56b9c846dafb751e4cef47b1869d77d1535a9865175b27b3c7adcd',
'serviceId': '1', 'transferTxId': '0x56024d9c2c1d2d3b3021f21dcc5cf6c544914d8fa6ddb371be7b2232f5f99918'},
'environment': 'compute-v4-engine-dev', 'algorithm': {'documentId':
'did:op:09aa3f5235ed3170baa2eb5cacb8c64068ac444f29209cf792637eea98fde198', 'serviceId': '0', 'transferTxId':
'0x17dc3e5510e5786fc2fec1aa988017de1926cee8909d085f2f91df61471f6096'}, 'signature':
'0xa657ac434840374f19dbd4c9bb60d1683dcab17663c24bcf36069ede3d3804e475430178b9ca44a62c08e653280f31a8f738e479ca9d88c016960c492f93d7ff01', 'nonce': '1687177454529.354', 'consumerAddress':
'0x0b600C9d669241453A449f766fF49b5CC50eDD54', 'additionalInputs': []},
response is b'<html>\r\n<head><title>502 Bad Gateway</title></head>\r\n<body>\r\n<center><h1>502 Bad Gateway</h1></center>\r\n<hr><center>nginx</center>\r\n</body>\r\n</html>\r\n'
mariacarmina commented 1 year ago

The nonce from payload is equal to the one from provider's database and a restart of the pod didn't change anything.