It's this: https://redmine.pfsense.org/issues/13984

Resave the reverse proxy page as shown there.

Steve

@gertjan yeah because it doesn't come from some ipv6 link-local address ;)

@stephenw10

I don't have email notification enabled. I turn it on and check right now.

Setting that only does so for connections from the firewall itself. It doesn't affect connections form clients behind it.

@atafm2 yes on both counts. The pid is normally only there if it’s running so it must have crashed once. IIRC the stream memory is related to CPU cores/threads not RAM but we usually don’t need to adjust it.

In that situation it's likely Linode controls the actual VLAN config and the hosts within each VLAN do not see the VLAN tags etc. So I would not expect to need to use any VLAN config in pfSense directly.
However I've not used Linode in that way so I'm not sure exactly what they expose to the user.

Indeed the console does not require a login by default there. In general if you can access the local console on a machine you can bypass a login there anyway so that becomes a physical security issue.

Steve

@oldschoolrouterjockey said in SG1100 on 22.1 updated to 23.01, basically a brick:

PHP Errors:
[30-Apr-2023 00:49:25 Etc/UTC] PHP Fatal error: Uncaught TypeError: Cannot access offset of type string on string in /usr/local/pkg/pfblockerng/pfblockerng.inc:1013
Stack trace:
#0 /usr/local/pkg/pfblockerng/pfblockerng.inc(6466): pfb_build_if_list(true, false)
#1 /etc/inc/pkg-utils.inc(715) : eval()'d code(3): sync_package_pfblockerng()

Uninstall and reinstall pfBlockerNG

Download/install latest System Patches package.
Install all recommended patches.
Reboot.

@gstlouis Bad cookie? Try a private or different browser.
Could it be trying to redirect to https?

@richvalleywirelessisp Not here, I have often wondered why there is so much fuss around mbuf's as even on my busiest devices they remain extremely low, what type of usage tends to increase mbuf usage? If you find the answer to that question it might help you out aside from the obvious of increasing the limit.

Hmm, the difficult part there would be disabling the IPv6. That won't happen unless you have dynamic IPv6 and it loses it's address when the WAN goes down.
Mmm, I'm not sure how that could be done in the current code. 🤔

Thanks for your help so far,

what ever happened during last installation, I reinstalled pfSense and it works now!
As I tried to hack my own firewall and the logs were empty I recon there must be s.th. wrong...

And I gonna make a factory reset also on my switch after I made so much, some times stupid, changes on VLANs and routing forward and back...

FYI: I decided to use virtualization, because I'll need a witness Server later on and not to have too much hardware around...
I'm also not familiar to bhyve and not too deep into UNIX, but Installation is quit easy.
UNIX & bhyve needs so little resources, so you can run multiple Servers, web, DB, LDAP ... on one little 4Core Celeron (If you don't have too much users).

Thanks again for your support so far, maybe there will come up further questions...

Regards
Thorsten

@stephenw10 That seems to be what was causing my problems.... thank you!

The replacement for the NewBox works flawlessly... Guess we are tossing this one up to the who done it gods -_-

No that's fine at first boot. It can't check the remote pkg version until the dynamic repo data has been pulled in.

Thank you so much @stephenw10 . My boss insisted over and over and over again it was a PFSense issue, and while I was confident in the PFSense config, I, being the junior IT person I believed him. Your help got me the info I needed to convince him to look outside PFSense and wouldn't you know it, it was the windows Firewall that's his area that was the issue. The Windows firewall on the machines didn't allow ping responces outside their local subnet.

Thank you so much again @stephenw10 you rock!

@thebear Ah, the order was incorrect! Could have known that :(. Changed the order and will do some further testing; let you know!

Ah, good result.

Bad request like that implies the client has an invalid certificate. It may have just not pulled a new cert. Running: pfSense-upgrade -c would correct that.
If you still see errors send me your NDI in chat and I'll check it.

@cappie said in pfSense Plus 23.01 : Unable to gather system activity (1):

I linked to that earlier

Doh, missed that. 🤦