TeamSpeak 5 Client trying to move homebase to same target

I deleted them and reinstalled but still the same. It works fine when I log into a different myteamspeak account. But my main account has such a problem

Can you please share the latest ts chat log?

By any chance you used a non ts5 client with that account? It is known to break account.
I’m asking because the homebase move is suspicious to us. No offense, just asking.

1 Like

I do not know English much. Sorry. I’m posting the logs. I don’t think it’s much different than before.

[2022-07-20 18:12:12.792] [info] TSBindingBrowserTSChat ctor
[2022-07-20 18:12:12.792] [info] TSChat library version: 1
[2022-07-20 18:12:28.982] [info] [tschat_client_lib_export.go:308:TSChat_UpdateHomebase] update homebase: tsChatId=0
[2022-07-20 18:12:28.983] [info] [clients.go:71:UpdateHomebase] Updating homebase to 0
[2022-07-20 18:12:28.983] [info] [clients.go:75:UpdateHomebase] Homebase deleted, tsChatId = 0
[2022-07-20 18:12:28.983] [error] [contacts.go:142:InviteAllContacts] No homebase found
[2022-07-20 18:12:29.085] [error] Failed to move homebase to central: 1
[2022-07-20 18:12:29.113] [info] TSBindingBrowserTSChat::create scHandlerId=0 server_identifier= specifier= endpoint=CENTRAL
[2022-07-20 18:12:29.113] [error] No specifier in create chat, aborting
[2022-07-20 18:12:39.160] [info] TSBindingBrowserTSChat::create scHandlerId=0 server_identifier= specifier= endpoint=CENTRAL
[2022-07-20 18:12:39.160] [error] No specifier in create chat, aborting

[2022-07-20 18:12:12.793] [info] Notifications_Windows ctor
[2022-07-20 18:12:12.811] [info] TeamSpeak Client 5.0.0-beta70 (2022-06-08 08:26:25)
[2022-07-20 18:12:12.811] [info] SystemInformation: Windows 10 (19044) x64 (AMD or Intel) Binary: 64bit
[2022-07-20 18:12:12.811] [info] Using hardware aes
[2022-07-20 18:12:20.343] [info] disconnected from push system.
[2022-07-20 18:12:20.343] [info] current mytsid data is invalid - blocked to request new
[2022-07-20 18:12:20.343] [warning] avatar certificate check failed - keep current avatar (if any) until avatar sign was refreshed
[2022-07-20 18:12:20.610] [info] Initialized with 2 channels in 32bit, 48kHz. - Hoparlör (4- SteelSeries Arctis 1 Wireless)
[2022-07-20 18:12:20.614] [warning] Failed to set volumen_modifier
[2022-07-20 18:12:21.022] [info] connected to push system.
[2022-07-20 18:12:29.085] [warning] failed to move home - error handling triggered: moveHome origin and target are the same: @ag3yrez7hlvafqvnhnhton3yukxft2eeq5ovhm6pqkyxlk3l7vz42===:chat.teamspeak.com
[2022-07-20 18:12:42.796] [info] starting download for http://update.teamspeak.com/windows/x64/latest/info.json

[0720/181212.729:INFO:crash_reporting.cc(219)] Crash reporting enabled for process: browser
[0720/181212.910:INFO:crash_reporting.cc(219)] Crash reporting enabled for process: utility
[0720/181213.542:INFO:CONSOLE(2)] “Notification Settings loaded. [object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]”, source: tsui://default/main.js (2)
[0720/181213.543:INFO:CONSOLE(2)] “Message Notification settings loaded. [object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]”, source: tsui://default/main.js (2)
[0720/181213.543:INFO:CONSOLE(2)] “Whisper Settings loaded.”, source: tsui://default/main.js (2)
[0720/181213.799:INFO:CONSOLE(2)] "Restoring previously opened activities: ", source: tsui://default/main.js (2)
[0720/181214.153:WARNING:browser_info.cc(301)] Returning a speculative frame for 25769803781 [6,5]
[0720/181214.223:INFO:CONSOLE(2)] “analytics :: heartbeat”, source: tsui://default/main.js (2)
[0720/181214.223:INFO:CONSOLE(2)] “default device changed: -none- to Hoparlör (4- SteelSeries Arctis 1 Wireless)”, source: tsui://default/main.js (2)
[0720/181214.223:INFO:CONSOLE(2)] “default device changed: -none- to Mikrofon (4- SteelSeries Arctis 1 Wireless)”, source: tsui://default/main.js (2)
[0720/181214.342:WARNING:browser_info.cc(301)] Returning a speculative frame for 25769803781 [6,5]
[0720/181214.342:WARNING:browser_info.cc(301)] Returning a speculative frame for 25769803781 [6,5]
[0720/181214.343:WARNING:browser_info.cc(301)] Returning a speculative frame for 25769803781 [6,5]
[0720/181214.343:WARNING:browser_info.cc(301)] Returning a speculative frame for 25769803781 [6,5]
[0720/181215.010:INFO:crash_reporting.cc(219)] Crash reporting enabled for process: utility
[0720/181229.086:INFO:CONSOLE(2)] “Homebase moved to central successfully”, source: tsui://default/main.js (2)
[0720/181229.113:INFO:CONSOLE(2)] “Connecting to homebase chat system, homebaseData: [object Object]”, source: tsui://default/main.js (2)
[0720/181229.133:INFO:CONSOLE(2)] “Failed to create tschat: not initialized”, source: tsui://default/main.js (2)
[0720/181229.133:INFO:CONSOLE(2)] “Error joining Homebase connection central”, source: tsui://default/main.js (2)
[0720/181231.065:WARNING:browser_info.cc(301)] Returning a speculative frame for 30064771077 [7,5]
[0720/181231.169:WARNING:browser_info.cc(301)] Returning a speculative frame for 30064771077 [7,5]
[0720/181231.169:WARNING:browser_info.cc(301)] Returning a speculative frame for 30064771077 [7,5]
[0720/181231.169:WARNING:browser_info.cc(301)] Returning a speculative frame for 30064771077 [7,5]
[0720/181231.169:WARNING:browser_info.cc(301)] Returning a speculative frame for 30064771077 [7,5]
[0720/181239.160:INFO:CONSOLE(2)] “Connecting to homebase chat system, homebaseData: [object Object]”, source: tsui://default/main.js (2)
[0720/181239.172:INFO:CONSOLE(2)] “Failed to create tschat: not initialized”, source: tsui://default/main.js (2)
[0720/181239.173:INFO:CONSOLE(2)] “Error joining Homebase connection central”, source: tsui://default/main.js (2)
[0720/181259.193:INFO:CONSOLE(2)] “Connecting to homebase chat system, homebaseData: [object Object]”, source: tsui://default/main.js (2)
[0720/181259.203:INFO:CONSOLE(2)] “Failed to create tschat: not initialized”, source: tsui://default/main.js (2)
[0720/181259.203:INFO:CONSOLE(2)] “Error joining Homebase connection central”, source: tsui://default/main.js (2)

Don’t worry. I have a teamspeak beta badge. Screenshot by Lightshot

My account is open in Teamspeak 3 client at the same time, will this be a problem?

no this should not be a problem (normally).

1 Like

Can you please share your tschat.log in a private message?

1 Like

I sent this to you

Do you use a VPN?

I have that problem when I use a VPN.

If you use one disable it for teamspeak and try if you can go online

1 Like

His problem is a homebase move that should not happen because source and target are the same.
But can not say more till i can talk with IT tomorrow.

3 Likes

No, I do not use VPN.

source and target are the same. What exactly do you mean here?

The client thought it should change the homebase (the chat server that the client uses) but the homebase and the homebase it wants to connect to are the same so it thinks you’ll changing the chat server when you acutally are not changing it.

3 Likes

We can not see why your client tries to move it’s homebase.

Can you please do following in order?

  1. Clear your homebase.
    Enter Dev into Client’s search bar and you will find Developers tools.
    Scroll down and press the Clear homebase button.

  2. Close the client and Rename or Delete the Default Folder in following paths:
    %AppData%\Teamspeak
    %LocalAppData%\TeamSpeak\Cache
    %LocalAppData%\TeamSpeak\User Data
    %LocalAppData%\TeamSpeak\Logs

  3. Start the client and go back into Developers tools and activate Debug in Log Level.

  4. Restart the client and set the myTS as homebase (in case Setup chat is there at the bottom).

  5. Zip all logs and share them to us.

2 Likes

Upload Files Easily | Fast File Upload and Sharing Up To 10GB I did what you said and sent you the log files.

1 Like

Can you please start the TS5 client and reset your myTS password and do a fallback while the client is running?

Why am i asking this?
Our guess is that your made password reset in the past and some data from client did not reach the synced data.

**We can reproduce this move that should not happen but in general the client recovers from that and just triggers a new creation and it works fine. **not exactly your case but logs look the same

Before you do the reset!

We looked into your account and you only seem to have 1 identity synced.
You may backup this identity first before you do the fallback.

We can not recover this identity, because it is encrypted and we do not have access to this data.

4 Likes

reset your myTS password and do a fallback. What did you mean here? Do I need to reset my myTeamspeak password?

Yes. Start the client and make sure that you are logged in and then visit Reset myTS password page and do the reset.
You must use a different password then the current one you use to login. Else your encrypted data does not get cleared. You can change the password afterwards.

But be aware that you loose that one mentioned identity!!!

2 Likes

The problem is solved for now. Thank you. I hope the username change system will come, I don’t like this username. You know sometimes we set a username and they use it in the Game it’s terrible

Great.

So did you reset your password some months ago?

1 Like

It’s possible. i don’t remember exactly