Voyage II: Federating the monolith (Lesson 9: Reference Resolvers)

Help
,
1

After separating the accounts subgraph while I’m running the query provided in the ‘Testing our Changes’ it gives me the following error:
{
“data”: {
“listing”: null
},
“errors”: [
{
“message”: “HTTP fetch failed from ‘accounts’: HTTP fetch failed from ‘accounts’: error trying to connect: received corrupt message”,
“path”: [
“listing”,
“host”
],
“extensions”: {
“service”: “accounts”,
“reason”: “HTTP fetch failed from ‘accounts’: error trying to connect: received corrupt message”,
“code”: “SUBREQUEST_HTTP_ERROR”
}
},
{
“message”: “HTTP fetch failed from ‘accounts’: HTTP fetch failed from ‘accounts’: error trying to connect: received corrupt message”,
“path”: [
“listing”,
“reviews”,
“@”,
“author”
],
“extensions”: {
“service”: “accounts”,
“reason”: “HTTP fetch failed from ‘accounts’: error trying to connect: received corrupt message”,
“code”: “SUBREQUEST_HTTP_ERROR”
}
}
],
“extensions”: {
“valueCompletion”: [
{
“message”: “Cannot return null for non-nullable field Host.name”,
“path”: [
“listing”,
“host”
]
},
{
“message”: “Cannot return null for non-nullable field Listing.host”,
“path”: [
“listing”,
“host”
]
}
]
}
}

and on the router I’m getting this error:
Fetch error: HTTP fetch failed from ‘accounts’: HTTP fetch failed from ‘accounts’: error trying to connect: received corrupt message.

Please help me resolve this error. Thanks

2

Hi there @shubham ! Thanks for reaching out, and I’m sorry to hear that you’ve run into errors! This error in particular looks like something another learner was experiencing recently: here’s the post for reference. In their case, the routing-url for the accounts subgraph had been published with https rather than http. Could this perhaps be the source of the problem you’re seeing?

If not, please let me know - we can continue troubleshooting to get to the bottom of this!

Liz

3

Hey @lizhennessy Thank you so much. I was making the same mistake my accounts subgraph was using https in routing-url instead of http. I updated the routing-url and it’s working now I’m getting the data that was expected.

4

That’s fantastic to hear! :tada: So glad the issue’s been resolved. Happy coding!

1 Like