Certificate is not loaded after config reload

Before creating a ticket, please consider if this should fit the discussion forum better.

Environment

• ejabberd version: 23.01
• Erlang version: Erlang (SMP,ASYNC_THREADS) (BEAM) emulator version 12.3.1
• OS: Red Hat Enterprise Linux 8.5
• Installed from: official rpm

Bug description

Reload of certificate from valid to invalid seems not working.

1. I have configured certfile: "/opt/ejabberd/conf/lx-rec-fss-01-ejabberd.pem" where pem file was issued for different host
   -> Ejabberd was started with this config and behavior is OK. Service is running and when reaching Admin UI then secure connection is not established "NET::ERR_CERT_COMMON_NAME_INVALID"
2. Changed certificate "/opt/ejabberd/conf/lx-rec-fss-01-ejabberd.pem" to the correct one (rename invalid cert to different name and rename proper cert tolx-rec-fss-01-ejabberd.pem )
   ->Config was reloaded and new valid cert is accepted. When reaching Admin UI then secure connection is established.
3. Changed certificate again to invalid one and reload config.
   -> No impact, ejabberd is still using cert from step 2
   ejabberd.zip

I expect that once cert is updated although to wrong one, this one is used and not previous cached one.

Thank you.
BR,
Marek

No source file, test, or entry point is named. Reproduce the three-step certificate replacement and configuration reload using the attached ejabberd.zip and the stated ejabberd 23.01 environment, then trace certificate loading during reload. Done means the newly replaced certificate, including an invalid one, is used after reload rather than the previously cached certificate.