Server I need help: Servers getting on greylist

[n0ns]

After I started using an original license converted to teaspeak I'm frequently having problems with greylisted on my IP
The license I bought was 32 slots for $ 30 annual plan
I converted to teaspeak with the help of a post here right from the forum and I was able to connect the most recent clients normally.
Some ports on the teaspeak server have the capacity of 50, 100, 250, 300 slots
Is there any recommendation not to get greylisted?
Is there something I forgot to do too?
I've never had this problem while using the Tea*Speak Server Crack 3.0.13.8 with Accounting Emulator from r4p3.net

 

[mkll11one]

If you buy license with 32 slots = only 32 slots can be there!
And there is always chance for be "greylisted" incl blacklisted!

 

[n0ns]

If you buy license with 32 slots = only 32 slots can be there!
And there is always chance for be "greylisted" incl blacklisted!

Understood my friend
Can you tell me if there is someone selling licenses with the most amount of slots supported here in the forum?

 

[yamano]

Since i'm using Teaspeak (+-6months) i do not have grey/blacklisted ip's
90% of the grey/blacklisted servers results from a bad configuration..

Basic Rules:
1. Do not publish your teaspeak servers in weblist (the most important)
2. Do not publish your teaspeak servers in gametracker
3. Close 2008 port (accounting)
4. Close 2010 port (weblist) (There is a option in "config.yml" to disable weblist report.)
5. Use cloudflare to hide your real server ip (when clients are connecting with dns)

That's what i'm doing

 

[n0ns]

Since i'm using Teaspeak (+-6months) i do not have grey/blacklisted ip's
90% of the grey/blacklisted servers results from a bad configuration..

Basic Rules:
1. Do not publish your teaspeak servers in weblist (the most important)
2. Do not publish your teaspeak servers in gametracker
3. Close 2008 port (accounting)
4. Close 2010 port (weblist) (There is a option in "config.yml" to disable weblist report.)
5. Use cloudflare to hide your real server ip (when clients are connecting with dns)

That's what i'm doing

Do you use a converted license as well?
So you can connect the most recent customers ...

Of all the list you cited, I just do not do the cloudflare
I had problems with it in the past, in which using their connection, many users would lose the connection or were simply dropped from the server in random times ..
Currently I use cloudflare, but only for dns
Without that little cloud marked in the rules

 

[yamano]

Yes. I'm using Tea*Speak license converted.
I'm using cloudflare with that little cloud marked so my ip's can stay hidden

 

[n0ns]

Yes. I'm using Tea*Speak license converted.
I'm using cloudflare with that little cloud marked so my ip's can stay hidden

Outside the marked cloud, should any other configuration be made to the cloudflare dashboard?
Because I had an experience in the past where some people lost connection at random times with my server ... and only after a while did I find out that it was because of that cloud marked on the panel.
Since then I use only their DNS function, without the cloud marked

 

[yamano]

I think not.
That kind of experience / problem was in teaspeak and not in the cloudflare.
Teaspeak is constantly updating, at the moment, the only problem i'm facing is just the
memory fragmentation when using Sinusbot (tested by the last 4 months!).
All the other teaspeak problems are from the past

 

[farhadhelix]

i have done limiting connections to my country and preventing other country accessing my servers. that plenty helped me from getting blacklisted
i dont know your situation . but if you are certain on countries which your members are connecting , limit it to only those countries especially USA which Tea*Speak is located at it .