guglfield.blogg.se

Filemaker server 12 ports
Filemaker server 12 ports







#Filemaker server 12 ports upgrade#

Sdiff -l $PROXYSAVE $PROXYCONF | cat -n | grep -v -e '($'Ī possible problem with this approach is that either later Server upgrades might blow out these changes, or the Server upgrade may stumble due to the non-standard configuration.Īnother option may be to disable the proxy from starting in the first place. e 's/RequestHeader set X-Forwarded-Port "443"$/RequestHeader set X-Forwarded-Port "9443"/' \Įcho "The file" $PROXYCONF "was succesfully modified" e 's/ServerName \$serverName:443$/ServerName $serverName:9443/' \ e 's/RequestHeader set X-Forwarded-Port "80"$/RequestHeader set X-Forwarded-Port "8080"/' \ e 's/ServerName \$serverName:80$/ServerName $serverName:8080/' \

filemaker server 12 ports

# Fix LISTEN, VIRTUALHOST, and REQUESTHEADER statements. # Changing the virtual host macros not required, but keeps things consistent. # We really only want to replace once for each pattern, but sed is a bit awkward about that, Will ask if ok to overwrite existing file if present. PROXYCONF="/Library/Server/Web/Config/Proxy/apache_nf"Įcho "This script must be run as root" 1>&2 # simon_b: fixed several patterns so that its safe if run more than once I’ve done this often enough that I’ve finally come up with a full sed based shell script to make these changes: #!/bin/bash Once you have the file open in an editor, make the following changes.įor each of these directives using port 443 or 80: The configuration file for this can be found at:

filemaker server 12 ports

One option to avoid this conflict is to modify the proxy configuration to no longer listen on these ports. This is problematic if you want setup something outside of Server (e.g., FileMaker Server) that needs to attach to ports 80 or 443. Unfortunately, the new proxy setup has the proxy always listening (attached) to ports 80 & 443, even if the sites in Server GUI are disabled and the Web service is off. In particular, an instance of Apache is used as a proxy to any ‘backend’ copies of Apache. Apple’s macOS Server 5.x has a rather different Apache configuration compared to the core macOS setup or those used in previous versions of Server.







Filemaker server 12 ports