You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 29, 2023. It is now read-only.
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
The text was updated successfully, but these errors were encountered:
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.
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
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
Hi guys, I'm trying to run tempest along with legato, both are running with caddy, my caddy file is
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
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
The text was updated successfully, but these errors were encountered: