[Discussion] TeamSpeak Server 3.1.0 Beta

[numma_cway]

The problem what we have is the IPv6 protocol.
If you connect with a IPv6 address to the ts3server than the filetransfer is doesn't working...
If i connect with a IPv4 address to the ts3server than is the filetransfer work!

On the iOS Client is that with IPv4/IPv6 not working...
Unfortunately I still can't say where the problem with iOS is.

I don't know where your issue with that is. It works for me. So it's not a bug.

[MrCraigTunstall]

Hi, some Aussies are finding it hard to join my server and are getting the "the time difference between server and client is too large" error. So I got them to change timezone to "auto" if using Windows 10.

[dante696]

1. File transfer for IPv6 also works fine for us.


Update for following point: This needs a client update with bigger value. Server will not be touched for this.

2. about the time difference:
This only should appear when clock is wrong to set timezone on their computer (in case the timezone & clock is right on your server).
We will raise the current allowed time difference for the server.

Note: This will delay the stable release for 1 or 2 days.

[SossenSystems]

I have some users thay say that also...

[maggy]

I don't understand this time zone issue. If the idea is to check system time against another source, that should always be calculated in UTC. Otherwise when an offset transition occurs (like daylight savings or the user moving across a time zone boundary) then the calculation will be wrong and apparently the user will not be able to connect. But earlier you said that the tolerance is +/- 6 hours (against what?) which at least conceptually should not trigger this.

Maybe the client should log the result of the calculation so that it can be debugged, eg. "your system time is 13h behind [source]"

[numma_cway]

It compares the UTC time of the system against the server's UTC time.
Thing is: If you set a random timezone and then set the time to what your clock says, the local time (which is display in the bottom right) looks right, but the UTC is incorrect, because you set a random timezone, so your computer cannot calculate UTC.

E.g.: You live in Berlin, DE +0100 and it's noon there, so it's 11:00 UTC. Then – like everyone who has this issue – you set your timezone to some random timezone just because you think it's funny, let's say Queensland, AU +1000. After that, you set your clock to noon. That equals 02:00 UTC, but it's actually 11:00 UTC.

[maggy]

If that's the case, then the error displayed to the client should include a link to a KB article explaining this and how to fix it, since a simple error message won't help these people.

That is assuming that this is the only scenario that is causing this error.