-
Notifications
You must be signed in to change notification settings - Fork 33
Received invalid host specified
when connecting on RPC
#124
Comments
More info: Using:
and
I see in this commit of geth ethereum/go-ethereum@beabf95 that they are moving from using the params like How should k8s be configured? |
It seems like that's usually related to not having the rpcvhosts value, like you thought originally. Are you sure that the geth start command was updated successfully and ran with the new flags you added? Also, how are you connecting to the RPC endpoint? |
thanks @bmcd I'm 90% sure that the flags were applied as I did a |
@bmcd How is this supposed to be put in? this is what I have:
|
@bmcd Adding Here is the config:
I've tried variations below and more and have not had any success:
|
Hmm, not sure. When I use wizard to generate a qubernetes project it looks like:
There are no errors in the logs from when it crashes? |
hmm... The order seems to matter. This works:
our config also has that trailing I take it websockets are the same? |
it looks like that line is where qubernetes puts the Geth_Startup_Params value from the qubernetes.yaml file. So since it's empty in your config it just puts the \. You can delete that line. When you say it works, you mean it doesn't crash anymore? Or the rpc endpoint also no longer shows the invalid host error? websockets use the --wsorigins="*" flag instead of corsdomain and vhosts. |
Thanks! Nice to have it working a little. I'll close the issue. |
I got the error:
Error: Invalid JSON RPC response: "invalid host specified\n"
when trying to connect to the 8545 through a traefik IngressRoute.I tried adding:
to the deployment.yaml but did not work
The text was updated successfully, but these errors were encountered: