Upgrading to FileWave 13+ from older Versions on Systems where Port 443 is used
Description
FileWave 13 introduced the Web Admin interface, which uses port 443 by default. If another service is already listening on port 443, the FileWave Server installer cannot complete until the conflict is resolved.
To resolve the issue, either move the other service off port 443 or configure FileWave Web Admin to use a different port before upgrading.
Directions
Configure FileWave to use a different Web Admin port before the upgrade as follows:
Mac / Linux
Edit /usr/local/filewave/apache/conf/httpd.conf and add the following line:
# Putting the last character in brackets is a trick to prevent Apache from issuing a warning if the file does not exist.
IncludeOptional conf/httpd_webadmi[n].conf
Create /usr/local/filewave/apache/conf/httpd_webadmin.conf with the following content:
Define WEB_ADMIN_PORT 20440
Restart Apache:
sudo fwcontrol apache restart
Then run the FileWave Server 13+ installer as normal.
Windows (Legacy)
WindowsÂ
Edit C:\Program Files (x86)\FileWave\apache\conf\httpd.conf and add the following line:
# Putting the last character in brackets is a trick to prevent Apache from issuing a warning if the file does not exist.
IncludeOptional "C:\Program Files (x86)\FileWave\apache\conf\httpd_webadmi[n].conf"
Create C:\Program Files (x86)\FileWave\apache\conf\httpd_webadmin.conf with the following content:
Define WEB_ADMIN_PORT 20440
Restart Apache from Command Prompt or PowerShell running as Administrator:
fwcontrol apache restart
Then run the FileWave Server 13+ installer as normal.
No comments to display
No comments to display