Provider appliance
Jump to navigation
Jump to search
Contents
Key features
The regify Provider Software Appliance can get described with the following key attributes:
- Software appliance, based on a special Linux version (comes as an ISO image).
- Hardened for 24/7 internet availability and security
- Built-in firewall blocking all unused ports.
- All unused services, users and groups are removed or stopped.
- Continuously updated by "check for updates" function including all operating system and application components (Kernel, Apache, MySQL, OpenSSL etc).
- Appliance management is only available by SSH from internal IP address range or (optional) from dedicated external IP addresses.
- Supports database replication (Master-Slave, Cross-Master) for full redundancy and high availability.
- Offers easy SSL certificate generation and usage, including LetsEncrypt support (menu guided).
- Fully supports all Subprovider features (handles multiple IP addresses, customizations etc).
- Included database (MariaDB as the default).
- Included Apache Webserver with PHP environment.
- Included MTA (Mail Tranfer Agent) which is also usable as relay with a company SmartHost.
- Automatic time-synchronisation using NTP.
- Fully supporting NAGIOS monitoring.
- Fully supporting ZABBIX monitoring.
- Use any network SMB shares for regibox and regipay Plus storage (optional).
- Installs in less than 10 minutes.
- Allows easy and automatic updates.
- Does not need any advanced Linux knowledge.
Hardware requirements
You can find the hardware requirements at the Hardware page.
Performance considerations
You can find information about performance and speed at the Hardware page.
Monitoring support
The regify provider software appliance offers you two kind of monitoring:
- Monitoring using Nagios or Zabbix
- Using the built-in monitoring capability:
Built-in monitoring
The regify provider software appliance offers a dedicated HTTPS call to get information about the health of the regify provider. By calling this prepared URL, it returns either
- "OK" -> Everything is fine
- "WARNING: description" -> System still running, but there are problems
- "ERROR: description" -> System is in maintenance mode and not running
The description contains detailed information about the reason of the current state.
This monitoring call allows you to generate basic monitoring with no big efforts. This call is testing the following things:
- Clearing connection health?
- Is the provider in maintenance mode?
- Is free disk space bigger than 300MB?
- Is regibox space available and working (if enabled)?
- Do we have working cryptography?
- How is internal database connectivity?