SharePoint with Apache mod_proxy

The Apache Software Foundation provides a reverse proxy module named mod_proxy and mod_ssl (which extends functionality into SSL). This is a non-authenticating reverse proxy similar to function to Microsoft’s IIS Application Request Routing module. This article will cover getting a single Web Application on a single SharePoint server behind the reverse proxy over SSL on port TCP/443. We will be starting from the same VM as used in the previous blog post about using CentOS and iptables, so familiarize yourself with that before continuing as that will be the base configuration moving forward. By now I will assume that you’re familiar enough with vi to know how to save files. In addition, I will assume that the Domain Controller on the Hyper-V Internal vSwitch is at and the SharePoint server is at In addition, our SharePoint server is going to have an SSL certificate of, and of course that is what our Web Application will be. This particular SSL certificate has been issued from StartSSL (it’s free).

The first step will be to modify the networking on the CentOS virtual machine.

Add a new line:

This will disable the DHCP client ( dhclient) from automatically adding the DHCP servers DNS information to /etc/resolv.conf (which is what allows the VM to automatically resolve domain names). Instead, we’re going to manage that using the internal Domain Controller over eth1!

Add a new line:

Next, let’s edit the resolv.conf

Change it so it reads:

The next step is to bring up and down both interfaces.

Once both interfaces are back up, your Windows Servers should continue to have name resolution connectivity to the Internet. In addition, /etc/resolv.conf should show the static settings you inputted ( cat /etc/resolv.conf). In addition, you should be able to ping, from the CentOS VM, to the internal servers by IP and FQDN. Next, we need to install a few packages on CentOS. Apache (for mod_proxy), mod_ssl (for SSL support), and bind_utils (for dig, similar to nslookup on Windows).

We now need to add a couple of new firewall rules:

And save the rules:

This allows iptables to accept SSL traffic to the reverse proxy (locally).

The next section will not be quite as easy. We will be dealing with SSL certificates on the CentOS VM. In order to do this properly, we’ll need to upload certificates to the CentOS VM and unlike Windows, it isn’t quite the point-and-click affair with PFX.

Most SSL certificate vendors will offer an unencrypted private key as well as public key file. You’ll want both of these. In addition, you’ll also want the appropriate Certificate Authority SSL certificate bundle (this contains the public certificate chain for your SSL certificate). If your SSL vendor does not offer these file types, you’ll need to use OpenSSL to convert the files to the appropriate file formats. For reference, here will be my file names:

Unencrypted private key: sharepoint.key

Public key: sharepoint.cer

CA bundle: startssl-bundle.pem

In addition to this, specifically for mod_ssl, we will need a single file that contains both the public and unencrypted private key in a single file. It should be in the following format:

You can use a program like Notepad++ to edit the sharepoint.key and sharepoint.cer files to create the new files with the public and private key contained within it. This will be the Public-Private key bundle, and saved as sharepointpubpriv.crt. Now all of these files need to be transferred to the CentOS VM. In order to do this, we’ll use a protocol called SCP. This protocol allows you to transfer files over SSH. Thanks to our default iptables rules, SSH is already open on our eth0 interface! Grab a copy of WinSCP and copy these files over to a directory (e.g. /root).

The next step is to copy over the files to the appropriate default locations.

Now, using vi, we need to configure httpd.conf (the primary Apache configuration file).

Make sure the following lines exist:

In my example, I’ve removed the Listen 80 as well as the default VirtualDirectory. This is a reverse proxy intended to only listen on 443 and serve requests to our internal SharePoint server. There are many other settings within here that you can modify and likely should modify, but this is not an in depth lesson on Apache security.

The next step is to modify the ssl.conf file.

LoadModule ssl_module modules/ should be present at the top of this configuration file.

Instead of providing you specific lines to set, here is the entire configuration. Again we’re using my example domain here, so adjust to fit your needs.

Make sure at the end of the ProxyPass and ProxyPassReverse lines you end them with a “/” at the end of the path, otherwise relative paths will not be returned properly to the reverse proxy and you’ll see unexpected results.

Once the changes are configured, run

Any errors will be logged in the log files at /var/log/httpd/error_log and sharepoint_ssl_error_log. To watch error_log  in real time, run:

The last step would be to edit the hosts file on any client computer to target, in this case, at the IP of the eth0 interface. If everything goes well, we should be prompted for credentials and let right through to the SharePoint site!


  1. Hi Trevor,
    Very interesting way to approach this problematic.
    I wanted to know if you could do some load balancing with that but I found out the solution myself so here is how to do it in case you have multiple WFE’s

  2. Hello Trevor,
    thanks a lot for sharing that information. I am actually trying to reverse-proxy the sharepoint to give access from outside. The connection is https (on the proxy server with mod_proxy) and https on the sharepoint server. The proxy also serves a Wiki and a bugtracking system to the outside world therefore ProxyPass / is not possible. Do you probably know a solution to use something like

    ProxyPass /sharepoint https://external.url/sharepoint

    I have tried a lot including mod_rewrite but it failed.



    • Make sure you’re using mod_ssl and have the SSL certificate in use by SharePoint installed and configured on the Apache server. Are you able to allocate multiple IP addresses to the Apache server? That may allow you to use ProxyPass / using VirtualHosts. You could potentially also use SNI if you cannot allocate multiple IPs.

  3. bad thing is that we have only one free external domain/ip with port 443 to serve multiple services via the proxy module. The / in virtualhosts leads to a customer landing page with authentication to access the links behind the proxy.

    Probably there is no way arround AAR

  4. I wan’t to use it on apache 2.4.6. I know some lines change because of the version, but httpd still does not want to start. Do you have a working code for 2.4.6?

  5. Pingback: Route request from apache web server to SharePoint * VPN SSL Online

  6. Hi, thanks for your useful and clear how to. I have some question if you have time.
    I’m proxying sharepoint from SSL to http (sharepoint). Homepage works well but when I try to access subsites I get the warning from the browser that some parts are not secure.
    I try to proxy also the subsite but do not change anything.


  7. Thanks for the Doc ..

  8. Hello Trevor,

    does this guide work for all IIS website configured in Windows Authentication? I’m trying to proxying with Apache a Dynamics Navision host, but i can’t make it work with only Windows Authentication (with Basic also, works instead)

    Do you have any suggestions?


  9. Dear Seward,

    I am using rhel server for reverse proxy , all are working fine with Active directory, but recently client has changed form AD to LDAP(claim based authentication ) for share point 2010 on windows server using same NTLM feature.

    But now it’s not working can you please HELP.


    Bhanu K

Leave a Reply