The command you are using just renews the certificate file on the machine, it doesn't restart Apache, so you won't see the new cert until you do. Certbot has an option for apache integration that takes care of that stuff, so use that.
I have not heard anything from you in the DM.
Nor has there been any activity in this thread.
Do you still have a problem?
Is it no longer urgent?
Hi Rudy,
Sorry for the late reply.
I believe there is still a problem. Sometimes it works and sometimes it doesn't.
I cam pay 200 to fix and have it so that it renews automatically.
Can you take this job?
Best,
I think I can ... I think I can ...
lol
Hi Rudy,
I believe we worked together previously on this server.
Are you available to assist in resolving this issue?
Best,
I think we keep different sleep schedules ...
But, yes.
Please keep in mind that this is a public forum. While it is possible to interact with it via email, your replies are still posted publicly, the same as they would be when replying via the web. You really do not want to publicly post credentials.
Rather than share an SSH secret key, which is an extremely risky activity, it is far safer to temporarily add an additional SSH public key to the appropriate account on your server. You can safely request that from the person assisting you as it is not secret by design.
Thank you. Sorry for the confusion, I deleted the relevant post.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.