smee-client icon indicating copy to clipboard operation
smee-client copied to clipboard

🔴 Receives payloads then sends them to your local server

Results 30 smee-client issues
Sort by recently updated
recently updated
newest added

If server and client are connected and the server changes its ip address (seems to happen in AWS kubernetes quite often), than the client still thinks its connected but does...

Currently client pases original "Host" header coming from request. This way kubernetes ingress can't dispatch call to respective service. Host header should come from target hostname and original Host could...

wontfix

Currently, the text provided after the Smee token in a request is appended to the path given in the `-P/--path` option. This is working fine for us so far to...

My smee client is started as a system process, and works OK for some time, a few hours, and then it seems like the process is "ready", but notifications aren't...

I am using smee URL to trigger push events from bitbucket to Jenkins. Using smee client in Jenkins as sidecar conteiner. Please check below code: - name: smee-bitbucket image: docker.io/oveits/smee-client:latest...

I was using smee for a year but from a last week I'm getting error: Event { type: 'error', message: 'certificate has expired' } Smee as service is started with...

Hi, first of all thanks for the support. We are using smee.io service/client to communicate github events with our internal Jenkins instance (nothing new here). We upgraded [smee-client npm library](https://www.npmjs.com/package/smee-client)...

In order to avoid to keep the terminal open and to have multiple paths listening. I was wondering if you can implement a -d option to keep run and listening...

Hello Everybody, I am trying to operate SMEE on a server behind a proxy and I was getting connection timeout errors when I intput the following: smee -u SMEE-link  -p...

Anyone seen this issue? ``` { Error: Internal Server Error at Request.callback (/home/docker/.nvm/v10.15.3/lib/node_modules/smee-client/node_modules/superagent/lib/node/index.js:706:15) at Stream.parser (/home/docker/.nvm/v10.15.3/lib/node_modules/smee-client/node_modules/superagent/lib/node/index.js:916:18) at Stream.emit (events.js:189:13) at Unzip.unzip.on (/home/docker/.nvm/v10.15.3/lib/node_modules/smee-client/node_modules/superagent/lib/node/unzip.js:55:12) at Unzip.emit (events.js:194:15) at endReadableNT (_stream_readable.js:1125:12) at process._tickCallback...

bug