In the original post I mentioned that BraveNet uses a reverse proxy and I had to add the following code to the WordPress config file:
if ($_SERVER[‘HTTP_X_FORWARDED_PROTO’] == ‘https’) $_SERVER[‘HTTPS’]=’on';
Apparently BraveNet had been working on this problem in the background and after I had contacted them about the issue in the second post they followed up (great customer service by the way) and let me know that they were implementing a fix on their end for that exact problem.
As of last Tuesday (June 30th), you no longer have to add the above code as the BraveNet web servers know when a client connection has been made with HTTPS and sets the variable to ‘on’.
They’re also looking at setting the port value correctly (WordPress doesn’t use this but some software does) in a future update.