sbeaver has committed a fix just now - https://github.com/pfsense/pfsense/commit/055375927e013fb9227ea48cc7b2c3f7491fe33d

Will do it tomorrow :)

Hi cmb! I managed to config IKEv2 between 2.2.6 and 2.3. There are some gui issues I think on ipsec config page, see here: https://forum.pfsense.org/index.php?topic=105776.0 I did config manually via .conf files and it works like a charm now. Also upgrade from 2.2.6 to 2.3 correctly retains configs and it works. Problem was on new 2.3 install and new ipsec tunnel config creation. BR, Greg

@phil.davis: Well, what to say? I wish those "crash" messages displayed the actual PHP error message, rather than just a trace. Indeed, those aren't really helpful. Haven't had a chance to dig into why that type of "crash" doesn't include the PHP error, but that's irked me as well.

Just log spam, as noted in #4219.

gitsync to get fixed vpn.inc

Thanks! Guess I should have searched better.  Since I usually just lurk, my post count is low, I get one n00b freebie goof. :)

I was able to make it work from ssh by rmdir and the two left over directories in the error folder. Now it appears to be running but ever site produces a white page with no content. I see a no data received as well.

Probably this explains it why shared key worked: IPv4 Tunnel Network : The suggested default in the GUI of 10.0.8.0/24 is sufficient, but any random unused network inside of the RFC1918 space is recommended. For site-to-site shared key, only a /30 is used, not a /24, even if /24 is specified. Taken from: https://doc.pfsense.org/index.php/OpenVPN_Site_To_Site

https://github.com/pfsense/pfsense/commit/257fc849830aedf52338e84e489ad20e02f14179

I'm unlikely to add python

Agreed love the new look and redesign of gui. I still have a few package issues but over all loving it!

PR from  few weeks ago. No idea either :)

@NOYB: How about the enabled/disabled ex and check marks being red and green like they are in firewall rules.  Just a shading of the same color doesn't standout as well. In Firewall Rules the tick/cross indicates a pass/block rule. Currently the front Firewall Rules tabular display does not have a tick/cross column for enable/disable of the rule. So it might be a bit confusing for green/red to indicate pass/block in one context and enable/disable in another. Should the enabled/disabled colors be a different pair to the pass/block colors? Maybe blue tick (enabled - like now) and orange cross (disabled)? or?

Caught this one on squid install: [10/13] Extracting squid-3.5.12: …...... pkg: cannot rename //usr/local/etc/squid/errors/zh-cn.v4WYVKFe20xr to //usr/local/etc/squid/errors/zh-cn: Is a directory