Get refused connecting to the toolbench server
Opened this issue · 6 comments
Hi, I'm getting an error connecting to the server after running some tests. Is there a way I can solve this problem?
requests.exceptions.ConnectionError: HTTPConnectionPool(host='39.105.143.28', port=8080): Max retries exceeded with url: /rapidapi (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f54f6b8b350>: Failed to establish a new connection: [Errno 111] Connection refused'))
Hello, it is running normally now, you can try again
Hello, it is running normally now, you can try again
@sailaoda Thanks for the attention! However, I still get the same error ("ConnectionError") after several "ReadTimeout" errors when I try the new server IP released yesterday.
requests.exceptions.ReadTimeout: HTTPConnectionPool(host='47.99.174.162', port=8080): Read timed out. (read timeout=300)
To reproduce:
import requests
service_url = "http://47.99.174.162:8080/rapidapi"
payload = {'category': 'Mapping', 'tool_name': 'dargan', 'api_name': 'in_radius', 'tool_input': '{\n "postcode": "CF103NP",\n "radius": 2\n}', 'strip': 'truncate', 'toolbench_key': <toolbench_key>}
headers = {"toolbench_key": <toolbench_key>}
response = requests.post(service_url, json=payload, headers=headers, timeout=15)
Thanks.
Hello, you can use the latest host 8.130.32.149, which is the server we will maintain for a long time in the future. Please feel free to contact us if you have any questions, thank you
Hi @sailaoda , I believe the same issue is occurring again even with the 8.130.32.149 URL, has the server URL been changed?
Hello @YashThirani21 , there are very few tools that do report errors, you can try this command to see if the service responds. curl -X POST http://8.130.32.149:8080/rapidapi \ -H "Content-Type: application/json" \ -H "toolbench_key: YOUR_ACTUAL_TOOLBENCH_KEY" \ -d '{ "category": "Business", "tool_name": "CalAPI", "api_name": "AddNumbers", "tool_input": "{\"vala\":0,\"valb\":-1}", "strip": "truncate", "toolbench_key": "YOUR_ACTUAL_TOOLBENCH_KEY" }'
Thanks for the tip @sailaoda , in a specific example I was working with, it turned out to be a JSON formatting issue in the request body. But fixing that just led me to the familiar problem of "Unsubscribed error...". Could you shed some light on why that might still be occurring?