Messages

1

General Discussion / Re: acme.sh www.mydomain.com is not an issued domain, skip

« on: October 12, 2022, 09:16:51 am »

I could solve my issue by resetting the ACME Client like fraenki described on github.
https://github.com/opnsense/plugins/issues/3154

OpnSense -> Services -> ACME Client -> Settings -> Reset ACME Client

After that I could successfuly automaticaly renew all certs.

Thanks all 

2

General Discussion / Re: acme.sh www.mydomain.com is not an issued domain, skip

« on: October 07, 2022, 12:35:24 am »

Dou you think this is a Bug? I have checked the known issues at the Github page, but i didn`t find anything about this. 

https://github.com/opnsense/core/issues

Should I write a bug report?

3

General Discussion / Re: acme.sh www.mydomain.com is not an issued domain, skip

« on: October 02, 2022, 12:31:41 pm »

really no one with the same issue?

4

General Discussion / [SOLVED] acme.sh www.mydomain.com is not an issued domain, skip

« on: September 09, 2022, 02:52:38 pm »

Hi guys,

since a few weeks I am not able to automaticaly renew Letsencrypt certificates.

I have increased the loglevel to "debug 3" but this is all I can see in the logs:

Code: [Select]

2022-09-09T14:42:01 acme.sh [Fri Sep 9 14:42:01 CEST 2022] 'www.mydomain.com' is not an issued domain, skip.
2022-09-09T14:42:01 acme.sh [Fri Sep 9 14:42:01 CEST 2022] Renew: 'www.mydomain.com'
2022-09-09T14:42:01 acme.sh [Fri Sep 9 14:42:01 CEST 2022] DOMAIN_PATH='/var/etc/acme-client/home/www.mydomain.com'
2022-09-09T14:42:01 acme.sh [Fri Sep 9 14:42:01 CEST 2022] ACME_DIRECTORY='https://acme-v02.api.letsencrypt.org/directory'
2022-09-09T14:42:01 acme.sh [Fri Sep 9 14:42:01 CEST 2022] Using config home:/var/etc/acme-client/home
2022-09-09T14:42:01 acme.sh [Fri Sep 9 14:42:01 CEST 2022] Running cmd: renew
2022-09-09T14:42:01 acme.sh [Fri Sep 9 14:42:01 CEST 2022] Using server: letsencrypt
Very interessting is that the manual update with the button "issue or renew certificate" is working fine, Only the automated renew process is not working.

I have found some older similar issures, but the solution there was to update to the latest version witch is older that my version.

I there anything that I can do to analyze this deeper?

OPNsense 22.1.10-amd64
acme.sh 3.0.4 with DNS authentication

5

General Discussion / Zabbix Proxy compiled without IPMI support

« on: May 09, 2022, 02:20:40 pm »

Hi all,

I try to monitor my Server Hardware (Fujitsu IRMC Board) via OPNsense (Zabbix Proxy Plugin).

when I try to activate the Zabbix Proxy IMPI Pollers under Services -> Zabbix Proxy -> Settings

then the Zabbix Proxy service is stopped, the log file shows:

Code: [Select]

  7952:20220509:134647.068 Got signal [signal:15(SIGTERM),sender_pid:95441,sender_uid:0,reason:65537]. Exiting ...
 20809:20220509:134647.068 syncing history data in progress...
 22832:20220509:134647.070 syncing history data... 100.000000%
 22832:20220509:134647.070 syncing history data done
  7952:20220509:134647.439 Zabbix Proxy stopped. Zabbix 5.4.11 (revision 9aa30c495c).


Code: [Select]

zabbix_proxy [20947]: "StartIPMIPollers" configuration parameter cannot be used: Zabbix proxy was compiled without IPMI support
Also I see that IPMI support ist not enabled:

Code: [Select]

10702:20220509:140452.024 **** Enabled features ****
 10702:20220509:140452.024 SNMP monitoring:       YES
 10702:20220509:140452.024 IPMI monitoring:        NO
 10702:20220509:140452.024 Web monitoring:        YES
 10702:20220509:140452.024 VMware monitoring:     YES
 10702:20220509:140452.024 ODBC:                  YES
 10702:20220509:140452.024 SSH support:            NO
 10702:20220509:140452.024 IPv6 support:          YES
 10702:20220509:140452.024 TLS support:           YES
 10702:20220509:140452.024 **************************

I there any way to get IMPI suppot with the Zabbix Proxy plugin?

I am using:
zabbix54-proxy   5.4.11
OPNsense   22.1.5

thanks
zulasch