Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. https://crt.sh/?q=example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.
This is totally frustrating. No harm meant. Just saying. The original files have been put back in place… and yet getting errors when trying to launch the url.
As we said, it’s a bitnami issue. The platform and cert tool are their own. We can assist how we can, but Let’s Encrypt focuses on certificates. Wish we had a local bitnami person who could bridge the gap. From what I’ve seen on Bitnami’s community forums though, they have the resources and experience to give you direct specifics.
You can identify who is using port 80 or 443 with:
ss -tlnp | grep -E ":(80|443)"
@Jubilee2020 would you be interested in a short paid arrangement for somebody from the community to login to your server and help sort this out for you (from @schoen or someone else)? No pressure to, just if you feel like you could be spared trying to fix this yourself.
Yes, that is a better command than doing a kill -9. My motivation to use it (as a last resort) was that your control scripts were failing to stop Apache on their own.
