Skip to content
This repository has been archived by the owner on Nov 29, 2023. It is now read-only.

Server with caddy reverse proxy: proto: cannot parse invalid wire-format data #27

Open
cocodrino opened this issue Feb 4, 2021 · 4 comments

Comments

@cocodrino
Copy link

Hi guys, I'm trying to run tempest along with legato, both are running with caddy, my caddy file is

:2015 {
  root ./dist

  try_files {path} /index.html

  file_server
}

:2290 {
  reverse_proxy http://127.0.0.1:2289
}

because I'm using IP I had to replace all request from HTTPS to HTTP in the VUEJS files 😓 but now when I run and enter in the server I get this error in legato

 Server with caddy reverse proxy:  proto: cannot parse invalid wire-format data

I suspect that the caddy server is affecting the request, do you know if effectively this is the problem and how can I resolve it?

thank you so much

@bluskript
Copy link
Member

Tempest has not migrated to hRPC yet, which is why the wire format is broken. We're in the middle of restructuring the protocol, so it'll take some time to migrate.

@cocodrino
Copy link
Author

oh thanks @bluskript , I'm not very familiarized with RPC/hRPC...that is, caddy is not available to handle the requests because it's not HTTP and I must avoid use it to reverse proxy?...or is this not related to caddy and the reverse proxy? thanks

@pontaoski
Copy link
Member

oh thanks @bluskript , I'm not very familiarized with RPC/hRPC...that is, caddy is not available to handle the requests because it's not HTTP and I must avoid use it to reverse proxy?...or is this not related to caddy and the reverse proxy? thanks

The error is coming from legato because the client is using an old format which legato no longer understands, hence invalid wire-format data error

@bluskript
Copy link
Member

if you would like to test with old legato, this commit is the last one before the rewrite.

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

No branches or pull requests

3 participants