issues
search
MDSLab
/
wstun
Tunnels and reverse tunnels over WebSocket
Apache License 2.0
114
stars
44
forks
source link
issues
Newest
Newest
Most commented
Recently updated
Oldest
Least commented
Least recently updated
Expose a local server behind NAT to internet
#25
snimavat
opened
4 months ago
1
Please add HTTP headers injection & proxy support :D
#23
medram
opened
1 year ago
0
Allowlist version
#22
npeditto
closed
2 years ago
0
Error log4js is not defined
#21
yuanfeibi
opened
3 years ago
3
npm install error
#20
deepakkoirala
opened
4 years ago
2
Usage on Heroku
#19
thisismydesign
closed
4 years ago
1
Updating websocket to release v1.0.31 to allow compatibility with latest Node.JS releases
#18
artynet
closed
4 years ago
0
fix: memory leaks due to event listeners
#17
flongo82
closed
5 years ago
0
Error: read ECONNRESET
#16
npeditto
opened
5 years ago
0
Fix (occasional) message lost on reverse tunnel client
#15
Leemoonsoo
closed
5 years ago
0
Use on existing server
#14
manix
closed
5 years ago
4
Feature Request-> add additional path information to websocket
#13
sdellutri
opened
5 years ago
0
TypeError: this._reject is not a function
#12
mrvic
closed
6 years ago
1
client-reverse-wstunnel with http proxy
#11
pankajbhagra
opened
7 years ago
1
Reverse Client+Server Pair - Server Crashing
#10
t3chguy
closed
6 years ago
3
Can this work as a load balancer?
#9
jimmywarting
closed
8 years ago
1
Add ws_open ws_close hooks
#8
merlin-p
closed
8 years ago
0
Unable to bind server to a specific IP
#7
qub
closed
8 years ago
2
New stable version 0.1.2
#6
alotronto
closed
9 years ago
0
Arrange for node module
#5
alotronto
closed
9 years ago
0
Multiple client on server
#4
alotronto
closed
9 years ago
0
Only one client is managed by reverse wstunnel server
#3
alotronto
closed
9 years ago
2
Reverse wstunnel
#2
alotronto
closed
9 years ago
0
On reverse tunnel the problem of managing multiple conncetions TCP on server at the same time, using id for TCP connections.
#1
alotronto
closed
9 years ago
0