PipedreamHQ
[BUG] 403 error when using pre-built Bybit actions
Describe the bug A clear and concise description of what the bug is. Since the 28th of February I have been getting a 403 error when using the pre-built Bybit actions.
To Reproduce Steps to reproduce the behavior:
- Go to 'workflows' and select 'New' to add a new workflow
- Click on 'add trigger' and choose one
- Click on 'add a step' and select a pre-defined Bybit action, for example 'generic_wallet_balance'
- See error
Expected behavior A clear and concise description of what you expected to happen.
Error log Error - Request failed with status code 403 ""-//W3C//DTD HTML 4.01 Transitional//EN\" \"[http://www.w3.org/TR/html4/loose.dtd\">\n<HTML><HEAD><META](http://www.w3.org/TR/html4/loose.dtd/%22%3E/n%3CHTML%3E%3CHEAD%3E%3CMETA) HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">\n<TITLE>ERROR: The request could not be satisfied</TITLE>\n</HEAD><BODY>\n<H1>403 ERROR</H1>\n<H2>The request could not be satisfied.</H2>\n<HR noshade size="1px">\nBad request.\nWe can't connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner.\n<BR clear="all">\nIf you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation.\n<BR clear="all">\n<HR noshade size="1px">\n<PRE>\nGenerated by cloudfront (CloudFront)\nRequest ID: rU4108pIUVZa4M2V27t7uqfA1GtBWq7aZhd89cj7qewni3FUVIpxIw==\n</PRE>\n<ADDRESS>\n</ADDRESS>\n</BODY></HTML>" DETAILS at null.createError (/tmp/pdg/dist/code/66230d0253dc7564420f0162c6eb9942b9dab4ce88291bcb7b2bba9c05fb5238/node_modules/.pnpm/[email protected]/node_modules/axios/lib/core/createError.js:16:15) at null.settle (/tmp/pdg/dist/code/66230d0253dc7564420f0162c6eb9942b9dab4ce88291bcb7b2bba9c05fb5238/node_modules/.pnpm/[email protected]/node_modules/axios/lib/core/settle.js:17:12) at IncomingMessage.handleStreamEnd (/tmp/pdg/dist/code/66230d0253dc7564420f0162c6eb9942b9dab4ce88291bcb7b2bba9c05fb5238/node_modules/.pnpm/[email protected]/node_modules/axios/lib/adapters/http.js:269:11) at IncomingMessage.emit (events.js:412:35) at null.endReadableNT (internal/streams/readable.js:1333:12) at process.processTicksAndRejections (internal/process/task_queues.js:82:21)
Desktop (please complete the following information):
- OS: On both MacOS Monterey 12.6.1 and Windows
- Browser: Chrome, Safari
Hello @Menacing-Salt, I can reproduce this issue. I'll add this to Pipedream prioritized backlog
When tried to setup Google Two-Factor Authentication by sending the verification code to the email, I got
-200: TypeError: Failed to fetch
So I was not able to get the authentication in order to create an API Key! Blocked!
I am suffering the same error and would like to add some info that could be worth:
Describe the bug
All the API calls to Bybit using a GET method return a 403 error (attached below). This happens with all of them. For instance:
-
The
generic_market_symbols: this action does not allow any configuration, so it is not possible to mess it up. It should work as it is. -
generic_api_call: I can use this to create GET requests that fit the API format required by Bybit. I have tried it to make work all the other Bybit actions that returned error, but still got the same, despite making sure they comply with it.
All the POST methods work fine. It is only a GET problem. Therefore, it is not an IP problem, as it was confirmed to me by Bybit support. They mentioned these three possible causes for such an error:
- Don't send anything in body for the GET requests.
- GET requests should be in query string format
- Make sure the method names are in uppercase (GET)
the last two ones can be discarded, as I made sure that was not the case. So it seems the GET request needs to have some body in it as far as I can understand, though there is no possibility to amend that in the pipedream workflow interface.
Here is the link to the Bybit API error codes explained, which further confirms my idea:
https://bybit-exchange.github.io/docs/v5/error#:~:text=403,empty%20json%20body
I also found a stack overflow thread already talking about this issue on a similar case:
https://stackoverflow.com/questions/978061/http-get-with-request-body
This is my understanding of the case. However, my knowledge is limited and I could be getting something wrong.
@jcortes I was this close 🤏to restart onboarding Bybit because I didn't saw in the app store. Must be "admin only" right now because of this bug and #10799.
That said, I was able to create a ByBit account and went through properly 2FA, in case you want to resume tackling this issue. (Both 2DA and api key + secret are in 1PW).
We can't support ByBit app beause it has the USA as a restricted country of operation.
Currently ByBit does not support connections from certain restricted countries, included the United States. This appears in their services agreement:
As stated in Section 11.3 of the [Service Agreement](https://www.bybit.com/help-center/s/article/Bybit-Terms-of-Service), Bybit does not offer services or products to Users in a few excluded jurisdictions including the United States, the Chinese Mainland, Hong Kong, Singapore, Canada (...)