-
Notifications
You must be signed in to change notification settings - Fork 193
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
[HELP] Is it possible to access gRPC as vdir #381
Comments
@johnny15243 I guess gRPC service you are running do not support vdir or have an invalid base URL (or similar) setting. To be exact, vdir rule share the same reverse proxy router object as proxy rules but with automatic rewrites on the path name. Zoraxy will rewrite the hostname automatically on vdir requests (i.e. yourdomain.com/vdir/myresources -> upstream_ip:port/myresources), in this case, I guess there is a misconfiguration in your upstream gRPC server or your gRPC server do not support such path rewrite. |
@tobychui Thanks for the response :-) First. The path rewrite is no problem. If i add the path to the proxy target, it appends it. {
"MatchingPath": "/api/",
"Domain": "127.0.0.1:33073/api/",
"RequireTLS": false,
"SkipCertValidations": false,
"Disabled": false
}, To day i scanned the packets via tcpdump.
I recognized that the request is done via h2 (http2 with tls). Here is a caddy.conf-sample for netbird.
|
@johnny15243 any update on this? I really want to try netbird with zoraxy |
Yes. I was able to bring it up running.
After copying and mounting the certificate you have to tell the netbird containers a few commands. Later this day I'll paste my netbird docker-compose file and a instruction. |
@faud Here ist my Konfiguration:
I hope it may helps you. |
What happened?
I tried to get Netbird running.
I started with the advanced installation.
After configuring the vdir for proxy, have the following errors
If i use the vdir as proxy target, and call uri. No errors appear
Here is my Configuration
Describe the networking setup you are using
Here are some example, commonly asked questions from our maintainers:
Additional context
Add any other context or screenshots about the feature request here.
The following uri-Path are gRPC-Services and normally called via h2c [http2] within caddy
/management.ManagementService/
and
/signalexchange.SignalExchange/
The text was updated successfully, but these errors were encountered: