Search Engine: Elastic

Article ID: 129238, created on Aug 10, 2016, last review on May 31, 2018

  • Applies to:
  • Operations Automation


OACI VE console does not work.

The console shows the message:

Session Closed. Please click on Reset Console


OACH console requires a series of configuration entries on Branding and Virtuozzo hosts. Due to various reasons, the configuration may get broken as a result of reconfiguration - brands relocation, Apache reconfiguration, Virtuozzo nodes reinstallation, etc.


The check-list below will help to validate the VE console configuration:

  1. Each host that contains a brand should have the following configuration files in place:

    # cat /etc/httpd/conf.d/oaci.conf
    SSLProxyEngine On
    ProxyVia Off
    ProxyRequests Off
    Order allow,deny
    Allow from all
    Header set X-Forwarded-Proto https ProxyPass "/oaciws/22" "ws://" ProxyPass "/oaciws/23" "ws://"

    The bottom lines are formed with the help of backnet IP addresses of the Virtuozzo hardware nodes.

    The configuration file should be included into the Apache configuration tree:

    # grep oaci.conf /etc/httpd/conf/httpd.conf
    Include conf.d/oaci.conf
  2. Each Virtuozzo host should have Apache configuration file /etc/httpd/conf.d/oaci.conf, describing OACI virtual host that should be located at /var/www/oaci. The virtual host includes a single .htaccess file to forward the incoming requests to web sockets.

    # cat /var/www/oaci/html/.htaccess
    RewriteEngine on
    RewriteRule ^websocket/([^/]+) ws://$1/websockify [P]
    RewriteRule ^oaciws/([^/]+)/([^/]+) ws://$2/websockify [P]
  3. All Branding and Virtuozzo hosts should have mod_proxy_wstunnel RPM package installed, with additional Apache configuration file to load the module:

    # cat /etc/httpd/conf.d/proxy_wstunnel.conf
    LoadModule proxy_wstunnel_module modules/

    Note: RedHat7/CentOS7 have mod_proxy_wstunnel shipped with httpd by default. RPM package mod_proxy_wstunnel is not required on servers with RedHat7/CentOS7.

  4. The request to access VE console arrives at the Branding host, which is proxied to the web sockets running on Virtuozzo hosts. Connectivity between Branding and Virtuozzo on port 80 is required to make this work.

    Log files to check for possible errors:

  5. Apache service should be running on all Virtuozzo and Branding nodes:

    # service httpd status

5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07

Email subscription for changes to this article
Save as PDF