You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 4, 2019. It is now read-only.
This maybe an issue with the Starter Plan instance and it's related infrastructure(including documentation) and it might not have anything to do with the Vehicle Manufacture network. Since it is not clear how to file issues against the Starter Plan, I am just using this repo to file this issue.
Following the instructions here to manually deploy Vehicle Manufacture network to the Starter Plan instance, when I finally arrive at Step 3.4 to synchronize the certs using the API call:
Note that I got {"message":"ok"} for the earlier steps. It was extremely painful to figure out the exact strings to replace the placeholder tokens in the curl commands but I managed to use the logs and figure it out.
The text was updated successfully, but these errors were encountered:
@caroline-church -- Yes. However, I am now using the UI as described in this blog to sync the certificate. It's so much easier than doing it from the command-line using curl.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
This maybe an issue with the
Starter Plan
instance and it's related infrastructure(including documentation) and it might not have anything to do with theVehicle Manufacture
network. Since it is not clear how to file issues against theStarter Plan
, I am just using this repo to file this issue.Following the instructions here to manually deploy
Vehicle Manufacture
network to theStarter Plan
instance, when I finally arrive at Step 3.4 to synchronize the certs using the API call:it results in
{"error":"route not found"}
.Note that I got
{"message":"ok"}
for the earlier steps. It was extremely painful to figure out the exact strings to replace the placeholder tokens in thecurl
commands but I managed to use the logs and figure it out.The text was updated successfully, but these errors were encountered: