Messages

yes, sorry it was a typo. address.

Many Thanks !

JC

Hi,

I am setting up some container  in a docker IPVLAN L3, within a host.
I have added my host as a gateway for the subnet, in opnsense. (lesson learned)
I have added an explicit outbound NAT rule with source address my docker network  subnet and translation target my WAN net

Ping will lose 100% of traffic.
All outgoing connections get stuck.

I can see all my outgoing traffic in green and matched against a rules in firewall. There is no blocked traffic.

Can you guys help me figure out what am I missing ?

Thanks.

JC

Hi,

I have a fresh 25.2 instalation running as VM in Proxmox. I have pi-hole in a separate VM

I have open WAN to allow 80/443 from want to my opnsense ip instance.
I have created forwarding rules to redirect 80/443 traffic from wan to my opnsense server.
I have dynamic IP address, currently ddns via AWS Route53 via a hosted zone.
Wireward works perfectly.

Using the plugin

I have enabled the plugin
I have created an account
I have created a challenge  HTTP01 a per multiple suggestions due to DNS on pi-hole. I have set up HTTP Service to automatic port forward. Interface is WAN

I create certificate common name --> my domain in route53, accme account --> let's encrypt

I get this eventually in ACME Log

2025-02-12T16:02:10    acme.sh    [Wed Feb 12 16:02:10 CET 2025] Sleeping for 10 seconds and retrying.
2025-02-12T16:02:10    acme.sh    [Wed Feb 12 16:02:10 CET 2025] Cannot init API for: https://acme-staging-v02.api.letsencrypt.org/directory.
2025-02-12T16:02:10    acme.sh    [Wed Feb 12 16:02:10 CET 2025] Please refer to https://curl.haxx.se/libcurl/c/libcurl-errors.html for error code: 6

Any  hints how can I overcome this problems ?

After doing this, internet connectivity fails and I have to reboot opnsense......pretty bad actually.

Thanks

JCG