@chudak
If NGINX runs on a device behind pfSense within a private subnet you have to forward 80 and 443 to it, of course.

Firewall > NAT > port forwarding.
Add a rule:
interface: WAN
protocol: TCP/UDP
destination: WAN address
destination port: HTTP
Redirect target IP: NGINX IP
Redirect target IP: HTTP

Add a second rule for port 443 (HTTPS).

Ensure that the webGUI is not listening on port 80/443. System > Advanced > Admin Access > TCP port

@stephenw10
Thanks alot
It is working properly now !
You saved me

Ok. You still need to do something to avoid route asymmetry. So that would be either putting LAN onto a pfSense interface or moving the pfSense WAN to a different interface on the Mikrotik router.

@mayonnaise Yeah!! Good Luck, the reason I asked about separation is to see if this was separated over ISP or just local network

@Spooke Thank you for the information. I have erro and I will set them up that way.

@stephenw10 tnx this is exactly what happened, and i used the solution purposed by @viragomann , which is in the end same of yours and it works fine thanks guys!
You're precious as usual!
Respect!

@stephenw10 Done

Ted

Hmm, well there's no config option for that. Some coding would be required it looks like.

@it_ib said in Log Collector:

Humio and the Falcon LogScale Collector

Not seeing any FreeBSD builds that might be applicable.

If you configure notifications you should get that. You won't see a notice for shutdown but you would be upgrades and for boot-up complete.
https://docs.netgate.com/pfsense/en/latest/config/advanced-notifications.html

Steve

The blocked traffic you showed is on the WAN. To pass that traffic you would need to a firewall rule on the WAN. That screenshot shows a rule in LAN.

However if you are trying pass the VPN traffic to the Cisco router behind pfSense you need to add a port forward. By default that will add a firewall rule for you:
https://docs.netgate.com/pfsense/en/latest/nat/port-forwards.html#adding-port-forwards

Steve

Hey, Sorry for the late.

After the last tests I tried to map one vlan on the LAN NIC and It's OK. So the problem was either the nic used for the VLANs or the switch port used.

Thanks

@stephenw10 had a backup machine I upgraded... tested and then upgraded active system.

Still have a question on if backup config file should be in root of FAT32 partition or in E:\config\ -> I had it in both.

Process I followed was to:

change interface to em0 pre-upgrade and disable the shellcmd script. Take backup and upload to usb key Connect my Bell MTS ONT to pfSense Reboot and install new

This found the config, recognized and got internet DHCP address for WAN on em0 and installed packages as there was an active internet connection.

No other config changes were needed.

This has been quite a journey from when I first started this thread! Glad to see my script is no longer needed.

Works ok now for some reason!

@alteredstate said in Deleted pfSense Package Settings Appear in Backup:

@bmeeks What happens when I import the backup containing config settings for packages that are not installed? Will those config settings become null and void or appear in the next backup? I would like for said config settings to disappear when I import the backup.

If you import a backup with those settings in it, then they will return and stay. You would have to repeat the process of installing the package again, unchecking the box to retain settings, then removing the package.

You may find it easier to simply edit the config.xml file directly before importing it. If you have any familiarity with XML, then you can very quickly see how to remove the section pertaining to a given package by simply studying the layout of the config.xml file and deleting the appropriate section.

@Matt_Sharpe said in Log Rotation Issue:

Another query would be, is it possible to move the /var/log partition to a dedicated disk in PFsenses?

It's possible in FreeBSD but there isn't any supported way to do it in pfSense. Someone familiar how disks/partitions works in FreeBSD should be able to set it up without too much trouble, but it may also take some manual adjustments in the code since pfSense has to make a lot of assumptions in that area.

That would work.

The default config for any Netgate device uses the first port as WAN. I would always recommend using that because it makes reinstalling or resetting far easier.
https://docs.netgate.com/pfsense/en/latest/solutions/netgate-4200/io-ports.html#networking-ports

So:
Port1 = WAN
Port2 = LAN
Port3 = DMZ
Port4 = WiFi perhaps

@stephenw10 I noticed that this happened whenever I enabled a NAT rule, so I followed this tutorial https://docs.netgate.com/pfsense/en/latest/recipes/port-forwards-from-local-networks.html and changed the NAT +Proxy for Pure NAT, and I checked both checkbox options... it worked, now logs no longer appear every 15 minutes... thanks