Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GraphQL error while sending payments #502

Closed
dasquantum2909 opened this issue Dec 29, 2022 · 2 comments
Closed

GraphQL error while sending payments #502

dasquantum2909 opened this issue Dec 29, 2022 · 2 comments

Comments

@dasquantum2909
Copy link

Describe the problem/bug
Whenever I try to send payments I am receiving graphql error

Your environment

  • Version of ThunderHub: 0.13.18
  • Deployment method: using umbrel bundled package
  • Other relevant environment details: RPI4, ubuntu, umbrel lightning node

To Reproduce
Steps to reproduce the behavior:

  1. Go to 'Home'
  2. Click on 'send'
  3. Provide invoice
  4. Select the out channels
  5. See error- Graphql error

Expected behavior
It should send the payment

Actual behavior
Throws graphql error
{"graphQLErrors":[],"clientErrors":[],"networkError":{"name":"ServerError","response":{},"statusCode":400,"result":{"errors":[{"message":"Variable \"$out\" got invalid value null at \"out[0]\"; Expected non-nullable type \"String!\" not to be null.","locations":[{"line":1,"column":52}],"extensions":{"code":"BAD_USER_INPUT"}}]}},"message":"Response not successful: Received status code 400"}

Screenshots/Links
If applicable, add screenshots or links to help explain your problem.
image

Additional context
Add any other context about the problem here.

@aphex3k
Copy link

aphex3k commented Jan 12, 2023

This is actually a network/server error instead of GraphQL if you look at the error message more closely. I described the same behavior in #508

@apotdevin
Copy link
Owner

Fixed with #531

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants