December 12, 2019 01:12PM
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;
sendfile on;
keepalive_timeout 65;

server {
server_name gw.mydomain.com;
location / {
proxy_pass http://192.168.24.109;
}
}
}

I can connect from the outside to the web server :-) What surprises me however is that in the address line of Firefox my external WAN-IP of the firewall is located afterwards. Is this normal an ok?
Subject Author Posted

NGINX only for forwarding to LAN

pixel24 December 11, 2019 07:42AM

Re: NGINX only for forwarding to LAN

Francis Daly December 11, 2019 03:22PM

Re: NGINX only for forwarding to LAN

pixel24 December 12, 2019 11:02AM

Re: NGINX only for forwarding to LAN

pixel24 December 12, 2019 11:22AM

Re: NGINX only for forwarding to LAN

Francis Daly December 12, 2019 11:38AM

Re: NGINX only for forwarding to LAN

pixel24 December 12, 2019 01:12PM

Re: NGINX only for forwarding to LAN

pixel24 December 13, 2019 02:39AM

Re: NGINX only for forwarding to LAN

Francis Daly December 13, 2019 08:24AM



Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 121
Record Number of Users: 8 on April 13, 2023
Record Number of Guests: 421 on December 02, 2018
Powered by nginx      Powered by FreeBSD      PHP Powered      Powered by MariaDB      ipv6 ready