Firewall >> Portforwarding http/https to >> cloud.xxx.de
On cloud.xxx.de Nextcloud runs as virtual domain on Apache2 and is configured with A+ rating. On same host another virtual domain office.xxx.de is configured via reverse proxy to my internal OnlyOffice Document Server running on Nginx. Both domains are running on https in Apache2 using lets encrypt certs. The document server can be accessed from the outside:
When trying to open any document the iFrame content is blocked away in Safari:
Interestingly an unsecure http:// link is opend though I’ve never entered an http:// and in source code no http is visible. Even if http would be used, my Apache rewrites all http to https.
When trying to use Firefox no content is blocked but an nginx error page is shown:
Negative, the reverse proxy is encrypted with valid cert as you can see in the first screenshot. This is exactly why a reverse proxy is used. The internal server (http://192.168.0.103) is not accessible from internet and do not have a public DNS by design. The reverse proxy converts all http internal URLs to public https://office.xxx.de this works well when called directly. This works with other websites and dynamic webapps aswell. But somehow it’s not working with OnlyOffice.
yes but probably that isn’t sufficient. It looks like that the document server itself redirects inside of it to http.
So you need to do the ssl part of: https://github.com/ONLYOFFICE/Docker-DocumentServer too, and redirect to 443 or something sslish inside to OO.
The cheap “the proxy does the dirty work” doesn’t always do the job.
Indeed you need to enable OO https directly, even if self-signed (because you can ignore SSL status of the remote in the proxy). I have the same setup and OO support stated this earlier today.
I appreciate your energy but in enabling https in OO this still doesn’t work.
In detail: I’ve installed private cert. No public one possible due the fact that this is a server in the internal segment. The server is accessible now via https. Of course Firefox warns because self-signed but basically the server is up and running.
Alrighty, back to my config file. I’ve forgotten to add SSLProxyEngine Directive. After saving and restarting the next boom: The proxy server could not handle the request GET and showed errors during handshake. This is more worse than before without https.
Onlyoffice does not work behind a reverse proxy. IMHO this makes it unuseable for secure networks. Or I still missing something and we need an apache-woodoo master.
I’m currently suffering in a similar situation, and would really appreciate some help!
I have Nextcloud running via Apache on a server visible to WAN (cloud.XXX.com). Let’s call this server MIDGAR
I have installed OnlyOffice with Nginx on a second server on the same LAN, but clearly not visible to WAN. Let’s call this server MIDEEL.
I have been successful in using ProxyPass on Apache on MIDGAR to send traffic from office.XXX.com to MIDEEL with SSL authentication on MIDGAR using Let’s Encrypt.
Under this situation requests to office.XXX.com successfully resolve to OnlyOffice on MIDEEL with accepted SSL. However when trying to integrate into Nextcloud I am faced with a 302 error.
