backuppc – gui downloading bin file – Ubuntu 14.04

I’ve just made a fresh install of backuppc on Ubuntu 14.04. However, when I visited the web interface then the browser just shows a bin file like this:


Having a bin file server from Apache (or any other web server) generally means there is a fault with the webserver and the script isn’t being parsed before it’s served.   A quick look at the Apache log files located at /var/log/apache2/error.log shows the problems:

unable to connect to cgi daemon after multiple tries: /usr/share/backuppc/cgi-bin/index.cgi

Apache2 isn’t parsing the file through a cgi script.  The Apache server doesn’t have the cgi module enabled.  You can enable an Apache module from the command line without editing any configurations.

sudo a2enmod cgid

Then restart apache2

sudo service apache2 restart

You should then have a working copy of backuppc.

14 thoughts to “backuppc – gui downloading bin file – Ubuntu 14.04”

  1. Hello I get the same issue as you have here. When I do “sudo a2enmod cgid” it says it already running and then a restart of apache didnt help. any other ideas?

    1. When you do “sudo a2enmod cgid” it should have said “Module cgid already enabled” rather than already running. Did it say that?

  2. I also found out you have to use the right adress, “localhost/backuppc” and “127.0.01/backuppc” cause this problem more likely than “”

  3. For me, on kubuntu 14.04 LTS, it helped to just restart the OS after the installation of Backuppc, and voila, it’s web interface started to work. Command line hacking wasn’t neccessary.


  4. I think the problem is in different plase.
    I have prepared Backuppc on virtualbox – it worked fine. So i have copied it on secondary machine, with same network settings. In this case backuppc started, but in it’s interface there was error “cant connect to”
    But, when changed hostname, it started to download binary file when accessed from any machine in network
    But… still have no idea how to make it work if not want to build BackupPC from scratch

    1. Hum, it sounds like some settings are wrong in Apache. is the local interface. Have you tried enabling the cgi server and restarting Apache?

Leave a Reply