Dear Nathan,
Today I worked on reaching your containerized Azure server. I learned that we had probably not set up the .env file correctly, and that it should should be in the "front-end" package, and that we need to rebuild VITE. However, we have fixed all of those problems, and have verified in the debugger that the URL which you specified (the blackdune one) is correctly configured. However, it times out. We constructed the curl command below as a test, which also times out. Not that we can reach the URL on port 443 (not 8001), and it gives a valid response, and it answers a ping, so we know that the container is "up" and reacheable.
I hope you can tell us what we are doing wrong. Ideally you would run our code, but if you can just tell us how to get a working "post" the the ohm-match (which is what our code has successefully used in the past) with curl, I can probably take it from there.
Note I am nervous about if we should be using port 443 or port 8001 for this. You said 8001, but it answers 443.
robertread@Robs-MacBook-Pro-418 front-end % curl -X POST https://openhardwaremanager.blackdune-e38fce01.westus3.azurecontainerapps.io:8001 -H "Accept: 'application/json', 'Content-Type': 'application/json'" -d '{"okh_url":"https://projdatablobstorage.blob.core.windows.net/okh/okh-quaker-oats-oatmeal-recipe.json"}'
curl: (28) Failed to connect to openhardwaremanager.blackdune-e38fce01.westus3.azurecontainerapps.io port 8001 after 75004 ms: Couldn't connect to server
robertread@Robs-MacBook-Pro-418 front-end %
Dear Nathan,
Today I worked on reaching your containerized Azure server. I learned that we had probably not set up the .env file correctly, and that it should should be in the "front-end" package, and that we need to rebuild VITE. However, we have fixed all of those problems, and have verified in the debugger that the URL which you specified (the blackdune one) is correctly configured. However, it times out. We constructed the curl command below as a test, which also times out. Not that we can reach the URL on port 443 (not 8001), and it gives a valid response, and it answers a ping, so we know that the container is "up" and reacheable.
I hope you can tell us what we are doing wrong. Ideally you would run our code, but if you can just tell us how to get a working "post" the the ohm-match (which is what our code has successefully used in the past) with curl, I can probably take it from there.
Note I am nervous about if we should be using port 443 or port 8001 for this. You said 8001, but it answers 443.