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.
Having read your initial post, I don’t know the issue you’re facing. I visited app5.juvlon.com and was redirected to app6.juvlon.com. It looks like you have a valid Let’s Encrypt certificate that was issued on August 12 for app6.juvlon.com that is not yet ready for renewal. You could force a renewal, but you normally don’t want to do that unless you’re changing something (e.g. adding/removing a domain/subdomain, wanting a new private key). Since you’re redirecting app5.juvlon.com to app6.juvlon.com, the Let’s Encrypt certificates you generated on August 29 and August 30 for app5.juvlon.com obviously aren’t going to do anything.
At https://crt.sh/?q=app5.juvlon.com I can clearly see two new certificates issued on August 29 and August 30 for app5.juvlon.com. From the link you posted, I think the following may be misleading you:
These results were cached from August 2, 2020, 10:26 pm PST to conserve server resources.