Froxlor
The server administration software for your needs. Developed by experienced server administrators, this panel simplifies the effort of managing your hosting platform.
Installation
Fast install
- Ensure that your webserver serves /var/www
- Extract froxlor into /var/www
- Point your browser to http://[ip-of-webserver]/froxlor
- Follow the installer
- Login as administrator
- Adjust "Server > Settings" according to your needs
- Choose your distribution under "Server > Configuration"
- Follow the steps for your services
- Have fun!
Detailed installation
http://redmine.froxlor.org/projects/froxlor/wiki/Installationtarball
Help
You may find help in the following places:
IRC
froxlor may be found on freenode.net, channel #froxlor: irc://chat.freenode.net/froxlor
Forum
The community is located on http://forum.froxlor.org
Wiki
More documentation may be found in the froxlor - wiki: http://redmine.froxlor.org/projects/froxlor/wiki
License
May be found in COPYING
Downloads
Tarball
http://files.froxlor.org/releases/froxlor-latest.tar.gz MD5 SHA1
Debian repository
/etc/apt/sources.list.d/froxlor.list
deb http://debian.froxlor.org {wheezy|jessie} main
Gentoo repository
http://files.froxlor.org/gentoo/repositories.xml
Let's Encrypt support
This version of Froxlor contains a test implementation of support for Let's Encrypt. This is (as Let's Encrypt is in itself) still a beta version and may break your system. The way it currently works is by creating a (sub-)domain with the default system - certificate, after which the Let's Encrypt cronjob orders the certificate for this (sub-)domain and inserts the certificates in the database. With the next run of the default cronjob, the certificates will be updated on the disk and the webserver reloaded.
This has 2 known side-effects at the moment:
- The basic ip/port combinations don't work with the Froxlor - integration of Let's Encrypt, since it needs a certificate for the very first creation
- After creating a domain, it will have the default certificate for a short time (by default 5 minutes until the cronjob runs the next time)
It may be possible to fix these issues, but they are not a priority at the moment
By default the testing environment of Let's Encrypt is used. This issues certificates which will not be signed by a known certificate authority.
To activate the production system, change the Let's Encrypt environment in Settings -> SSL settings to https://acme-v01.api.letsencrypt.org (Live).