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: Getting started

2019-12-12 Thread James Read
On Thu, Dec 12, 2019 at 5:03 PM Francis Daly wrote: > On Thu, Dec 12, 2019 at 04:52:25PM +, James Read wrote: > > On Thu, Dec 12, 2019 at 4:42 PM Francis Daly wrote: > > Hi there, > > > > If not, "nginx -V" should show the "configure arguments", which will > > > show any --conf-path or --pre

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: Getting started

2019-12-12 Thread Francis Daly
On Thu, Dec 12, 2019 at 04:52:25PM +, James Read wrote: > On Thu, Dec 12, 2019 at 4:42 PM Francis Daly wrote: Hi there, > > If not, "nginx -V" should show the "configure arguments", which will > > show any --conf-path or --prefix that will indicate the default config > > file that nginx will

Re: Getting started

2019-12-12 Thread James Read
On Thu, Dec 12, 2019 at 4:42 PM Francis Daly wrote: > On Thu, Dec 12, 2019 at 04:34:17PM +, James Read wrote: > > On Thu, Dec 12, 2019 at 4:24 PM Francis Daly wrote: > > Hi there, > > > > If you do > > > > > > curl -i http://127.0.0.1/ > > > > > > what content do you get back? Is it from t

Re: Getting started

2019-12-12 Thread Francis Daly
On Thu, Dec 12, 2019 at 04:34:17PM +, James Read wrote: > On Thu, Dec 12, 2019 at 4:24 PM Francis Daly wrote: Hi there, > > If you do > > > > curl -i http://127.0.0.1/ > > > > what content do you get back? Is it from the file that you want it to be? > > > > I still get the Welcome to ngin

Re: NGINX only for forwarding to LAN

2019-12-12 Thread Francis Daly
On Thu, Dec 12, 2019 at 11:22:10AM -0500, pixel24 wrote: Hi there, > 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 Quoting my previous message: """ If you can report a specific problem -

Re: Getting started

2019-12-12 Thread James Read
On Thu, Dec 12, 2019 at 4:24 PM Francis Daly wrote: > On Wed, Dec 11, 2019 at 08:54:24PM +, James Read wrote: > > Hi there, > > > Access log shows that page hasn't changed http code 304: > > > > 127.0.0.1 - - [11/Dec/2019:20:46:42 +] "GET / HTTP/1.1" 304 0 "-" > > "Mozilla/5.0 (X11; Linux

Re: Getting started

2019-12-12 Thread Francis Daly
On Wed, Dec 11, 2019 at 08:54:24PM +, James Read wrote: Hi there, > Access log shows that page hasn't changed http code 304: > > 127.0.0.1 - - [11/Dec/2019:20:46:42 +] "GET / HTTP/1.1" 304 0 "-" > "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) > Chrome/79.0.3945.

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 {