Browser not trusting cloudflare origin certificate

[jadeyv]

Hello,

I’m trying to understand how cloudflare and their certificates work so I have a test dns that’s being handled by cloudflare as well as a test server. My A record for my dns points to my server and I made sure it’s being proxied through CF (orange cloud).
Then set my SSL/TLS settings to full(strict).
Lastly I generated origin certificates and downloaded them.

Then I ran my server using those certificates but when I try to connect to the server in my browser I receive an untrusted certificate error

Am I doing this correctly? Do the DNS settings need time to update?
I’d like to use cloudflare’s origin certificates as well as route through cloudflare but I’m not sure what I’m doing wrong.

[sdayman]

As the Origin Certificate page says:

Origin Certificates are only valid for encryption between Cloudflare and your origin server.

It’s only for Proxied hostnames.

[jadeyv]

@sdayman It is proxied though. As I mentioned in my posted, "I made sure it’s being proxied through CF (orange cloud)

Unless I am misunderstanding. Does it not work for proxied A record to IP addresses?

[sdayman]

It does not appear to be proxied for you. What’s the actual hostname?

[jadeyv]

The host name is jdragon.digital and the server is running on port 8080. I posted an image showing the name, ip and proxied status.

[sdayman]

8080 is not an HTTPS port.

I’m not even able to get a response from that server with https, http, or http on 8080.

[jadeyv]

So does it have to be 443? I’ll try running it on 443. But it’s a simple node js web server I’m testing for ssl.

const https = require(‘https’);
const fs = require(‘fs’);

const options = {
key: fs.readFileSync(‘key.pem’),
cert: fs.readFileSync(‘cert.pem’)
};

https.createServer(options, function (req, res) {
res.writeHead(200);
res.end(“hello world\n”);
}).listen(8000);

[sdayman]

443 would certainly be nice if you want HTTPS.

[jadeyv]

Oh nevermind! Now it’s working! Thank you so much @sdayman !

[sandro]

@sdayman

8080 is not an HTTPS port.

Just for the sake of good order - because I am sure in two years there’ll be someone referring to this thread saying ports are protocol specific - generally 8080 is just yet another port and of course you can run HTTPS on it, in this particular case (and what @sdayman meant) it won’t work because Cloudflare only proxies HTTP over that port.

Apologies for the nitpicking, just tired of all the bandwidth and sub-domains and secure sites on HTTP

[jadeyv]

Thank you for both! I should have just used 443, it works on 443 .

[sandro]

Thanks only go to @sdayman please. I was just nitpicking