ssl-check | HTTPS certificates , in a programmatic way | TLS library

Do you known how properly work a fetch call with a self-signed certification in react-native app ?

I have a valid Let's Encrypt SSL certificate which works as expected when setup on windows IIS:

https://www.sslshopper.com/ssl-checker.html#hostname=https://paperlesssolutionsltd.com.ng

When I apply same certificate to an Elixir ACE server like so:

I am working on a proof of concept for deploying a conformance pack via AWS cloudformation and I am stumped by the error "Parameter values specified for a template which does not require them." The config rule I am using does require a parameter. Code is attached. I have also tested the template with cfn-lint and do not receive any feedback/errors.

My template is "simple" and below:

conftest.py:

I have the following parametrized test:

Bad(?) news "SSL For Free is joining ZeroSSL". Since their news I renewed my certificates and TLS stopped working. Used to work fine.

With new certificates I get error "You may need to install an Intermediate/chain certificate to link it to a trusted root certificate" from https://www.sslshopper.com/ssl-checker.html and this error "TLS Certificate is not trusted" from https://www.digicert.com/help.

Browsers are smart enough to mask the problem but my Android app uses an API and it stopped working.

Anyone else getting TLS problems since ZeroSSL got involved?

I'm using redbirdjs on nodejs which is awesome since its so simple (two domains, same server), but Zero provides no installation instructions for my setup. (My domains are small in traffic so using the fastest webservers etc. isn't an issue).

Zero took away the 2 domains in one cert option (gee thanks) so my updated script looks like:

I've made an app that calls a website to populate its content... it worked without problems, but suddenly today I noticed that the app is not getting data from the site anymore. On all installations of the app. How is this possible? Has my site been added to some sort of blacklist for whatever reason by google?

EDIT:

if I open Url in the browser i see "1".. but this returns "":

My website works well. I can see it properly in the browser, but then I get this error message if I want to run the W3C validator on it.

Before asking here I searched the high and lows of stackoverflow, and tried the solution of adding the header to my express server res.set('Accept', 'text/plain'); or router.use((req, res, next) => { res.append('Accept', "application/soap+xml"); next(); }); but still cannot be validated

Seems to be related to the SSL certificate but I have tested the certificate using several websites like https://www.sslshopper.com/ssl-checker.html but it seems that the certificate is correct.

Any ideas? Many thanks

When I try to validate social sharing tags using Linked in Post Inspector I get the following error for any page I submit, but no other information, it gives no clue as to what is wrong:

I found this post: LinkedIn post inspector encountering server error on https URL

which says there are known issues with the Post Inspector, that post is over a year old is there really no update from Linked In on this?

I also found this: Validating link in post-inspector linkedin in gives server error

I checked the certificate here: https://www.sslshopper.com/ssl-checker.html

which reported that the hostname is correctly listed in the certificate.

Any advice on debugging this would be very welcome.

The 520 error seems to be related to Cloudflare, so this is possibly an issue with headers related to SSL - Cloudflare, certificate origin maybe?