https://bugs.contribs.org/show_bug.cgi?id=10494

--- Comment #90 from Jason Smith <[email protected]> ---
(In reply to Jason Smith from comment #89)
> (In reply to John Crisp from comment #88)
> > OK,
> > 
> > I am not sure why it can't resolve/connect on startup. There are a number of
> > issues in the forums but they say 'fix your DNS' which isn't helpful if it
> > seems to be working....
> > 
> > I deleted the DB and restarted and it seemed happier, BUT the admin key
> > changes and it obviously doesn't update the Setting in config show teamspeak
> > 
> > Despite the startup error it seems to be up and running after a reboot and I
> > can get a terminal with:
> 
> > https://support.teamspeakusa.com/index.php?/Knowledgebase/Article/View/44/16/
> > which-ports-does-the-teamspeak-3-server-use
> > 
> > Are you using this locally only or over the interwebs? Here are the ports
> > you need open for remote access ie INBOUND connections - OUTBOUND are never
> > blocked):
> > 
> > teamspeak=service
> >     TCPPorts=30033,10011
> >     UDPPort=9987
> >     UserPassword=laskjdlkasjdlkjdlkjsad
> >     access=public
> >     status=enabled
> > 
> 
> Yes I updated the teamspeak server with the new version. I was able to
> remotely connect with clients even with the errors in the logs. I have now
> opened those ports and will see if that fixes that issue at least.

Sorry when I say new version, I mean the 3.4 which is the current server
version available. After reboot same error in log...

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
_______________________________________________
Mail for each SME Contribs bug report
To unsubscribe, e-mail [email protected]
Searchable archive at https://lists.contribs.org/mailman/public/contribteam/

Reply via email to