OCI API Gateway scenarios with 'No Such File or Directory' scenarios During Backend Connection Setup
I need help solving I'm following best practices but I've been researching this but I'm trying to figure out I'm working on a personal project and Quick question that's been bugging me - I'm trying to set up an API Gateway in Oracle Cloud Infrastructure (OCI) to connect to my backend service hosted on a Compute Instance... I have configured the API Gateway with the correct backend URL, but when I attempt to test the API, I receive a `No such file or directory` behavior. Here’s the setup I have: - **API Gateway Version**: 2.1.0 - **Backend Type**: HTTP - **Backend URL**: `http://<instance-ip>:<port>` I've ensured that the Compute Instance is running and accessible from the public internet. I can access the backend service directly using the same URL in a browser. The following is a snippet of my API Gateway configuration: ```json { "id": "my-api-gateway", "routes": [ { "route": "/my-service", "backend": { "url": "http://<instance-ip>:<port>", "timeout": 5000 } } ] } ``` When I test the API through OCI's console, the response shows this behavior log: ``` behavior: Backend connection failed: No such file or directory ``` I've also checked the network security settings and ensured that the appropriate ingress rules are set in the instance’s security list to allow traffic on the specified port. I’ve tried accessing the backend from a different environment and it works perfectly. Additionally, I have verified the API Gateway's settings multiple times, but I still get the same behavior. Does anyone have an idea of what could be wrong or how to troubleshoot this further? For context: I'm using Json on macOS. What are your experiences with this? Any ideas how to fix this? This is part of a larger mobile app I'm building. Thanks, I really appreciate it! I'm working in a Windows 10 environment. Thanks for taking the time to read this!