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.
My domain is: bioscope.club
I ran this command: Right-click Inspect and opened Console
It produced this output: ERR_CERT_COMMON_NAME_INVALID
My web server is (include version): AWS
The operating system my web server runs on is (include version):
My hosting provider, if applicable, is: AWS Lightsail
I can login to a root shell on my machine (yes or no, or I don't know): Yes
I'm using a control panel to manage my site (no, or provide the name and version of the control panel):
AWS Lightsail
The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot): N/A (sudo /opt/bitnami/bncert-tool)
There are 6 references to URIs starting with //13.43.73.48/ on that /videos/ page. That's not going to work, as the certificate isn't valid for IP addresses. You should change the CSS code to use URIs starting with //bioscope.club/ instead.
Hopefully that CSS code is dynamically added to the HTML page, otherwise you might have to search your entire code base for references to the IP address in URIs.. Not a bad idea to do anyway.
Good day
Will you please assist?
I'm getting the same error on About | The Rainbow Mafia
I've used the plugin; Better Search & Replace to sort out the IP / URL issue.
Yet, the icons are still not showing.
Those errors are not related to your Let's Encrypt cert. Something is wrong with your website configuration. You should consult a forum for website programming.
That said, it looks like you are trying to load items from font-awesome using a specific IP address (https://13.42.205.187). That isn't correct and you need to change that. There is a cross-origin request blocked message when I try to load your page in Firefox on Ubuntu. Your error message is different but I believe it is the same underlying reason.
