Username Password
Bookmark and Share


Related Pages

  • adding a new site to existing webgui installation
    This was written using webgui 7.4.40, wre .8.4
  • - what it does. is one of three scripts that is suggested to be set up as a cron job. See WRE installation wiki for details.
  • Building the WRE on 64bit RHEL 5 or CentOS 6
    These instructions were originally written by pvanthony who installed WebGUI 7.10.26 onto CentOS 6 64bit and whose original post can be found at (towards the bottom of the second page of posts). I've modified them after my experiences of installing WebGUI 7.6.35 onto RHEL 5 64bit. Lots of thanks to scrottie and haarg for their help on IRC.
  • Compile mod_php into WRE
    Although we all love WebGUI, there are times when PHP is needed for custom apps or tools. We've implemented this solution in two ways:
  • Configuring WebGUI for SSL (HTTPS)
    In most cases, you need to purchase an SSL Certificate from a Certificate Authority to run your website over https.
  • Customizing WRE Configuration
    The WRE comes preconfigured for the most common needs. However, the Apache configuration files can be customized to meet unusual requirements as well. Let's outline some of the possibilities below:
  • enabling mod_status
    server: debian, wre .084
  • Existing Site to WRE
    Here are instructions on how to migrate an existing site to the WRE.
  • How to Build the WRE on OpenBSD
    Here is a detailed log of what I did to build the WRE under OpenBSD 4.2. Install OpenBSD 4.2-RELEASE Add xbase42 to the sets installed, we need expat In 4.3-RELEASE expat will be part of base, this step is not required. After First Boot Login as "root" Add a normal user for yourself. Be sure to add this user to group 'wheel' Add a user called 'webgui'. Set shell 'nologin' Login Class 'daemon' Empty password Set the password so the user cannot login. Edit the sudoers file Uncomment the line to allow people in group 'wheel' to run all commands and set environment variables NOTE: We'll be adding the WRE's environment to our own login Set up your PKG_PATH Edit root's .profile to export PKG_PATH so we can use pkg_add(1) with the '-i' switch See for how to set up packages Install necessary packages pkg_add -i bash link /usr/local/bin/bash to /bin/bash pkg_add -i gmake pkg_add -i autoconf-2.61p1 Install wget so we can get files from the web Log out and log back in under your username (we'll refer to them as 'user' from now on) Build the WRE Make the /data directory Change the owner of /data to 'user' Get the WRE Download the WRE source to /data Extract the WRE source. It creates /data/wrebuild Update OpenSSL to 0.9.8g cd /data/wrebuild/source rm -rf openssl-0.9.7m wget tar zxphf openssl-0.9.8g.tar.gz rm openssl-0.9.8g.tar.gz cd .. perl -pi.bak -e's/openssl-0\.9\.7m/openssl-0.9.8g/' Build the WRE cd /data/wrebuild; ./ --all WRE is installed to /data/wre Fix permissions chown -R webgui /data/wre/var/logs chown -R webgui /data/wre/var/mysqldata/ Start the WRE and add a site Set up your environment For both users of the system: 'root' and 'user' Add this to .profile: . /data/wre/sbin/ Note the space between the . and the / Run the WRE Console for initial setup Source in the WRE environment. This will happen automatically next time we login (due to what we did above). . /data/wre/sbin/ Open web browser to where it tells you Update Perl Modules cd /data/WebGUI/sbin perl
  • How To Configure a Static, non-WebGUI site
    If you need to deploy a static-HTML, non-WebGUI site on a WebGUI WRE server, it's not too hard to do.
  • Installing WebGUI and WRE on a computer with no internet connection. (Manual Install of WebGUI using WRE)
  • - what it does is one of three scripts that is suggested to be setup as a cron. See WRE installation wiki for details.
  • Migration To WRE 0.8
    Verify that your backups are still working if you were using the that came with the previous wre, you may need to enable backups again. Also, I had to recreate the file /data/wre/etc/backup.exclude.
  • One WebGUI Multiple Sites
    Typically, each website has its own WebGUI database, but there are some instances where it is advantageous to have ONE webgui database to serve up all your domains. This means that additional sites will be added via the asset manager to your "master site", but accessed through a different domain or subdomain. Here's how:
  • Override Core Modules
    If you need to edit one of the WebGUI core modules, a safer way of doing this that will be upgrade-proof is to add an additional directory for your overrides. In the example below, I've suggested creating a site_lib directory in the WebGUI root.
  • port forwarding
    if you have SSH access to your server and if for some reason you are unable to open port 60834 to access wreconsole when installing wre, you can use port forwarding to access the site:
  • restoring from webgui upgrade
    During today's experience of a failed upgrade, I thought I'd write this...
  • Running separate instance of apache with WRE
    Let's define what we're going to accomplish.  This will all be done on a working instance of WebGUI using the WRE ( try it on a dev server first so you're not breaking your live site while you play ).  For this example I am using CentOS 5 with WRE 0.7.2 and WebGUI 7.3.22 already installed, up and running.  Here are our goals: 1. Install the apache, php, and php-mysql packages using yum. 2. Configure this instance of apache to listen on port 82. 3. Configure mod_proxy apache in the WRE to send all of the traffic for a new domain (vhost) to our OS based apache, transparently to the end-user.
  • startup scripts
    This was stripped from from for clarity
  • The WRE and your shell environment
    This article describes how to avoid polluting your shell environment with
  • Upgrade WRE (v0.8.x+)
    The following information is drawn from wre/docs/upgrade.txt.
  • What to do if privileges on the uploads directory don't seem to work
    This issue should be fixed in recent versions of the WRE 0.8.x via rewrite rules in the modproxy template file which check for the existence of a .wgaccess file. However, as of v0.8.5, the rewrite rule which checks for the .wgaccess file is wrong (see this support ticket). Replace the $ with a % in the 2nd rewrite rule to get this to work. Hopefully this problem will be addressed in the next release of WRE.
  • WRE Troubleshooting
    If you encounter errors with your WRE installation, here are some techniques to try when troubleshooting:
  • WRE-Building on FreeBSD 5.3
    These are notes taken while building the WRE 0.7.2 from source inside a FreeBSD 5.3-RELEASE jail. 
  • - what it does is one of three scripts that is suggested to be setup as a cron. See WRE installation wiki for details.
Most Popular | Recent Changes | Wiki Home
© 2023 Plain Black Corporation | All Rights Reserved