BlueOnyx
BlueOnyx 5107R - make_sock: could not bind to address 0.0.0.0:80
BlueOnyx 5106R - Unresponsive Login Manager
BlueOnyx uses the PAM ABL module to mitigate brute force attacks. Though it’s not a good idea to rely solely on this module to protect your services, it’s definitely better than nothing. However, for some reason the database storing the failed hosts and users tends to corrupt easily on BlueOnyx systems.
BlueOnyx 5106R - dovecot: Fatal: imap-login: No authentication sockets found
After installing a new wildcard SSL certificate on a BlueOnyx 5106R server, I performed the mandatory system tasks to spot any potential problems. Unfortunately the system was rapidly throwing the following error messages:
Installing a BlueOnyx OpenVZ template with Proxmox VE
The following article demonstrates one approach to installing and configuring a BlueOnyx OpenVZ container using Proxmox VE 1.9. If you’re familiar with Proxmox VE you might have noticed that BlueOnyx has been pulled from the list of community maintained appliances.
Running BlueOnyx with suPHP and WordPress
suPHP allows the execution of PHP scripts with the privileges of their owner. PHP scripts are no longer executed by the Apache user. This will be safer, but also more resource intensive. From a users point of view, the biggest advantage in terms of user friendliness is the fluent installation of plugins, updates and file uploads.