On Mon, Mar 15, 2021 at 07:11:54AM -0400, bubugian wrote:
Hi there,
there have been some mentions of QNAP on the list in the past.
I'm not aware of any QNAP owner actually following up with a working
recipe, though.
> location /qnap{
>proxy_pass https://192.168.1.10;
>}
You probably wa
I'm trying to hide my QNAP NAS behind NGINX... without success.
With more attention I discover that with
server {
listen 80;
listen [::]:80;
access_log /var/log/nginx/reverse-access.log;
error_log /var/log/nginx/reverse-error.log;
location /qnap{
proxy_pass https://192.168.1.10;
}
}
wh
Hi,
is there any messages in error.log file?
While I'm here could you guide me - is there any specific reason to
use a back slash instead of a very common forward slash?
Thanks.
--
Sergey Osokin
On Sat, Mar 13, 2021 at 04:52:01PM -0500, bubugian wrote:
> Hi GROUP !
>
> I've a problem with NGI
Hi GROUP !
I've a problem with NGINX (reverse proxy).
All work perfectly if I assign internal server to root:
server {
listen 80;
listen [::]:80;
access_log /var/log/nginx/reverse-access.log;
error_log /var/log/nginx/reverse-error.log;
location /{
