We have a strange problem when enabling Cloudflare proxy to one of our Linode servers, We added a DNS record for a server proxied by Cloudflare.. When we access the server by the dns name we are being proxied as expected by Cloudflare. However, if i want to access the page directly via the real IP even by SSH and other ports, iam still also being proxied by Cloudflare and thus don’t reach the server at all. If i disable the proxy and make it a regular DNS record, everything works back again. Cloudflare only proxy WEB Traffic (http, https). we don’t have zero trust service by Cloudflare. Accessing the server via real IP should solely be based on communication between the client (our IP) and Linode. What could the issue be?
What steps have you taken to resolve the issue?
i disable the proxy and make it a regular DNS record, everything works back again but we become exposed on the web traffic
What feature, service or problem is this related to?
Yes, the real IP of the server! on tshark via cli i see no traffic at all reaching the server say by SSH, the moment i disable the proxy, everything works fine back.
I have worked before with cloudflare on other sites, never faced this problem.
If using the IP address of the server, the traffic will not pass through Cloudflare (unless the host is using Cloudflare Magic Transit - but you will still be able to reach the server by its IP address).
That’s a Linode IP address and doesn’t route over Cloudflare. If accessing a service directly by that IP mysteriously stops working when energy.tikal.ai is proxied, then the service you are connecting to is using energy.tikal.ai somewhere in its configuration.
I have many services running on this server each with its own port, besides SSH, all of them work freely whether by IP or by DNS, this happened only when i moved the dns from godaddy to Cloudflare and enabled the proxy (orange cloud).the dns name is not specifically configured anywhere apart from the web server.
Non-HTTP/S services won’t work if you use the hostname while it is proxied.
Using the IP address of the server will route direct to it, not via Cloudflare.
There will be a reason, it’s not possible for the proxying or not of energy.tikal.ai to affect your ability to connect directly to 172.238.119.211 unless that services refers back to energy.tikal.ai.