Hi Francis, thanks for the details. I guess the trick is first to bypass a QNAP internal redirect to the NAS GUI (if possible or to integrate it on the first request). And second to to adapt the login request the right way. (btw: I try to avoid to change the qnap service, because of the regular QNAP firmware updates.) For the first topic the internal network traffic analysis from Firefox shoby no.1 - Nginx Mailing List - English
I've been trying to reach my QNAP NAS from internet via reverse proxy on Raspberry Pi. Beside the stand alone QNAP a owncloud installation should run as well on the RPi. The plan was to use subdirectories to access both (https://example.com/nas and https://example.com/owncloud). Subdomains are not possible. Even if I leave out the owncloud installation it won't work to access the NAS via subdirby no.1 - Nginx Mailing List - English
Hi Kenkron, I tried it on a RPi with the instructions from http://www.aelog.org/install-owncloud-in-a-subdirectory-using-nginx/ and it works for me. Just change the root directory and collect the rewrite rules into a location block with /owncloud prefix. Regards no.1 (a real nginx rookie)by no.1 - How to...