Issues with Renewed/ Self Signed Certs

[seanvandermolen]

Not sure if this is the right place for this, but I do believe this issue belongs to hitch.
I'm using Xvarnish/Cachewall and I've run into some issues with hitch not using the correct certificates.

The latest issue was a letsencrypt certificate that renewed and was not updated in hitch. It continuously loaded the expired certificate until I disabled and re-enabled cachewall. Then things worked correctly.

The other issues happened a while ago on another server and I've been unable to use Cachewall since. There was a bug in CPanels autoSSL that was generating self-signed certs. A new domain was made and during this time hitch used another domains certificate instead of the correct certificate. Even after the bug was fixed and new certificates were created on the account. And after reloading cachewall on several occasions, hitch still loads the incorrect certificate for that domain.

There are no instructions on how to troubleshoot this or if there is a way to clear hitch so it looks for new information?

I believe Cachewall was abandoned as a project, but I'm not sure. I also think the developer worked on hitch, wondering if anyone here knows anything about the status of that project.

[Kailashaghera]

I am having same problem. I am facing this problem in Xvarnish/Cachewall. So far I am unable to find any solution for this problem.

[SupraMario]

Can confirm this problem still exists as I'm experiencing it currently now, after implementing cachewall for a client per their request, addon domains with comodo certificates generated via AutoSSL are now failing.

xvctl disable cachewall

and all sites start working correctly with correct certificates. Unfortunately if we re-enable cachewall the sites go back to using an expired certificate and displaying errors.