http event errors filling up eventlog

[FrancWest]

Hi,

case #04981311. Our eventlog was filling up with 'An error occurred while using SSL configuration for endpoint 0.0.0.0:6172' http event errors. This event occurs several times every second.

It seems to be caused by the AHV Platform Service. Since we aren't using Nutanix it's safe to disable this according to support and thus we were advised to create the following registry key:

Path: HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Backup and Replication
Name: Disabled
Type: DWORD
Value: 1

This indeed worked, the errors are gone. However, I find the key-name rather strange. The key is named 'disabled'. I double checked with the engineer if this was a typo, but it was the correct key name.

Why was this key-name chosen? I would strongly recommend to rename it to a more meaningful key-name.

[foggy]

Hi Franc, the key name does indeed look strange, I will check. Thanks.

[FrancWest]

Hi foggy,

Any update?

[FrancWest]

Hi Foggy,

Any update on this?

Hi Franc, the key name does indeed look strange, I will check. Thanks.

[MILJW002]

Funny thing, I started to get the same error about a week ago. After googling a bit it looked like the root cause was the config was pointing to an old cert.

I’m also not using AHV, but just deleted the following key:

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HTTP\Parameters\SslBindingInfo\0.0.0.0:6172]

This made the errors go away for me.

J

[FrancWest]

We and Veeam Support checked the certificates and they were all fine in our case. Even regenerating the Veeam Self Signed Certificate didn't solve the issue.

[foggy]

Sorry, @FrancWest missed this thread. We were able to confirm that the key is correct and even though the name is indeed awkward (somehow it was historically given this name many years ago) it was decided not to touch it to avoid possible broken dependencies. Of course, we try to name the registry values descriptively and even have a naming policy in place for it, so this will not repeat in the future.

[FrancWest]

@foggy, can happen. Thanks for the update.