I've added all the required meta tags to my html head section but when I run my site through Twitter Card Validator or another site like opengraph.dev, my tags cannot be found.
The Twitter Card Validator log tells me, "ERROR: Fetching the page failed because other errors.".
I have no idea what I'm doing wrong, everything is as it supposed to be on my end. This is so frustrating!
Here's my head section:
<!-- Primary Meta Tags -->
<title>Web | DASA</title>
<meta charset="utf-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge" />
<meta name="author" content="DASA">
<meta name="viewport" content="width=device-width,initial-scale=1.0,maximum-scale=1" />
<meta name="description" content="Web | DASA is a a full-service web design and development company that specializes in creating custom websites that are tailored to the needs and goals of our clients.">
<!-- Open Graph / Facebook -->
<meta property="og:type" content="website">
<meta property="og:url" content="https://dasa.rf.gd/">
<meta property="og:title" content="Web | DASA">
<meta property="og:description" content="Web | DASA is a a full-service web design and development company that specializes in creating custom websites that are tailored to the needs and goals of our clients.">
<meta property="og:image" content="https://dasa.rf.gd/images/DASA_1000.png">
<!-- Google Verification -->
<meta name="google-site-verification" content="DT_07_6QW8E0XDtntVY_u5nDz8OFjlgGg9lKnd6uPiU" />
<!-- Twitter -->
<meta property="twitter:card" content="summary_large_image">
<meta property="twitter:url" content="https://dasa.rf.gd//">
<meta property="twitter:title" content="Web | DASA">
<meta property="twitter:description" content="Web | DASA is a a full-service web design and development company that specializes in creating custom websites that are tailored to the needs and goals of our clients.">
<meta property="twitter:image" content="https://dasa.rf.gd/images/DASA_1000.png">
Here's the url for my site: https://dasa.rf.gd
This issue can occur when your TLS certificate is signed by an untrusted authority. Specifically, the intermediate certificate in the certificate chain may be missing or invalid.
You can use a service like SSL Labs Server Test to identify issues with your certificates and follow their recommendations to resolve the problem. Additionally, you can look up your certificate provider's FAQ or documentation if the issues persists.
Since you are using ZeroSSL, a quick recommendation will be to switch to Let's Encrypt as their intermediate certificates are signed by the Internet Security Research Group