Howto: TeamSpeak 3 server in pfSense 2.x(Now with scripts amd64) v1.3

kevev

Post #2 has everything you are looking for. You can tar up the install which will backup the sqlite database.

I'm going to attempt an update to pfSense today. Kev, what steps would you recommend I follow in order to retain my settings/unique key through the update?

Also, are there any easy ways to make running this server on my pfSense box any more secure? Simple stuff like firewall rules or at least some basic things that don't leave the rest of my network open to attacks through the TS server. Right now I only have the one LAN that goes through an Asus RT-N56u that serves my main rig, 2x smart Bluray players, 1x Chromecast, 1x Android tablet, 1x Android phone. The proper solution here is to not host TS on the pfSense box, but it's my only option for the foreseeable future. It's going to be a while before I get my new rack installed and all my server hardware back online.

ETA: Also, what would be required if I decide to change hardware for pfSense? Eventually I plan to get one of those small devices from aliexpress to mount to my network panel and I would very much like to keep my TS server and not have to reconfigure everything from scratch. I know I can export/import my pfSense settings, just curious about the TS server. Would I have to do something like download a specific folder, install TS on new pfSense box, upload that specific folder?

opjohnny

@kevev:

Post #2 has everything you are looking for. You can tar up the install which will backup the sqlite database.

Thanks Kev! Backed up the TS directory, ran the update, TS came back online with pfSense with no issues. 8)

opjohnny

Backed up my TS directory and updated to pfSense 2.2.1. Absolutely no issues. 8)

opjohnny

Backed up TS, upgrade to pfSense 2.2.2 went without a hitch, then realized TS 3.0.11.3 was available so continued instructions in post 2 for an actual TS upgrade, but ran in to an issue at the step where I extract the tar.gz file in /root/ to /user/local/lib.

tar -xzvf teamspeak3-server_freebsd-x86-*.tar.gz -C /usr/local/lib

tar: teamspeak3-server_freebsd-x86-3.0.11.3.tar.gz: Not found in archive
tar: -C: Not found in archive
tar: /usr/local/lib: Not found in archive
tar: Error exit delayed from previous errors.

Then after I started the TS server back up it was taking a long time, rebooted, same issue. Saw the TS processes running in the webGUI. Did a forcestop, tried start a few times, eventually the server came back up. When I connected to it I was given a popup notice about the server identity changing and asking me if I accept the new identity and want to remain connected. Not exactly sure what happened here.

ETA: I stopped the server, unzipped the tar.gz on my desktop, then unzipped the .tar on my desktop, then copied that folder over to /usr/local/lib/ via FileZilla, issued the chown command, then rebooted pfSense since I always have trouble manually starting the server for some reason. The server came online a few minutes after rebooting the box. Viewing Server Connection Info in my TS client shows version 3.0.11.3.

For anyone having a similar issue with the tar command just download FileZilla(the .zip option, not .exe since the latter includes bloatware) and connect to your router IP using port 22. Make sure SSH is enabled in Advanced Settings of pfSense and under that no port is chosen, otherwise if you set a port use that port to connect with FileZilla. Then just drag and drop the TS folder to /usr/local/lib/ and choose the overwrite option for all files in queue.

opjohnny

Haven't upgraded in a while but due to pfSense 2.3 being released I'd figure I'd give an update on how things are working in case others are still hosting TS on their pfSense box or will do so.

The upgrade to TS Server 3.0.12.3 went without a hitch. I just followed the upgrade instructions except for the extraction part. For that I still unzipped the folder and copied its contents to the folder un \usr\local\lib\ in FileZilla, making sure to overwrite all. You also need to add an ".sh" to the end of "server" in the start command in the instructions otherwise it will fail as an unknown command.

After the upgrade to pfSense 2.3 the TS server came right back up on its own as expected, so this method still works great.

Thanks again, Kevev. 8)

tong

Carefull guys Teamspeak has changed their naming schemes, so you have to be careful and make those changes:

for example this latest update 3.0.12.4 as of today:

teamspeak3-server_freebsd_amd64.3.0.12.4.tar.bz2

**problems were: freebsd_amd64 instead of freebsd-amd64 (including the internal folder)
**changed it from a tar.gz to a tar.bz2

So either edit the install script to reflect those changes or, as I did, I changed the name of the file from _ to -, and changed the name of the internal folder from _ to - also, then changed it from tar.bz2 to tar.gz

NoOneParticular

@tong:

Carefull guys Teamspeak has changed their naming schemes, so you have to be careful and make those changes:

for example this latest update 3.0.12.4 as of today:

teamspeak3-server_freebsd_amd64.3.0.12.4.tar.bz2

**problems were: freebsd_amd64 instead of freebsd-amd64 (including the internal folder)
**changed it from a tar.gz to a tar.bz2

So either edit the install script to reflect those changes or, as I did, I changed the name of the file from _ to -, and changed the name of the internal folder from _ to - also, then changed it from tar.bz2 to tar.gz

I just wanted to add, the scripts haven't been updated for this change yet.

I found it easiest to modify the install file and rename the folder within the script after the teamspeak3 server file is decompressed. The script will continue and you'll have less changes to make to the install script.

```
tar -xf /root/teamspeak3-server_freebsd_amd64*.tar.gz
mv teamspeak3-server_freebsd_amd64 teamspeak3-server_freebsd-amd64

2dfx

Anyone else having file i/o issues with TS3 after installing? Can't modify icons or upload files to the server.

All folders within the ts3 server folder in /usr/local/lib have been chown'd recursively to the teamspeak user yet the issue still exists.

opjohnny

Just updated Teamspeak to 3.0.13.6, no issues at all. Still doing it the copy/paste way where I connect via filezilla and drag the contents of the new \teamspeak3-server_freebsd-amd64\ folder in to the usr\local\lib\teamspeak3-server_freebsd-amd64\ folder overwriting everything, with putty open in the background for the backup and ownership commands. This way also doesn't require you to rename anything.

tong

Looks like the newer version don't give root enough permissions for /usr/local/lib

I've tried everything i could on a new install to get it to work with no success. True i have very limited skill and knowledge on freebsd.

Any chance someone could explain how to get it to work on a new install (version 2.3.3 )?

Or maybe we can get an updated script?

opjohnny

I'm up to date on pfsense and no issues with TS, especially after multiple reboots the last few days while trying to open NAT for my xbox. Haven't attempted any TS updates in a few weeks.

tong

I ended up finding an image of 2.2 i had that allowed me to install TS then updated to 2.3.3, trying to figure out why in the new package root does not have permissions with /usr/local/lib to be able to copy the files over and do the rest.

opjohnny

So TS server will only work if it's already installed prior to 2.3.3, and after 2.3.3 you can't install or upgrade the TS server due to the permissions issue?

tong

@opjohnny:

So TS server will only work if it's already installed prior to 2.3.3, and after 2.3.3 you can't install or upgrade the TS server due to the permissions issue?

That seems to be my experience, unless I choose something I shouldn't have during an install. I will test this out later on another box I have just in case.
Seems that root user no longer has enough permissions to /usr/local/lib to copy the folders over (never mind the rest of the stuff it has to do).

tong

It works. You need to edit the "pfsense-teamspeak-install_amd64.sh" and "teamspeak3-server.sh" script and change all instances of

/usr/local/lib/teamspeak3-server_freebsd-amd64

to

/usr/local/lib/teamspeak3-server_freebsd_amd64

That single "-" is what's causing the install issue. It extracts the archive to a folder named "teamspeak3-server_freebsd_amd64" but tries to move a folder named "teamspeak3-server_freebsd-amd64" to that location and obviously that doesn't exist.

Funny thing is it's not the scripts fault cause it's not telling it what to extract it to. Teamspeak changed the folder structure that it extracts. So looks like someone decided not to follow precedent and errors like this happen.

opjohnny

That is a known issue. It was a page or two back when someone caught the change.

iced98lx

OPJohnny - have you abandoned the idea of making a package for this vs manually handling it with scripts?

opjohnny

Outside of my skillset, honestly. I'm a Microsoft sysadmin that just dabbles in this stuff.

iced98lx

Fair enough, I understand completely.

iced98lx

Just wanted to say that after I manually extracted and renamed the 64 bit file the script worked great!