As I wanted my new server to act as a DVR, I decided to go with MythTV as my backend.
Install MythTV (server only, I will have separate frontends):
- Install htdigest (for password protecting MythWeb):
- sudo apt-get install apache2-utils
- Install mythtv-backend-master (and all dependencies)
- sudo apt-get install mythtv-backend-master
- Answered yes to password protect MythWeb
- Told it that MythWeb would not be the only thing running on Apache
- Told it other computers would be connecting to it (remote frontends)
- Ran mythtv-setup
- Changed database password to match the one in /etc/mythtv/config.xml
- Changed it to listen on 192.168.1.XXX instead of 127.0.0.1
- Also change the backend ip to the same (learned this the hard way)
- Added my HDHomeRun Dual tuner (must do twice once as tuner 0, second as tuner 1)
- Created an OverAir video group (use EIT)
- Put both tuners in this group
- Scanned for channels
- Enable remote connections in mysql (learned this the hard way):
- Change the bind-address in /etc/mysql/my.conf
- bind-address = 192.168.1.XXX
- Restart mysql
- sudo service mysql restart
Software Versions:
Xubuntu 14.04.1 LTS (Trusty Tahr)
MythTV 0.27
Troubleshooting:
Make sure MythWeb password protection is on. In /etc/apache2/sites-enabled/mythweb.conf the following lines should be un-commented:
AuthType Digest
AuthName "MythTV"
AuthUserFile /var/www/htdigest
Require valid-user
BrowserMatch "MSIE" AuthDigestEnableQueryStringHack=On
Order allow,deny
Satisfy any
Restart apache:
sudo service apache2 restart
For more info see:
http://www.mythtv.org/wiki/Securing_MythWeb
Error: "mythtv cannot connect to database":
My remote frontend
was unable to connect to my backend mysql database until I changed
/etc/mysql/my.cnf to allow remote connections by changing bind-address
from 127.0.0.1 to 192.168.1.XXX (server ip)
Mythfilldatabase returning an error about no version response, really slow backend connections, and constant backend crashes:
Turns out that when changing the ip to listen on from 127.0.0.1 to 192.168.1.XXX, you
HAVE to make sure to also change the backend ip from 127.0.0.1 to 192.168.1.XXX