For example: Įdit all SSL virtual host files inside the /opt/bitnami/apache2/conf/vhosts/ directory and modify the value specified in the VirtualHost directive. To change the port number, follow the steps below:Įdit the /opt/bitnami/apache2/conf/bitnami/nf file and modify the value specified in the VirtualHost directive. Restart the Apache server for changes to take effect: $ sudo /opt/bitnami/ctlscript.sh restart apacheĪpache listens for HTTPS requests on port 443. NOTE: Do not edit virtual host files containing the SSLEngine on directive. For example: Įdit all non-SSL virtual host files inside the /opt/bitnami/apache2/conf/vhosts/ directory and modify the value specified in the VirtualHost directive. For example: Listen 8080Įdit the /opt/bitnami/apache2/conf/bitnami/nf file and modify the value specified in the VirtualHost directive. To change the port number, follow the steps below:Įdit the /opt/bitnami/apache2/conf/nf file and modify the value specified in the Port directive. Under the default configuration, Apache will listen for HTTP requests on port 80. Approach A: Bitnami installations using system packages HTTP port Refer to the FAQ for more information on these changes.
The output of the command indicates which approach (A or B) is used by the installation, and will allow you to identify the paths, configuration and commands to use in this guide. To identify your Bitnami installation type and what approach to follow, run the command below: $ test ! -f "/opt/bitnami/common/bin/openssl" & echo "Approach A: Using system packages." || echo "Approach B: Self-contained installation."
On account of these changes, the file paths stated in this guide may change depending on whether your Bitnami stack uses native Linux system packages (Approach A), or if it is a self-contained installation (Approach B). NOTE: We are in the process of modifying the file structure and configuration for many Bitnami stacks.
0 kommentar(er)
