That screenshot shows the CSR and key - neither of which demonstrate the existence of a certificate.
Anyway, there’s a couple of things that might be wrong:
You probably haven’t yet created a certificate.
For the certbot --apache certificate issuing process to succeed, port 80 needs to actually point at Apache. In your case, your port 80 is pointing directly at your application server, and only port 443 is pointing at Apache. This won’t work because Apache is “bypassed” when Let’s Encrypt performs domain validation.
If you want the certificate to be valid for isoko.ga and www.isoko.ga, you need to include those two domains on the certificate by including each domain with -d example.org -d www.example.org etc in your Certbot command.
The act of installing Certbot doesn’t give you an SSL certificate. You need to use it to issue a certificate in a way that makes sense for your hosting environment.
If you can elaborate on how you want your website to work (what kind of website it is, are you going to proxy it behind Apache or do you want to install the certificate directly to the application, etc), we can help you get a certificate.
Without knowing what your webapp runs on (JBoss? Tomcat?) it’s impossible to say whether it is possible to set it up with HTTPS without a proxy.
If you can’t set it up behind a proxy successfully, the most I can reccommend to you is to pay a sysadmin to help you or review online materials such as https://httpd.apache.org/docs/2.4/howto/reverse_proxy.html . If you manage to do that, then Certbot will work in a simple way.
my problem is to get https
here living, im one who can help myself, no one can touch what im doing, especially with java, everyone works with php
im the only one into this, remember