[NodeJS] TeamSpeak 3 Proxy - Create your own TS3-Proxy Website (like ts3cloud)!

[UnlimitedBytes]

​

Today i want to release, the TS3-Proxy System. Which is a powerful, open source, proxy system for teamspeak 3servers and licensed under the MIT License. It’s based on simplicity and power. Extend the functionality at your own with a few simple Javascript lines.

Prerequisites

• NodeJS
• NPM

Features

• Easy to set up with detailed instructions.
• Also works with domains and SRV records.
• Self-developed design.

How to get it

Just go to the Github Project Page:​

UnlimitedBytes/ts3proxy

Contribute to UnlimitedBytes/ts3proxy development by creating an account on GitHub.

github.com

​

Working Live Demo

TS3 Proxy

​

Screenshot

​

Spoiler

​

​

​

 

[kingston]

Glad to be the first one to comment on this extremely interesting contribution. I was coding something similar in the past, will be very happy to look into your code. Thanks a lot!

 

[djalmasi]

Ohh man. You really amazing. Its work

 

[Ondra3211]

Where I can see list of all used ports?

 

[KuraPL]

[email protected] start /home/ts3proxy/ts3proxy
NODE_ENV=production node index.js

sh: 1: node: not found

npm ERR! [email protected] start: NODE_ENV=production node index.js
npm ERR! Exit status 127
npm ERR!
npm ERR! Failed at the [email protected] start script.
npm ERR! This is most likely a problem with the ts3proxy package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! NODE_ENV=production node index.js
npm ERR! You can get their info via:
npm ERR! npm owner ls ts3proxy
npm ERR! There is likely additional logging output above.
npm ERR! System Linux 3.16.0-4-amd64
npm ERR! command "/usr/bin/nodejs" "/usr/bin/npm" "start"
npm ERR! cwd /home/ts3proxy/ts3proxy
npm ERR! node -v v0.10.29
npm ERR! npm -v 1.4.21
npm ERR! code ELIFECYCLE
npm WARN This failure might be due to the use of legacy binary "node"
npm WARN For further explanations, please read
/usr/share/doc/nodejs/README.Debian

npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! /home/ts3proxy/ts3proxy/npm-debug.log
npm ERR! not ok code 0
ts3proxy@protalk:~/ts3proxy$ cd /home/ts3proxy/
ts3proxy@protalk:~$ npm start
npm ERR! Error: ENOENT, open '/home/ts3proxy/package.json'
npm ERR! If you need help, you may report this entire log,
npm ERR! including the npm and node versions, at:
npm ERR! <http://github.com/npm/npm/issues>

npm ERR! System Linux 3.16.0-4-amd64
npm ERR! command "/usr/bin/nodejs" "/usr/bin/npm" "start"
npm ERR! cwd /home/ts3proxy
npm ERR! node -v v0.10.29
npm ERR! npm -v 1.4.21
npm ERR! path /home/ts3proxy/package.json
npm ERR! code ENOENT
npm ERR! errno 34
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! /home/ts3proxy/npm-debug.log
npm ERR! not ok code 0

 

[DifferentUser]

This failure might be due to the use of legacy binary "node"

node -v v0.10.29

update your node version maybe?

npm install -g n
n stable

 

[djalmasi]

Where I can see list of all used ports?

At the config file.

 

[Ondra3211]

@djalmasi no... I mean when I create proxy IP 127.0.0.1:2564 Where is the IP saved? Is this saved in file?

 

[ewenjo]

@djalmasi no... I mean when I create proxy IP 127.0.0.1:2564 Where is the IP saved? Is this saved in file?

IPs are not being saved, they're just added as a proxy using the npm package udp-proxy. The ip is stored in memory

 

[PrivateStresser]

@djalmasi no... I mean when I create proxy IP 127.0.0.1:2564 Where is the IP saved? Is this saved in file?

There is currently no way to see this, but it should be implemented in the future in the Adminpanel. (Referring to the Issues)