Getting the error while running in windows. for workload api (spiffe/error: Failed to watch the Workload API : rpc error: code = Unavailable desc = connection error: desc = "transport: Erro r while dialing: open \\.\pipe\backend-agent\public\api: The system cannot find the file specified.") about ghostunnel HOT 3 CLOSED

The error message indicates that Ghostunnel can't connect to the Workload API because the specified file exist. What steps have you taken to debug the issue? Have you checked that the file exists and the connection should be possible? If not, this doesn't look like a bug to me.

from ghostunnel.

the following attachment README file have the steps to follow to work the workloadpai. and one more doubt here file exist means, which file and in which location it will create. and it is pointing to the following path,
.\pipe\backend-agent\public\api. this means where the file will create, my project repo path is given below.
C:\Users\prasanth_allu\SPIRE\ghostunnel\docs\spiffe-workload-api-demo\windows
README.md

or

SPIFFE Workload API Support Demo
The following demonstrates using the SPIFFE Workload API to supply Ghostunnel with an X.509 identity and trusted CA roots that are used to facilite communication between a frontend and backend service.

Prerequisites
ghostunnel binary from Ghostunnel
spire-server and spire-agent binaries from SPIRE
socat
Architecture
There are several processes involved in the demo:

Frontend client that sends TCP data
Frontend Ghostunnel that receives TCP data forwards it to the backend Ghostunnel over SPIFFE-authenticated mutual TLS
Backend Ghostunnel that receives TCP data over SPIFFE-authenticated mutual TLS and forwards it to the backend server
Backend server that receives TCP data
Frontend SPIRE agent that identifies the frontend Ghostunnel and issues it a frontend SPIFFE identity
Backend SPIRE agent that identifies the backend Ghostunnel and issues it a backend SPIFFE identity
SPIRE server that mints the identities and delivers them to agents according to workload registration
TCP mTLS TCP
Frontend ------> Frontend Ghostunnel --------> Backend Ghostunnel ------> Backend
^ ^
| |
| |
Frontend SPIRE Agent Backend SPIRE Agent
^ ^
| |
+ +
\ /
\ /
+---- SPIRE Server ----+
Steps
Run SPIRE Server
$ ./01-run-spire-server.sh
Run Backend SPIRE Agent
$ ./02-run-backend-agent.sh
Run Frontend SPIRE Agent
$ ./03-run-frontend-agent.sh
Register Frontend and Backend Ghostunnel Workloads
$ ./04-register-ghostunnel-workloads.sh
Run Backend Ghostunnel
$ ./05-run-backend-ghostunnel.sh
Run Frontend Ghostunnel
$ ./06-run-frontend-ghostunnel.sh
Run Backend
$ ./07-run-backend.sh
Send the Frontend Request
Run the following the send a request from the frontend.

$ ./08-send-frontend-request.sh
You should see the backend print out a message!

from ghostunnel.

I'm not quite sure I understand what you're saying. But the README you're pointing to is for a demo, to explain how one might use Ghostunnel with their own deployment of SPIRE or a compatible system. Hence why it's in the "docs" folder. It was never intended to be used for a production deployment. I'm not surprised it doesn't run on Windows either, as it was written for Linux.

I don't think there's anything to fix here so I will close this issue.

from ghostunnel.