Terran Stellar Navy › Forums › (OOC) Division Development › Possible teamspeak issue
- This topic has 12 replies, 6 voices, and was last updated 8 years ago by
Nhaima.
-
AuthorPosts
-
21/01/2017 at 01:35 #19911
Nhaima
ParticipantAfter upgrading my teamspeak (or failing to stop the upgrade), I’m no longer able to connect to the TSN server. Other people have expressed similar issues. Do we need to rollback TS or is this something that needs fixing server-side?
Workaround:
Connect to “85.236.100.85:17587” rather than the comms.terranstellarnavy.etcIf that doesn’t work, there is a more detailed work around below.
-
This topic was modified 8 years ago by
Nhaima.
21/01/2017 at 01:47 #19913Nhaima
ParticipantBased on the server message van Leigh noticed, if you upgrade to 3.1 then you won’t be able to connect. Don’t upgrade your TS client unless Jemel, et al. gives the okay.
-
This reply was modified 8 years ago by
Nhaima.
21/01/2017 at 04:09 #19918Nhaima
ParticipantI have a work around for people who need it tomorrow, but if someone could log in and restore my rank and ADO privileges that would be great. I’m also reluctant to post the work around until I’m able to test it or at least correct the mistake if it backfires again.
21/01/2017 at 04:58 #19920John van Leigh
ParticipantNhaima managed to invent a workaround until Jemel fixes this server-side
I’ll spend the night drinking coffee, so if you need me to set up your permissions you can PM me over teamspeak.
21/01/2017 at 05:03 #19922Nhaima
ParticipantThank you to Cmdr. van Leigh for being a guinea pig, we now have a tested work around! Also to Lt. Cdr. Zelreich for fixing my account… >_>
If you cannot connect to Teamspeak because you updated your client:
- Open Teamspeak
- Go to Settings > Identities.
- Export your default identity.
- Download this installer.
- Run the installer and install it to a different location (such as C:\Teamspeak)
- Run the new teamspeak client.
- Go to Settings > Identities.
- Import your old identity.
- Connect to the TSN server.
You should have all your old permissions, etc. intact. If there is an issue, please contact the DO (me) and I’ll set about fixing things for you.
21/01/2017 at 08:29 #19932Blaze Strife
ParticipantThank you for the notification. I will not upgrade my TS until the brass says we can.
Also, I see roleplaying potential in this.
21/01/2017 at 16:43 #19944Anonymous
InactiveAs do I Blaze.
23/01/2017 at 18:58 #20025Jemel Eahain
Moderatorm still trying to problem solve the issue,
im not 100% sure its the server itself that has an issue as i have set up a backup url to test if the new ts3 client was having issues with connecting via url rather than ip, if others could try conecting via “tsn.ts3dns.com ” to confirm that works would be helpful.23/01/2017 at 19:54 #20033Nhaima
Participant‘tsn.ts3dns.com’ works for me, with the updated TS3 client. I think you fixed something while you’ve been working on this, because I can connect again using ‘comms.terranstellarnavy.community’
That said, when I do I get the following error message:
This server configuration is deprecated. Support for this configuration will be dropped with client version 3.1.1. Please contact your server administrator. For details, please see this Knowledge Base article.23/01/2017 at 19:56 #20035Nhaima
ParticipantTo be clear, I only get the error message when I connect to ‘comms.terranstellarnavy.community’
When I connect to ‘tsn.ts3dns.com’, it doesn’t complain in the slightest!
23/01/2017 at 22:31 #20048Jemel Eahain
ModeratorI reset some of the dns settings and removed a couple that should have been redundant, I be leave the error is from the not so redundant settings,
-
This reply was modified 8 years ago by
Jemel Eahain.
28/01/2017 at 00:29 #20115Charles Beaumont
ParticipantThought I’d double check here. Am I OK to update Teamspeak, is there anything I need to do to keep my profiles, and which address should I use when connecting?
28/01/2017 at 09:08 #20123Nhaima
ParticipantBack up your identity, just in case. You should be okay to upgrade, particularly if you connect via the IP:Port listed in the first post. All of the connection methods described should work, and I’ll be around tomorrow in case something goes sideways and you need your settings restored.
-
This topic was modified 8 years ago by
-
AuthorPosts
- You must be logged in to reply to this topic.