Local DNS Server interfering with issuing certificates

Here is the default block rule (on the WAN interface) for IPV4:

Shell Output - pfctl -vvsr | grep 1000000103

1000000103 is the rule identification number.
@5(1000000103) block drop in log inet all label "Default deny rule IPv4"
IPV6 rule is the same.

1 Like

Shell Output -
cat /var/log/filter.log | filterparser.php | grep block
Will list All blocked connection attempts EG: (short sample)

Dec  5 12:22:58 block igb0 TCP:S 89.248.172.140:51240 10.10.10.202:2444
Dec  5 12:22:59 block igb0 TCP:S 45.129.33.153:58799 207.55.114.xxx:20734
Dec  5 12:23:02 block igb0 TCP:S 89.248.172.140:51240 207.55.114.xxx:2444
Dec  5 12:23:03 block igb0 TCP:S 31.166.74.168:54454 10.10.10.202:445
Dec  5 12:23:12 block igb0 TCP:S 92.63.197.55:58251 10.10.10.5:18777
1 Like

@sionicion

EDIT: Images an non applicable questions removed to continue the thread on topic.

The goal here is to obtain and automate issuance of LetsEncrypt certificates to @sionicion's network. So it is on topic and within the scope of this forum.

Although I have successfully managed (Novell) clusters on municipal networks, I am not experienced with Kubernetes clusters specifically. There is a "certificate manager" involved here which is not part of pfSense distro. This may be complicating the process and I am convinced that we can get to the bottom of it and make this work for the OP.

(To Be Continued when OP has time)

2 Likes

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.