I proxied the domain.
In https://hostingchecker.com/ cloudflare hide my site(blog.webjeda.com) host.
But here It is not hiding.
This was likely a TTL / delay when you updated your DNS records to Cloudflare. Both tools now show Cloudflare as your host.
Related
I have purchased ngrok pro plan to use whitelabeled domains through cloudflare. But having trouble configuring end to end SSL encryption.
React app is running on localhost (http://localhost:3000).
created a domain (app.example.com) in ngrok.
added CNAME record for xxx.ngrok.io url in cloudflare for app.example.com.
SSL is enabled in cloudflare
https://app.example.com gives HTTP 520 error on cloudflare
cloudflare has universal certificate on *.example.com domain.
Is there anyway i can have https://app.example.com resolves to https://localhost:3000 through ngrok?
Here is one way, assuming you are fine with having Cloudflare only act as DNS:
Configure ngrok to serve the correct TLS certificate. In ngrok for your domain app.example.com, select the "Automated TLS certificates" option, which means ngrok will provision one for you.
In Cloudflare, "grey cloud the DNS record" so that traffic is no longer proxied through Cloudflare before it is proxied through ngrok. Now it will only be proxied through ngrok before being forwarded to your local server.
Start your ngrok tunnel. Assuming your local server is not configured to terminate TLS, you can run something like ngrok http --bind-tls=true --hostname=app.example.com 3000 to start a HTTPS only tunnel endpoint.
I was looking ngrok tunnel solution proposed and I also found a way you can do an Argo Tunnel through cloudflare directly. This can be another approach to the problem. https://developers.cloudflare.com/cloudflare-one/tutorials/share-new-site
I didn't answer your question. I just want to share, that we can make localhost on our computer accessible through our own domain using cloudflare tunneling.
https://developers.cloudflare.com/cloudflare-one/connections/connect-apps/install-and-setup/tunnel-guide/
Stack:
Cloudflare
SSL in Full(Strict) mode
Always Use SSL is ON
Heroku
Automatic Certificate Management (ACM)
All this seems to work well, except that on the Cloudflare SSL Overview tab, under Traffic Served Over TLS 30% is labeled None (not secure) I would expect this section to have started to approach zero.
The settings above have been in effect for well over 24 hours.
So, where's all this non-ssl traffic coming from? Is that just traffic coming in over HTTP that Cloudflare is redirecting to SSL before it gets anywhere else? Or is it something else?
Yes, it's very likely that traffic is coming in over HTTP that Cloudflare is redirecting to SSL. When someone first requests the HTTP version of the site that will be handled over HTTP (not HTTPS), which will then redirect to the HTTPS version.
Currently I am using No-Ip for my website and I wanted to use cloudflare for protection against ddos and bots. I noticed that you need a domain for cloudflare. Also I searched the web and found something called cloudflare ddns. I don't own a domain only the dynamic public ip of my home route. So how do I set up cloudflare without a domain?
Maybe you will be interested in Cloudflare Argo Tunnel.
A single command cloudflared tunnel --url localhost:80 will expose your webserver running on port 80 on your home server/PC to the internet. Cloudflare will generate a free subdomain under trycloudflare.com domain that your visitors can reach.
I am using Cloudflare, and my domain is using their nameservers olga and duke.
I have A records for ns1.mydomain.com and ns2.mydomain.com and that is only thing which is revealing my real IP address, because i can not force clients to use CloudFlare. So I host their DNS.
If I enable CloudFlare for my NS1 & NS2 A records, will everything continue to work well?
Notice: NS1 and NS2 at registrar are will still be pointing to real IP address.
If you want to use Cloudflare you need to choose one of the following configurations:
Change your name servers at the registrar and use in Full mode,
Use via a hosting partner, or
Upgrade to BIZ and use a CNAME setup
Cloudflare Knowledge Base Article
Whilst Cloudflare can host the DNS records for your host - it will not proxy DNS records; Cloudflare will only proxy HTTP and HTTPS traffic.
If you wish to proxy DNS traffic you can use Cloudflare's Virtual DNS product. This acts as a firewall for your existing DNS infrastructure.
i got a problem with my hosting provider (Mittwald) and Cloudflare.
Over Cloudflare i wanna use the flexible SSL
Cloudflare says:
Flexible SSL: There is an encrypted connection between your website visitors and CloudFlare, but not from CloudFlare to your server.
So if i understand it right, thats exactly what i want!
The User accesses the website over https://example.com but cloudflare is communication with my site over http://example.com so that the not opened port (443) from my provider is not needed?
unfortunately that doesn't work till now... i allways get an error like
err_connection_refused
Any help or hint would be great!
thanks in advance!
That would indicate your site hasn't yet propagated to go through CloudFlare's DNS and is pointing to your local site (where the port is closed and the connection is refused). If SSL is disabled on CloudFlare you would get a protocol error instead.
Therefore the best option would be, if you've waited for the DNS to propagate, to contact CloudFlare support.