# Well That's weird.. grpc problem a bug!
**URL:** https://openziti.discourse.group/t/well-thats-weird-grpc-problem-a-bug/4003
**Category:** zrok
**Created:** [February 20, 2025, 5:20pm UTC](https://openziti.discourse.group/t/well-thats-weird-grpc-problem-a-bug/4003 "2025-02-20T17:20:04Z")
**Posts on this page:** 5
**Page:** 1
### Author:  [@zzz](https://openziti.discourse.group/u/zzz)
#### Post date: [February 20, 2025, 5:20pm UTC](https://openziti.discourse.group/t/well-thats-weird-grpc-problem-a-bug/4003/1 "2025-02-20T17:20:04Z")
Sorry im just new to zrok and stuff
So i got my local server setup and everything cool until im using HTTP/2
I mean yall handle it pretty well but i don't know why the moment i put the header
"content-type: application/grpc" while using HTTP/2
oh yall get mad at me for some reason and give me error 464 with an empy response body
once i remove application/grpc everything works fine more than fine once i put it back yall dont like that why is that!!
Plus this never happen with HTTP/1 at all i can mess with grpc as much as i want.. but why not on HTTP/2
I'm so confused !!!
---
### Author:  [@michael.quigley](https://openziti.discourse.group/u/michael.quigley)
#### Post date: [February 20, 2025, 5:41pm UTC](https://openziti.discourse.group/t/well-thats-weird-grpc-problem-a-bug/4003/2 "2025-02-20T17:41:34Z")
Production zrok is hosted in AWS behind an AWS load balancer:
[https://http.dev/464](https://http.dev/464)
> HTTP response status code 464 Incompatible protocol is an unofficial client error specific to _AWS Elastic Load Balancer_ and used to indicate that the load balancer received an incompatible HTTP request protocol.
---
### Author:  [@zzz](https://openziti.discourse.group/u/zzz)
#### Post date: [February 20, 2025, 5:46pm UTC](https://openziti.discourse.group/t/well-thats-weird-grpc-problem-a-bug/4003/3 "2025-02-20T17:46:31Z")
is there is anything i can do at this point.. or i just unable to use grpc on HTTP/2
should i just stick with HTTP/1
is this gonna be fixed in the future or what gonna happen !!
---
### Author:  [@mguthrie88](https://openziti.discourse.group/u/mguthrie88)
#### Post date: [February 20, 2025, 6:15pm UTC](https://openziti.discourse.group/t/well-thats-weird-grpc-problem-a-bug/4003/4 "2025-02-20T18:15:51Z")
If it works with HTTP/1 then I would just stick with that. There are limitations within AWS that will prevent the use of some GRPC functionality when using HTTP/2 protocol. You could also look at using a private share, which might give you more control for what you need.
---
### Author:  [@zzz](https://openziti.discourse.group/u/zzz)
#### Post date: [February 20, 2025, 6:24pm UTC](https://openziti.discourse.group/t/well-thats-weird-grpc-problem-a-bug/4003/5 "2025-02-20T18:24:14Z")
ive been using it on private share for test then got to use it on public one cause i need trusted SSL cert connection cause that's the my whole purpose of this, guess my only way now is by using a custom domain and going through a lot of setup stuff, i wished this could've worked well