Looks like whimsy.apache.org is defined in one of the proxy modules: grep -i whimsy.apa proxy*.yaml proxy1-us-west.apache.org.yaml: - 'whimsy.apache.org' proxy1-us-west.apache.org.yaml: - 'whimsy.apache.org' proxy4-us-west.apache.org.yaml: servername: 'whimsy.apache.org' proxy4-us-west.apache.org.yaml: access_log_file: 'whimsy.apache.org.http_access.log' proxy4-us-west.apache.org.yaml: error_log_file: 'whimsy.apache.org.error.log' proxy4-us-west.apache.org.yaml: servername: 'whimsy.apache.org' proxy4-us-west.apache.org.yaml: access_log_file: 'whimsy.apache.org.ssl_access.log' proxy4-us-west.apache.org.yaml: error_log_file: 'whimsy.apache.org.error.log' proxy4-us-west.apache.org.yaml: # ErrorDocument 500 http://www.apache.org/dev/service_unavailable.html?site=whimsy.apache.org&code=500 proxy4-us-west.apache.org.yaml: # ErrorDocument 502 http://www.apache.org/dev/service_unavailable.html?site=whimsy.apache.org&code=502 proxy4-us-west.apache.org.yaml: # ErrorDocument 503 http://www.apache.org/dev/service_unavailable.html?site=whimsy.apache.org&code=503
If it does not use the proxy server anymore, perhaps it should be removed from the configs? On 5 June 2016 at 20:51, Sam Ruby <[email protected]> wrote: > On 2016-06-03 14:33 (-0400), Sam Ruby <[email protected]> wrote: >> This weekend I plan to update the DNS records to make whimsy.apache.org >> point to whimsy-vm3 instead of resolving (through the proxy) to >> whimsy-vm2. Once those changes are live: >> >> 1) whimsy2.apache.org can be used to access whimsy-vm2. You will likely >> get a certificate error as the hostname will not match the certificate. > > This does not appear to work; presumably there would need to be a proxy > server update to make it work; I'm inclined to simply return the VM instead. > >> 2) whimsy.apache.org can be used to access whimsy-vm3. Again there will >> likely be a certificate error initially until I go through and >> re-request a certificate from letsencrypt. Should I run into problems, >> I may need to back the DNS changes out until I resolve the problem. > > This is now working, and the certificate has been updated. > >> 3) whimsy3.apache.org will continue to be able to access whimsy-vm3. > > This will continue to work. > > - Sam Ruby >
