menesakdeniz
Member
Hi,
how can i be an official dealer for my country ?
how can i be an official dealer for my country ?
How to become official dealer?
- Thread starter menesakdeniz
- Start date
Write an E-Mail to [email protected] any apply.
@WolverinDEV, It would be interesting to have the prerequisites to become a reseller somewhere.
not an reseller, an hoster
@WolverinDEV, it would be interesting to have the prerequisites to become a hoster somewhere.
---- Automatically Merged Double Post ----
Adjusted.
---- Automatically Merged Double Post ----
Adjusted.
Last edited:
Really? Why not?
because we don't care, we are not your customers.
Because it is really obvious that as a official hoster you really need ddos protection
Hey,
first things first, a ddos protection is not the key to getting applied/approved as official hoster.
There are several things I'm looking for when receiving E-Mails:
1) Professionalism
This includes a proper texted E-Mail, why you want to become a hoster and what you're already offering.
Professionalism also includes the "to be informed" aspect. Does the applicant know what TeaSpeak is, has already some experiences and seems to be capable of hosting TeaSpeak servers for TeaSpeak / TeaWeb clients.
2) Authenticity
Does the applicant have an authentic web presence?
Fits his service all legal needs like an imprint, privacy policy etc
3) Look 'n Feel
This is a quite relative aspect, which mainly lies on my intuition.
Things which come into play are, how serious the applicant presents himself as well what his intuition about the appliance is.
An important point here is that he wants to promote and support TeaSpeak as well that he's informed about TeaSpeak itself.
Questions are allowed and welcomed and will not result in any kind of deny, but having no clue about TeaSpeak, a sloppy presentence and bad grammar will most likely result in a deny.
Side note:
These are not written down rules, they're just basic guidelines which I apply to each applicant.
Exceptions may occur in special cases.
PS:
Do not spam, jostle or try to send multiple mails within a short period!
This will, not negotiable, result in a deny despite even if everything else matches.
I'm checking the mails regularly and mostly respond within two of tree work days.
If you're still not receiving an answer you're welcomed to kindly ask if the mail maybe got lost (this might happen, we're all only humans)!
first things first, a ddos protection is not the key to getting applied/approved as official hoster.
There are several things I'm looking for when receiving E-Mails:
1) Professionalism
This includes a proper texted E-Mail, why you want to become a hoster and what you're already offering.
Professionalism also includes the "to be informed" aspect. Does the applicant know what TeaSpeak is, has already some experiences and seems to be capable of hosting TeaSpeak servers for TeaSpeak / TeaWeb clients.
2) Authenticity
Does the applicant have an authentic web presence?
Fits his service all legal needs like an imprint, privacy policy etc
3) Look 'n Feel
This is a quite relative aspect, which mainly lies on my intuition.
Things which come into play are, how serious the applicant presents himself as well what his intuition about the appliance is.
An important point here is that he wants to promote and support TeaSpeak as well that he's informed about TeaSpeak itself.
Questions are allowed and welcomed and will not result in any kind of deny, but having no clue about TeaSpeak, a sloppy presentence and bad grammar will most likely result in a deny.
Side note:
These are not written down rules, they're just basic guidelines which I apply to each applicant.
Exceptions may occur in special cases.
PS:
Do not spam, jostle or try to send multiple mails within a short period!
This will, not negotiable, result in a deny despite even if everything else matches.
I'm checking the mails regularly and mostly respond within two of tree work days.
If you're still not receiving an answer you're welcomed to kindly ask if the mail maybe got lost (this might happen, we're all only humans)!
Last edited:
Vafin
TeaFanatic
@WolverinDEV , i suggest that official TeaSpeak hosts should not be allowed to use the Protocol keys.
Using protocol keys is fine, they're randomly cryptographic keys, based for the connection crypt setup.
We're offering to configuring them in order to provide a way more secure server.
PS: What you may implicitly mean is already included in point 1.
We're offering to configuring them in order to provide a way more secure server.
PS: What you may implicitly mean is already included in point 1.
Yaşar Bilişim
New member
olumlu yanıt yetkili satıcı haline geldi. Ben şimdi ne yapmalıyım?
in english pls
moskito
New member
Hallo , kann mir vielleicht jemand helfen ? Ich habe den Server komplett installiert, die config angepasst. Es soll der Teaspeak-Client connecten können und das Webinterface. Client connectet perfekt, YaTQA connectet perfekt, nur der Webclient schreibt mir folgendes: "Could not connect to remote host (Connection refused) " . Tea*Speak-Client ist völlig unwichtig, weil ich kauf mir auch kein Audi und klebe BMW-Embleme dran. Kann mir evtl bitte jemand beim Webclienten helfen ? Übrigens TS3 connectet auch nicht, aber wie gesagt, unwichtig. Danke schonmal im Voraus.
Danke schonmal im Voraus.
Moin,Hallo , kann mir vielleicht jemand helfen ? Ich habe den Server komplett installiert, die config angepasst. Es soll der Teaspeak-Client connecten können und das Webinterface. Client connectet perfekt, YaTQA connectet perfekt, nur der Webclient schreibt mir folgendes: "Could not connect to remote host (Connection refused) " . Tea*Speak-Client ist völlig unwichtig, weil ich kauf mir auch kein Audi und klebe BMW-Embleme dran. Kann mir evtl bitte jemand beim Webclienten helfen ? Übrigens TS3 connectet auch nicht, aber wie gesagt, unwichtig.
hast du auch TCP Port 9987 freigegeben?
Das ist so zumindest mein erster Verdacht
moskito
New member
Japp Wolverin hat er. Fang ich meist an, wegen Standard-Port, der geht immer ^^. Ich hab schon echt viel probiert, weil bevor ich im Forum frage, probier ich selbst viel durch. Übrigens Wolverin, eine absolut klasse Idee mit Teaspeak, seitdem sich TS nicht schlüssig ist, welche Lizenznorm sie anbieten wollen. So kann ich später Teaspeak anbieten und hier unterstützen. Also TCP/UDP ist enabled, 9987 ist frei gegeben, sowie folgende 13 Ports,mein Anschluss läuft über OpenVPN - Zuweisung einer öffentlichen IP. Keine Ahnung wo es noch dran liegen kann.
---- Automatically Merged Double Post ----
Sorry yamano, my English is better than my Portuguese, but worse than my German. Since the forum also has German users, I will approach them. When we get into conversation later because of licenses, I'll make a little effort with my English.
---- Automatically Merged Double Post ----
Danke Wolverin, habs hinbekommen. Hab die öffentliche IP nicht explizid auf https zugewiesen. Somit gab es einen Crash der Namensauflösung. Kleine Dinge lösen gern mal große Wirkungen aus. ^^ Danke trotzdem nochmal ...
---- Automatically Merged Double Post ----
Danke Wolverin, habs hinbekommen. Hab die öffentliche IP nicht explizid auf https zugewiesen. Somit gab es einen Crash der Namensauflösung. Kleine Dinge lösen gern mal große Wirkungen aus. ^^ Danke trot
Also TCP/UDP ist enabled, 9987 ist frei gegeben, sowie folgende 13 Ports,mein Anschluss läuft über OpenVPN - Zuweisung einer öffentlichen IP. Keine Ahnung wo es noch dran liegen kann. ---- Automatically Merged Double Post ----
Sorry yamano, my English is better than my Portuguese, but worse than my German. Since the forum also has German users, I will approach them. When we get into conversation later because of licenses, I'll make a little effort with my English.
---- Automatically Merged Double Post ----
Danke Wolverin, habs hinbekommen. Hab die öffentliche IP nicht explizid auf https zugewiesen. Somit gab es einen Crash der Namensauflösung. Kleine Dinge lösen gern mal große Wirkungen aus. ^^ Danke trotzdem nochmal ...
---- Automatically Merged Double Post ----
Danke Wolverin, habs hinbekommen. Hab die öffentliche IP nicht explizid auf https zugewiesen. Somit gab es einen Crash der Namensauflösung. Kleine Dinge lösen gern mal große Wirkungen aus. ^^ Danke trot
Last edited: