Server 3.13.0 [Beta]

Yeah, I know, but this is how this world sadly works.

Either way, as I said earlier, very nice update, I’ll continue to support Staff but I had to be honest with what happened when reading that changelog.

But please, don’t be ridiculous like this next time as from what I can see, some people agree it was rather weird idea. And they might go away to other camp.

Edit, as someone thinks this is going off-top. It’s not. All these ”off-top” posts maybe barely but touch the topic, because we talk about a change made to the software. Sorry…

Hmm, after the update, i am unable to do anything. Even though i have full access (Server Admin) I can’t bypass anything (passwords, max clients, move other etc)

I also tried to test it with a new server creation just for test. So i made one, got the Server Admin from the priviledge key and made a channel with password. Logged out and logged in again, and ask for password. Even if the password is correct i still can’t join with the same error (invalid password). Also if there is channel limit the server admin can’t bypass it.
@TS.ChrisR

Is it enough to simply replace the old files with the new ones, because there are several changes now and I want to make sure that nothing gets lost in this update? :thinking:

I would like to kindly remind you this is a “Beta” build. I’d suggest to take a backup when testing such builds. If you’d like to remain on a stable build then I don’t think beta builds are for you.

1 Like

I know that this is a beta, hence the question

@TS.ChrisR
I think its time to change the web serverlist so server owners can add a domain/subdomain and allow the server owners to hide the IP of the server it’s not that hard to do and you guys still see the server IP and for the license and we can get the server more secure and more protection against DDoS … and more…
It’s 2020 … please …

Edit:
fix the channel permission i_client_poke_power
don’t know why if I set it to -9999999 the users still can send a poke to other users on the server

1 Like

Because this only counts for this one channel only and not for others.

@anyone else the web list has nothing to do wit this server release!

1 Like

Can only reproduce the password part here. But i can join a channel when i enter the right one.

A server restart and now i can reproduce more.

What we can not reproduce is that the password is wrong part. If we enter the password it is accepted.

3 Likes

A post was split to a new topic: Don’t want that anyone without a myTS account can join my server

Maybe a more descriptive name makes sense? afaik this list is used to circumvent rate limits and not for exclusive allows, so something like

query_ip_unlimitedlist
query_ip_unratedlist
query_ip_exceptionlist
query_ip_limitlesslist

After a client restart, when i type the passwords works fine - maybe something went wrong for that moment. So we still have the issue with the ignore passwords and the maxclients - inherited maxclients.

I’m a little concerned by this. I used to copy the admin server query group into a new server group, just for the sake of easily giving myself full access to my server. Do I take this to mean that this has been disallowed and completely locked down?

No. You still can copy the permissions into a normal server group.

This only means you no longer can set a ServerQuery group as a default template group for virtual servers. These templates are only needed when you create a new virtual server or did a permreset in an existing virtual server.
This was a bug and could break the database.

2 Likes

Ahh, no worries. Thanks very much for clarifying! :slight_smile:

Hey Chris, would it not be best to let people know about this in the “Known issues” section?

Had it something in draft but never send it. I did it know.

3 Likes

Beta.2 is live.

Download and latest changelog can be found in main post on Top.
Changelog here on forum is newer then delivered within the server!

6 Likes

Everything looks normal until now. Thanks for the fix :slight_smile:

1 Like

Tested… seems worked fine for me. :slight_smile:

Untill now, with beta1, no memory leak. Something like +10MB of RAM with 4 days of uptime.
Testing now beta2. I will give some feedback here soon.

Cheers

1 Like