@virgiliomi ok thank you ill check it out.... I appreciate it... due to no work.. I cant afford anything,... and people hoarding food and the damn toilet paper... I appreciate it and ill check it out (:

There aren't any plans to migrate from one to the other since they operate in much different ways.

@johnpoz said in Cert Manager Export Password: See the popup I showed where it says to look in profiles - did you miss that? It is a very valid point. It is easy to miss. But I haven't. Going back to the two things I have tried. If using the unencrypted p12 (which I know it is not meant to work): when I click on it, I see the pop up at the bottom saying that I have to go to my profiles to add it. If I go to general-->profiles I can see it there, I can click to install it, enter the pin code, and then I get stuck waiting for the password. But the p12 does get sent to profiles and an install can be attempted. when using the encrypted version, nothing happens when I click on the p12 file. When I say "nothing", I mean as if I had not touched the screen at all. No error, no "open with" menu, nothing. UPDATE: I have noticed that you used the Windows version of openssl. So just for the sake of it, I decided to install it and give it a shot. Surprisingly, it worked this time. Thinking that there can't be a difference between the two openssl, my head pointed towards the transfer between my raspbian and my Windows computer. Per default winscp transfers text file, and apparently doing this messed up the base64 and made it unusable for the encrypted version. After repeating the process with a binary transfer mode, I could import that encrypted p12 as well. So in the end, I could solve the problem and I hope this can help someone else. Thanks a lot @johnpoz for pointing me in the right direction. Without your screenshot I wouldn't have thought about looking into that and find the root-cause.

Of course You already did. When you visit the console, you activated that script. ( maybe without knowing it )

I split this off into its own thread so it doesn't take over the other one.

i replied in my other thread about the alias is fixed by reinstalling the firewall on my SG 3100 back to stable and not restoring ANYthing previously. entirely rebuilt from scratch i am now running sg 3100 on 2.4.4-RELEASE-p3 (arm) but have the same issue as i originally posted in this thread. on the stable release, i have spent hours on trying to figure this out. in reading on redmine https://redmine.pfsense.org/issues/6028 if i am reading this correctly this affects ALL versions of Pfense? i have been using Pfsense for the past 3-4 years and never experienced this. leads me to two things. is the image file for the sg 3100 contain issues my SG 4220 and SG 2220 did not have? because i have been using these same rules, and yesterday they were built from scratch not restored from a previous firewall.. if this is the bug i just need to know that so i understand its being worked on thank you Sir

So a good example would be something like this: pfctrl -sr currently prints out the rule set and userrules anchor (anchor "userrules/*" all) is empty. I have confirmed with a pfctrl -a userrules -sr which returns nothing. I then added the following: echo "pass in quick on em0 inet proto tcp from 192.168.1.7 to any port = 32400 flags S/SA keep state" | pfctl -a userrules -f - when I run pfctrl -a userrules -sr after this I get: pass in quick on em0 inet proto tcp from 192.168.1.7 to any port = 32400 flags S/SA keep state The rule doesn't work though and it doesn't display with a pfctrl -sr either. I can't see what I am specifying wrong, I have tried calling the anchor with and with out the /* in quotes a few times and it places the new rule under the userrules anchor as displayed with pfctl -a userrules -sr each time. I can clear it with pfctl -a userrules -Fr as well. Given this example can you see where I have gone astray? Thank you for your help.

Thank you, I'll keep that in mind for future. I understand why I had confusion and the replies have helped clear it up for me. Again thank you Jim and everyone that helped.

@jimp Thank you!

Today I updated pfsense to the version "2.4.5-RC (amd64) built on Thu Feb 27 00:05:35 EST 2020" and the problem with Dynamic DNS is gone. Thanks!

@jimp i try to to customize the code for my Owen purpose still it don't run after i gate the code

It has a well view, what did you use to improve your traffic graph? I still have some problems with and even more when I try to upgrade my Ip man is such horrible haha. I like you css style, well done bro!

I didn't get an error message, but bumping from 0221.1500 to 0225.2100 took me a solid 30 minutes. Not quite sure what the hold up was.

They are on a timer now and not triggered by any specific change as before. Keep an eye on Github and Redmine and see if anything interesting changed between what you have and the current one.

If it makes it into OpenSSH sshd in the base system FreeBSD, perhaps. But doubtful.