Page 1 of 2

Port INPUT and OUTPUT

Posted: Fri Dec 18, 2015 6:31 pm
by Deireadh
Hi. VESTACP by default blocking all port... only added to panel firewall they are received. How is the OUTPUT ports? or they are blocked?

Re: Port INPUT and OUTPUT

Posted: Fri Dec 18, 2015 7:38 pm
by skurudo
Nope, output not blocked

Re: Port INPUT and OUTPUT

Posted: Sat Dec 19, 2015 4:17 pm
by Deireadh
skurudo wrote:Nope, output not blocked
I do not know why VESTA blocks musicbot and client teamspeak: https://forum.sinusbot.com/threads/ts-c ... stacp.910/

Re: Port INPUT and OUTPUT

Posted: Sat Dec 19, 2015 4:42 pm
by skurudo
Open ports for teamspeak and use docs from software do you plan use...
These are the default ports used by TeamSpeak 3:

Default voice port (UDP in): 9987
Default filetransfer port (TCP in): 30033
Default serverquery port (TCP in): 10011
Default tsdns port (TCP in): 41144
Default weblist port (UDP out): 2011-2110 (first available port in given range)

In addition to that, packets originating from or sent to accounting.teamspeak.com:2008 (TCP) and weblist.teamspeak.com:2010 (UDP) must not be blocked. The local port for these connections is randomly assigned by the operating system when the connection is established. Please note that we do not guarantee that these DNS names will resolve to the same IP Address at any point in time. These services have changed IP addresses in the past and will continue to do so in the future.
Original - https://sku.su/YztFn

Re: Port INPUT and OUTPUT

Posted: Sat Dec 19, 2015 4:43 pm
by skurudo
Deireadh wrote: I do not know why VESTA blocks musicbot and client teamspeak
You admin on your server, you can do whatever you want. VestaCP is just a tool to help you. Remember. ;-)

Re: Port INPUT and OUTPUT

Posted: Sat Dec 19, 2015 5:23 pm
by Deireadh
skurudo wrote:Open ports for teamspeak and use docs from software do you plan use...
These are the default ports used by TeamSpeak 3:

Default voice port (UDP in): 9987
Default filetransfer port (TCP in): 30033
Default serverquery port (TCP in): 10011
Default tsdns port (TCP in): 41144
Default weblist port (UDP out): 2011-2110 (first available port in given range)

In addition to that, packets originating from or sent to accounting.teamspeak.com:2008 (TCP) and weblist.teamspeak.com:2010 (UDP) must not be blocked. The local port for these connections is randomly assigned by the operating system when the connection is established. Please note that we do not guarantee that these DNS names will resolve to the same IP Address at any point in time. These services have changed IP addresses in the past and will continue to do so in the future.
Original - https://sku.su/YztFn
I added all recommended ports TeamSpeak to firewalls and it did not help :/

http://prntscr.com/9g3mmg
http://prntscr.com/9g3mqt

qt.network.ssl: QSslSocket: cannot resolve SSLv2_client_method
qt.network.ssl: QSslSocket: cannot resolve SSLv2_server_method
2015-12-19 17:22:08.714750|INFO |Update | |Check license version: 1
2015-12-19 17:22:08.717004|INFO |LicenseViewer | |License language: en
2015-12-19 17:22:08.717539|INFO |LicenseViewer | |Found cached license for version 1 and language en
2015-12-19 17:22:09.145760|INFO |Newsticker | |Newsticker next check: Sat Dec 19 18:45:20 2015
2015-12-19 17:22:13.245827|INFO |ClientUI | |Blacklist check timeout
2015-12-19 17:22:13.589625|INFO |ClientUI |1 |Connect status: Disconnected
2015-12-19 17:22:13.590907|INFO |ClientUI |1 |Failed to connect to server, want autoreconnect = 0

Re: Port INPUT and OUTPUT

Posted: Sat Dec 19, 2015 5:36 pm
by Deireadh
BOT worked ... after installation VESTACP stopped working, so VESTA blocking something, but what?

Re: Port INPUT and OUTPUT

Posted: Sat Dec 19, 2015 6:11 pm
by skurudo
Deireadh wrote:BOT worked ... after installation VESTACP stopped working, so VESTA blocking something, but what?
Check input ports - TCP/UDP

Re: Port INPUT and OUTPUT

Posted: Sat Dec 19, 2015 6:13 pm
by skurudo
You can try to disable firewall and check again.

Re: Port INPUT and OUTPUT

Posted: Sat Dec 19, 2015 6:19 pm
by Deireadh
skurudo wrote:You can try to disable firewall and check again.
How to disable firewall?