Re: NGINX only for forwarding to LAN

2019-12-12 Thread pixel24
problem. I am not allowed to redirect the subdomain on the webserver: gw.mydomain.com --> WAN-IP from IPFire but must set an A-record in the DNA. gw A [WAN-IP from IPfire] now it works unencrypted. I will now get to the setup of LetsEncrypt. But for this I open a new threat. many thanks! Post

Re: NGINX only for forwarding to LAN

2019-12-12 Thread pixel24
My mistake! On IPFire (running NGINX) port 80 was closed. Now I'm a little closer. With: worker_processes 1; events { worker_connections 1024; } http { server_names_hash_bucket_size 64; include mime.types; default_type application/octet-stream; sendfileon;

Re: NGINX only for forwarding to LAN

2019-12-12 Thread pixel24
the line: server_names_hash_bucket_size 64; in the http-section fix the start-problem but when I try from outside to brwose to: gw.mydomain.com in the webbrowser firefox show me the status: connect to: http://192.168.XX.5 that can't work, can it? This address is not available in inetrnet Pos

Re: NGINX only for forwarding to LAN

2019-12-12 Thread pixel24
based on the default file, combined with your section, the file now looks like this: worker_processes 1; events { worker_connections 1024; } http { include mime.types; default_type application/octet-stream; sendfileon; keepalive_timeout 65; server {

NGINX only for forwarding to LAN

2019-12-11 Thread pixel24
et but nothing worked. Does this work at all? Can anyone help me? best regards pixel24 Posted at Nginx Forum: https://forum.nginx.org/read.php?2,286443,286443#msg-286443 ___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx