Heck, that's a lot of time.Took me nearly 3 hours to figure out ^^ Please have a look and advise.
curl -o- https://raw.githubusercontent.com/JoelLinn/iocage-ix-plugins/JoelLinn-backuppc/backuppc.json | sed -e 's/github.com\/freenas/github.com\/JoelLinn/g' > backuppc_joellinn.json iocage fetch -P --name backuppc_joellinn.json ip4_addr="em0|192.168.0.123/24"
iocage set -P adminpass="newpassword" backuppc
pkg install sudo
sudo -u backuppc ssh user@hostname
Thanks, I disabled strict host key checking for ssh so this is no longer an issue.I do have to say, using rsync/ssh i first had to:
pkg install sudo sudo -u backuppc ssh user@hostname
and then add it to known hosts, in order for it to work, we might need to come up with an automated solution for this.
Nothing exposed to the WWW. I use lets encrypt certificates on the intranet with split dns and many other organizations started to do so as well. Otherwise they would either often distribute the same paid wildcard cert among all their services or deploy their own root certificate - ewh.* I don't think we should use letsencrypt, more things can go wrong and who wants to access this tool via WAN? Just use VPN.
Great work so far, thanks.
Backuppc takes the username from apache, so users are effectively managed by a htpasswd file. Nothing to do with freenas users.* Users you mean in the FreeNAS ui right? that will also reflect to SMTP settings, would be the same implementation i guess.
Nothing exposed to the WWW. I use lets encrypt certificates on the intranet with split dns and many other organizations started to do so as well. Otherwise they would either often distribute the same paid wildcard cert among all their services or deploy their own root certificate - ewh.
However, I would set it up so that the acme.sh script is only downloaded once the user has choosen to use it.
Backuppc takes the username from apache, so users are effectively managed by a htpasswd file. Nothing to do with freenas users.
Mails are send using a sendmail compatible tool that has it's own configuration file which has to be generated by the iocage settings backend as well.
These are two different things.
root@backuppc:~ # service backuppc status
backuppc does not exist in /etc/rc.d or the local startup
directories (/usr/local/etc/rc.d), or is not executable
After a restart all of a sudden:
root@backuppc:~ # service backuppc status backuppc does not exist in /etc/rc.d or the local startup directories (/usr/local/etc/rc.d), or is not executable
Admin console not accesable, rc.d dir seems non existent. Any idea?
pkg info
I was on vacation, it is not finished nor is it stable.Hey guys,
how is the current status? Is it finished/stable? Is an official patch for the current plugin planned?
If you use my instructions there is no need to fidle with config files.Hi guys,
Same here, trying to install backuppc to a fresh jail, but got error :
Error: Unable to connect to BackupPC server
This CGI script (/BackupPC_Admin) is unable to connect to the BackupPC server on BackupPC port -1.
The error was: unix connect: No such file or directory.
Perhaps the BackupPC server is not running or there is a configuration error. Please report this to your Sys Admin.
Since I am not an expert I guess I messed it up with httpd.conf or config.pl TT.
Is your pluggin ready ? or I should figure out my issue?
THX m8s
If you use my instructions there is no need to fidle with config files.
Treat it like it is alpha software though.
Testing SRV response to iocage-plugins
pkg.cdn.trueos.org's SRV record could not be verified.
Testing DNSSEC response to iocage-plugins
pkg.cdn.trueos.org could not be reached via DNSSEC.
Then I pinged google to check internet acess, and works fine.
What I am doing wrong, any setting on freenas I should change?
Sorry for my late answer, Was a newbee mistake from me, the ip4 was set to 255. ;) Now works fine.Can you install other official plugins?