Closed XeroxDev closed 1 year ago
This is because sish supports setting an idle-timeout on a connection that hasn't written/read any data.
You can either increase the ping interval in your websocket app, increase the timeout duration, or disable this functionality entirely using:
--idle-connection Enable connection idle timeouts for reads and writes (default true)
--idle-connection-timeout duration Duration to wait for activity before closing a connection for all reads and writes (default 5s)
You likely will be fine with disabling this functionality (--idle-connection=false
)
That worked, thank you very much!
Keep up this awesome work and have a nice day.
Hey. I've a kinda "hacky" setup of sish and need a bit of help.
Setup
docker-compose.yml
id-sub.domain.tld.conf
Explaination
I know, this is not the best setup. I just tried to accomplish an nginx reverse proxy to sish. I don't need sish to create certs, because I've already a wildcard for it (with automatic refresh).
The reason why I disabled "https" in sish and use "sish http:80" was: It kept trying generating own and even after adding
It didn't worked and just threw errors. So I disabled it completely and make an normal http connection on the machine itself and it worked.
Issue
Connection etc works, but I've issues with web sockets...
I've a DotNet Blazor Server setup (which uses websockets / signalr) but after 5 secs of inactivity, the reconnect screen occurs
Client CLI says:
Server Logs are saying:
Maybe you know the issue? Or can help me setting it up correctly?
And thank you for the awesome work!
Btw. I've created a small powershell script which can be added to the users profile so the usage is a bit easier.
Usage: sish local-address subdomain (optional) Example:
sish localhost:5000 dpb