Monitoring, Management & Location Tracking

Running AMP's Apache Web Server on Different Ports

Aruba Employee

By default AMP's web server is configured to listen for https requests on port 443. (It also forwards any http requests on port 80 to port 443.) It's easy to configure apache to listen on additional ports. The following example describes adding 8080 and 8443 as https ports.

2 things need to be changed in /etc/httpd/conf.d/ssl.conf (nano is a good easy-to-use text editor that's included on the AMP):

1. Add Listen directives for the ports you want to listen to:

Listen 443
Listen 8080
Listen 8443

2. Add the ports to the VirtualHost:

<VirtualHost _default_:443 _default_:8443 _default_:8080>

After you make those changes and save the file, just restart Apache:

# service httpd restart

That will do it. In current versions of AMP (5.1 and 5.2) these changes will be overwritten during an upgrade, so we recommend that you save a copy of your config in /var/airwave/custom. In 5.3 the AMP will allow you to add your own custom configurations that persist beyond upgrades.

A further caveat: it is possible these changes may cause unexpected consequences, especially for VisualRF. Making these changes are not officially supported for AMP, so you should choose to do them cautiously.
By default AMP's web server is configured to listen for https requests on port 443. (It also forwards any http requests on port 80 to port 443.) It's easy to configure apache to listen on additional ports. The following example describes adding 8080 and 8443 as https ports.

2 things need to be changed in /etc/httpd/conf.d/ssl.conf (nano is a good easy-to-use text editor that's included on the AMP):

1. Add Listen directives for the ports you want to listen to:

Listen 443
Listen 8080
Listen 8443

2. Add the ports to the VirtualHost:

<VirtualHost _default_:443 _default_:8443 _default_:8080>

After you make those changes and save the file, just restart Apache:

# service httpd restart

That will do it. In current versions of AMP (5.1 and 5.2) these changes will be overwritten during an upgrade, so we recommend that you save a copy of your config in /var/airwave/custom. In 5.3 the AMP will allow you to add your own custom configurations that persist beyond upgrades.

A further caveat: it is possible these changes may cause unexpected consequences, especially for VisualRF. Making these changes are not officially supported for AMP, so you should choose to do them cautiously.

Version history
Revision #:
1 of 1
Last update:
‎06-06-2014 04:08 PM
Updated by:
 
Contributors
Search Airheads
cancel
Showing results for 
Search instead for 
Did you mean: 
Is this a frequent problem?

Request an official Aruba knowledge base article to be written by our experts.