I'm having trouble with getting NC to load the connector. My setup is: DocumentServer -->Apache Reverse Proxy (Handles HTTPS certs as well) --> Outside world. When going to https://onlyoffice.mydomain.com the page loads and says everything is well and good.

Now when putting that direct address into NC, the connector never loads, doesn't give any error message or anything. It shows up with a blank white page. One other thing to note, when I go to NC on the internal IP address and then put the DocumentServer internal IP address into the NC connector admin page, everything loads and works 100% as it should. That makes me believe it is something to do with my reverse proxy setup. Here is that code for my virtual host in Apache:

The Document server is only accessible directly from an internal IP. All external websites for my services are served access through an apache webserver. This keeps flow of traffic to only one server and IP address. Nginx on the document server is not accessible or serving up the domain for onlyoffice-document server.

Hello stansmith!Using custom port doesn't support by OnlyOffice, 80 port only. I suppose there is a problem.As an example you should take a look how as it is realized in nginx reverse proxy.In nginx config we have to set:

Correct, NC=Nextcloud. I am not using Apache for anything other than a reverse proxy. Nginx is used on the document server. This way the document server will run with all defaults as comes installed and Apache only handles the forwarding and routing to the domain name. Since I am able to load https://onlyoffice.mydomain.com and the site loads along with other tests I've done using only the domain. It makes me think that there is a setting in my reverse proxy setup that I don't have in the configuration. Something that needs to be set to help route traffic through the reverse proxy. I conclude this because when I take out the Apache Reverse proxy and us the setup on my internal IP addresses only, everything loads and works as expected.