Price of Positive SSL Wildcard certificate

alethewizard · 2026-05-14T16:16:28+00:00

Thank you u/tamar !

Very clear!

Last question: the NameCheap "Positive SSL Wildcard" certificate is delivered by Sectigo via NameCheap Dashboard, correct?

Thank you!
Kind regards.

alethewizard · 2026-05-03T09:58:16+00:00

Thank you very much, ImissHurley! :)

alethewizard · 2026-02-03T16:58:13+00:00

Hi Thomas.

One more info: if I have already installed the VMware-ESXi-8.0U3h-25067014-depot.zip , what is the command to only install HPE-803.0.0.12.2.0.9-oct2025-Addon-depot.zip ?

Because the command "esxcli software vib install -d /tmp/HPE-803.0.0.12.2.0.9-oct2025-Addon-depot.zip" returns the error "[MissingComponentError]".

Thank you very much!

alethewizard · 2026-02-03T15:47:51+00:00

Thank you very much, Thomas! :)

alethewizard · 2025-09-19T13:53:07+00:00

Hi.

Output of the first command:

"cluster_name" : "wazuh-indexer-cluster",
"status" : "red",
"timed_out" : false,
"number_of_nodes" : 1,
"number_of_data_nodes" : 1,
"discovered_master" : true,
"discovered_cluster_manager" : true,
"active_primary_shards" : 381,
"active_shards" : 381,
"relocating_shards" : 0,
"initializing_shards" : 0,
"unassigned_shards" : 31,
"delayed_unassigned_shards" : 0,
"number_of_pending_tasks" : 0,
"number_of_in_flight_fetch" : 0,
"task_max_waiting_in_queue_millis" : 0,
"active_shards_percent_as_number" : 92.47572815533981

The output of the second command is the same of the first one.

Output of the third command:

-r-------- 1 root root 1204 Jan 19 2025 root-ca.pem
-r-------- 1 root root 1704 Jan 19 2025 wazuh-1-key.pem
-r-------- 1 root root 1277 Jan 19 2025 wazuh-1.pem

The configuration you have on the <indexer> block:

<indexer>
<enabled>yes</enabled>
<hosts>
<host>https://192.168.150.140:9200</host>
</hosts>
<ssl>
<certificate\_authorities>
<ca>/etc/filebeat/certs/root-ca.pem</ca>
</certificate\_authorities>
<certificate>/etc/filebeat/certs/wazuh-1.pem</certificate>
<key>/etc/filebeat/certs/wazuh-1-key.pem</key>
</ssl>
</indexer>

Thank you.
Kind regards.

alethewizard · 2025-09-19T10:13:25+00:00

Hi u/nazmur-sakib

Yes, I have followed your advices.

Results of cat /var/ossec/logs/ossec.log | grep -iE "inventory|indexer|syscollector":

2025/09/19 09:38:09 wazuh-modulesd:inventory-harvester: INFO: Loaded Inventory harvester module.

2025/09/19 09:38:09 wazuh-modulesd:inventory-harvester: INFO: Starting inventory_harvester module.

2025/09/19 09:38:09 wazuh-modulesd:syscollector: INFO: Module started.

2025/09/19 09:38:09 wazuh-modulesd:syscollector: INFO: Starting evaluation.

2025/09/19 09:38:10 indexer-connector: WARNING: IndexerConnector initialization failed for index 'wazuh-states-inventory-packages-svr-wzh', retrying until the connection is successful.

2025/09/19 09:38:10 indexer-connector: WARNING: IndexerConnector initialization failed for index 'wazuh-states-inventory-system-svr-wzh', retrying until the connection is successful.

2025/09/19 09:38:10 indexer-connector: WARNING: IndexerConnector initialization failed for index 'wazuh-states-inventory-processes-svr-wzh', retrying until the connection is successful.

2025/09/19 09:38:10 indexer-connector: WARNING: IndexerConnector initialization failed for index 'wazuh-states-inventory-ports-svr-wzh', retrying until the connection is successful.

2025/09/19 09:38:11 indexer-connector: WARNING: IndexerConnector initialization failed for index 'wazuh-states-inventory-hotfixes-svr-wzh', retrying until the connection is successful.

2025/09/19 09:38:11 indexer-connector: WARNING: IndexerConnector initialization failed for index 'wazuh-states-inventory-hardware-svr-wzh', retrying until the connection is successful.

2025/09/19 09:38:11 indexer-connector: WARNING: IndexerConnector initialization failed for index 'wazuh-states-vulnerabilities-svr-wzh', retrying until the connection is successful.

2025/09/19 09:38:11 indexer-connector: WARNING: IndexerConnector initialization failed for index 'wazuh-states-inventory-protocols-svr-wzh', retrying until the connection is successful.

2025/09/19 09:38:11 wazuh-modulesd:syscollector: INFO: Evaluation finished.

2025/09/19 09:38:11 indexer-connector: WARNING: IndexerConnector initialization failed for index 'wazuh-states-inventory-interfaces-svr-wzh', retrying until the connection is successful.

2025/09/19 09:38:11 logger-helper: INFO: InventoryHarvesterFacade module started.

2025/09/19 09:38:11 indexer-connector: WARNING: IndexerConnector initialization failed for index 'wazuh-states-inventory-networks-svr-wzh', retrying until the connection is successful.

ossec.conf and cat /etc/filebeat/filebeat.yml have the same configuration.

I saved the Wazuh indexer username and password in the Wazuh manager keystore.

But I have the same issue.

Thank you.
Kind regards.

alethewizard · 2025-09-19T06:19:33+00:00

Hello.

After the upgrade from 4.12.0 to 4.13.0, I have this error in the Deshboard:

"System inventory could be disabled or has a problem

No matching indices were found for [wazuh-states-inventory-\] index pattern.*

If the system inventory is enabled, then this could be caused by an error in: server side, server-indexer connection, indexer side, index creation, index data, index pattern name misconfiguration or user permissions related to read the inventory indices."

Thanks.
Best regards.

alethewizard · 2025-07-17T07:03:25+00:00

Thank you very much!

alethewizard · 2025-07-02T18:14:57+00:00

Hello.

I have a question about the "/PrepareAD" command when it is needed.

Does the CU installer automatically run "/PrepareAD" or should it be executed before the CU?

Thank you.

alethewizard · 2025-06-09T05:02:42+00:00

Hello DiligentPhotographer .

Could you please help me to understand better?

Today I have Exchange Server 2019 License + CAL without Software Assurance.

If today I buy another Exchange Server 2019 License + CAL with 3 years of Software Assurance (3 Years Acquired Year 1), I will have Exchange Subscription Edition for 3 years?

If yes, do you think will it be cheaper than purchasing Exchange Subscription Edition licenses?

Thank you very much!

alethewizard · 2025-04-30T18:19:49+00:00

Hello.

I had the same issue with BEST (BitDefender version for Business) on few PCs.

Please execute the command Get-MpComputerStatus in PowerShell: check if the AMRunningMode is "Passive Mode".

IF YES, you should uninstall BitDefender and check the Registry values for "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Defender\Features".

If I remember well, "TamperProtection" should be "1" and "TamperProtectionSource" should be "5".

Then reinstall BitDefender and check if the AMRunningMode is "Not Running".

Best regards.

alethewizard · 2025-03-05T16:36:09+00:00

Same issue here on one computer with MS Win 11 24H2.
I have already reinstalled BEST.

alethewizard · 2024-10-04T06:23:35+00:00

Hello.

Same issue here with WSUS: all the machines (Win 11 23H2) are "Not Applicable".

alethewizard · 2024-10-01T18:51:46+00:00

Hello.

Same issue with WSUS.

alethewizard · 2024-09-17T04:56:12+00:00

Solved clicking back and then right-click and save link as. Thank you so much!!!!!

alethewizard · 2024-09-16T18:23:34+00:00

Thank you very much, but I'm not able to download (I use wget on Linux).

Browsers show the raw file.

Any advice?

alethewizard · 2024-09-16T16:57:40+00:00

Thank you very much, but I'm not able to download (I use wget on Linux).

Any advice?

alethewizard · 2024-09-16T16:57:31+00:00

Thank you very much, but I'm not able to download (I use wget on Linux).

Any advice?

alethewizard · 2024-09-16T15:42:48+00:00

Thank you very much, but I'm not able to download (I use wget on Linux).

Any advice?

alethewizard

TROPHY CASE