Tukukkk

All -

Here is the scenario I'm looking at. I've got a site, www.mycompany.com, that is our application. It's a web-based program that users log into and it works fine. We've got a marketing site in Wordpress at about.mycompany.com. The site, on its own, works fine.

I've been directed by management to have the Wordpress site, instead of being a separate site being a "subdirectory" off of our current site. So I am in the process of getting the servers to work together so that when you go to www.mycompany,com/about, it will show our Wordpress site.

Here is the configuration information for each of the servers:

www.mycompany.com.conf file:

<VirtualHost *:80>

    Redirect / https://www.mycompany.com

    ServerName www.mycompany.com

    DirectoryIndex index.php index.html

    DocumentRoot /var/sites/prod1

    ServerAdmin myaddress@mycompany.com

    ServerAlias mycompany.com



    <Directory />

        AllowOverride all

        Require all granted

    </Directory>



</VirtualHost>



<VirtualHost *:443>

    ServerName www.mycompany.com

    DirectoryIndex index.php index.html

    DocumentRoot /var/sites/prod1

    ServerAdmin myaddress@mycompany.com

    ServerAlias mycompany.com



    <Directory />

        AllowOverride all

        Require all granted

    </Directory>



    ProxyPreserveHost On

    ProxyRequests Off



    SSLProxyEngine on

    SSLProxyVerify none

    SSLProxyCheckPeerCN off

    SSLProxyCheckPeerName off

    SSLProxyCheckPeerExpire off



    ProxyTimeout 2400

    ProxyBadHeader Ignore



    ProxyPass /about https://about.mycompany.com

    ProxyPassReverse /about https://about.mycompany.com



    SSLEngine on

    SSLCertificateKeyFile /var/keys/www.mycompany.com.key

    SSLCertificateFile /var/keys/www.mycompany.com.crt



</VirtualHost>

about.mycompany.com.conf file:

 <VirtualHost *:80>

    Redirect / https://about.mycompany.com/

    ServerName about.mycompany.com

    DirectoryIndex index.php index.html

    DocumentRoot /var/sites/about

    ServerAdmin myaddress@mycompany.com



    <Directory />

        AllowOverride all

        Require all granted

    </Directory>



</VirtualHost>



<VirtualHost *:443>

    ServerName about.mycompany.com

    DirectoryIndex index.php index.html

    DocumentRoot /var/sites/about

    ServerAdmin myaddress@mycompany.com



    <Directory />

        AllowOverride all

        Require all granted

    </Directory>



    ProxyPreserveHost On

    ProxyRequests Off



    SSLProxyEngine on

    SSLProxyVerify none

    SSLProxyCheckPeerCN off

    SSLProxyCheckPeerName off

    SSLProxyCheckPeerExpire off



    ProxyTimeout 2400

    ProxyBadHeader Ignore



    ProxyPass /about https://about.mycompany.com

    ProxyPassReverse /about https://about.mycompany.com



    SSLEngine on

    SSLCertificateKeyFile /var/keys/about.mycompany.com.key

    SSLCertificateFile /var/keys/about.mycompany.com.crt



</VirtualHost>

I also created a 'cors-access.conf' file to allow the domains to talk to each other:

Header set Access-Control-Allow-Origin "*"

MySQL is on a second machine that has port 3306 open and is able to be accessed no problem. Wordpress itself seems to work fine, so I don't think that's an issue.

In the event that it matters:
- I am using self-signed certificates for this testing. I'm not getting any errors related to security, but mentioning it just in case.
- I am using Apache 2.4.6-80 on CentOS 7.5 (1804).
- These machines are NOT open to the internet when I'm working on them. They (including my client) have IP addresses entered into their respective hosts files for resolution to keep my testing contained to myself.

I have configured Wordpress in the following manner:

WordPress Address (URL) - https://about.mycompany.com

Site Address (URL) - https://www.mycompany.com/about

Permalinks are set for 'Post name'

Almost all of my pages work fine with access except one:
https://www.mycompany.com/about/about-us/
This one gives me a 404 error.

I have looked in Wordpress and the page IS there so it isn't that simple. I've also reset and turned back on my permalinks in the event that would fix it and no difference there either.

What I DO suspect (and I'm not sure if I'm doing the Proxy/ReverseProxy wrong or something else) is that there is a 'conflict' between the '/about' of the ProxyPass/ProxyPassReverse and the 'about' in 'about-us'. Here is my reasoning why I suspect the problem is here:

• When I modify the 'about-us' page's Permalink to anything that does not START with the string 'about' (like 'us-about' or 'ab0ut-us'), I can get the page to work.


• I am also sure it isn't just this page acting odd. I thought that there might be something somewhere behind the scenes hiddon on the page that I don't know about causing the problem, so I created some brand new pages called 'About Test' (which created a permalink of 'about-test') and 'About 2' (permalink of 'about-2) and those pages threw 404 errors as well.

I'm guessing somewhere I need to put some kind of 'RewriteCond' or 'RewriteRule' so that the 'about' isn't being handled twice (or whatever is going on) but I'm not sure.

If any additional information/clarification is needed, please ask otherwise any direction or suggestions would be greatly appreciated!!

Thank you,

Charles

Edit -

My reputation is too low still to reply directly to your comment, Orlando P., so here's my reply to you.

You ask a very good question and I'm happy to clarify/expand. What will end up happening down the road is that our www.mycompany.com server is going to be behind a load balancer running several servers. Instead of running WordPress on the same box as those servers (keeping the need to maintain the file count down), I wanted to offload the WordPress to a separate server since it doesn't need nearly the amount of processing power that the app servers will.

The other constraint that I have being imposed on me by my executive team is that they don't want our marketing site to be on 'about.mycompany.com', but they are willing to allow the use of 'www.mycompany.com/about' to be used. So my idea was to setup 'about.mycompany.com' on a separate server and then use a proxy redirection to the other server.

Do you have a suggestion/place you can point me where I can use another method instead of proxy-ing where I can do what I'm going for? I'm looking into the 'Location' directive in Apache to see if I can use that to accomplish the same goal but if you have any suggestions, throw them out there. Thanks!!