@Michelle_Mabuyo
This I’m getting in vscode terminal
{
“timestamp”: “2025-02-07T09:16:39.297310500Z”,
“level”: “ERROR”,
“trace_id”: “5a90e40eecf74fa7661873c458804174”,
“span_id”: “c6257965552d78f9”,
“fetch_error”: “hyper_util::client::legacy::Error(Connect, Custom { kind: Other, error: Custom { kind: InvalidData, error: InvalidCertificate(UnknownIssuer) } })”,
“target”: “apollo_router::services::http::service”,
“spans”: [
{
“http.route”: “/”,
“http.request.method”: “POST”,
“url.path”: “/”,
“client.name”: “”,
“client.version”: “”,
“name”: “router”
},
{
“name”: “supergraph”
},
{
“graphql.operation.type”: “query”,
“name”: “execution”
},
{
“apollo.subgraph.name”: “listings”,
“name”: “fetch”
},
{
“name”: “connect”
},
{
“net.peer.name”: “rt-airlock-services-listing.herokuapp.com”,
“net.peer.port”: “443”,
“http.route”: “/featured-listings”,
“http.url”: “https://rt-airlock-services-listing.herokuapp.com/featured-listings”,
“net.transport”: “ip_tcp”,
“name”: “http_request”
}
],
“resource”: {
“service.name”: “unknown_service:router-v2.0.0-preview.4.exe”,
“service.version”: “2.0.0-preview.4”,
“process.executable.name”: “router-v2.0.0-preview.4.exe”
}
}
This im gettin in localhost:4000 query hit
{
“data”: null,
“errors”: [
{
“message”: “HTTP fetch failed from ‘listings.v1’: invalid peer certificate: UnknownIssuer”,
“path”: [
“featuredListings”
],
“extensions”: {
“service”: “listings”,
“connector”: {
“coordinate”: “listings:Query.featuredListings@connect[0]”
},
“code”: “HTTP_CLIENT_ERROR”
}
}
]
}
Hi @Harshgaddam, I’ve re-categorized your post over to the “Other Apollo Topics” category that includes Odyssey tutorials, added tags and am tagging @Michelle_Mabuyo
Tags are a great way to make sure your post gets noticed.
Thanks
Hi @Harshgaddam! Hmm, can you confirm what GraphOS plan you’re on? You can find that under Settings → Billing.
When you ran rover dev, did you also include the APOLLO_KEY and APOLLO_GRAPH_REF values?
Hello @MichelleMabuyo
I have Enterprise Trail version and Role is Org Admin, and yes I did add APOLLO_KEY and APOLLO_GRAPH_REF
Error in localhost:4000 after I h
Error in vscode Terminal
{
"timestamp": "2025-02-07T09:16:39.297310500Z",
"level": "ERROR",
"trace_id": "5a90e40eecf74fa7661873c458804174",
"span_id": "c6257965552d78f9",
"fetch_error": "hyper_util::client::legacy::Error(Connect, Custom { kind: Other, error: Custom { kind: InvalidData, error: InvalidCertificate(UnknownIssuer) } })",
"target": "apollo_router::services::http::service",
"spans": [
{
"http.route": "/",
"http.request.method": "POST",
"url.path": "/",
"client.name": "",
"client.version": "",
"name": "router"
},
{
"name": "supergraph"
},
{
"graphql.operation.type": "query",
"name": "execution"
},
{
"apollo.subgraph.name": "listings",
"name": "fetch"
},
{
"name": "connect"
},
{
"net.peer.name": "rt-airlock-services-listing.herokuapp.com",
"net.peer.port": "443",
"http.route": "/featured-listings",
"http.url": "https://rt-airlock-services-listing.herokuapp.com/featured-listings",
"net.transport": "ip_tcp",
"name": "http_request"
}
],
"resource": {
"service.name": "unknown_service:router-v2.0.0-preview.4.exe",
"service.version": "2.0.0-preview.4",
"process.executable.name": "router-v2.0.0-preview.4.exe"
}
}
Thank you for the screenshots and information! One thing I noticed was the versioning, some were set to preview.0 and some are preview.4. Could you make sure they’re all set to the same? So in supergraph.yaml, and the router version when you run rover dev.
At the time of writing, the course was using preview.0, so it’s safest to stick with that for now. (We’re working on updates!)
Thank you for your quick response, I still see the Error
Hmm, just to confirm, you did include the lines for $env:APOLLO_KEY(and the other two environment variables) with the rover dev command?
Apologies for the back-and-forth on this, I don’t have Windows to try and reproduce on my end. One more thing to try: can you use a local folder instead of OneDrive? People have had issues with that in the past.
