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. crt.sh | example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.
You will also need to update your Apache configuration (e.g. /etc/apache2).
If your tar method preserved symbolic links, then Certbot on the new machine should be able to use the copy of /etc/letsencrypt to renew your certificates in the future.
tar zpcvf backup_etc-{date}.tar.gz /etc/letsencrypt/
I also copied a www.bayambangsystems.com-le-ssl.conf file from old server's /etc/apache2/sites-available manually. meaning I copied the text within it and copied it to same file name in new server.
What other files do I need to fix?
My website has some components that require https to run.
I changed the base url just to try if the application routing and database connection work. But everything should be working through https, which was my previous setup.
I also copied a www.bayambangsystems.com-le-ssl.conf file from old server's /etc/apache2/sites-available manually. meaning I copied the text within it and copied it to same file name in new server.
What other files do I need to fix?
Use a2ensite to enable that site (creating a symlink in sites-enabled).
If you used a different arrangement of names and certificates, you will eventually get expiry notices by e-mail when you don't replace a past certificate with an exactly equivalent one. If your new server is working properly the way you expect, including renewing your certificates, you can ignore these.