I sincerely apologize if this has been discussed however when trying to search for exactly what I am looking for and even reading several posts about this, I am unable to find the answer still. Further Documentation is not clear at all after you have setup Load Balancer and what is to be expected.
Ok so we setup the Load Balancer and enabled it.
As I have come to understand this A Record we are LB is sent though the CloudFlare, naturally when pinging the A Record we are seeing a new IP (that is foreign to our actual IP’s).
Here is the problem. We cannot reach the intended site. The site appears dead.
What am I missing?
When We test the actual IP’s (without DNS) site is working on both IP’s
CloudFlare shows the sites as up (Health Check - which seems puzzling to me that CloudFlare sees the site up).
While I appreciate going back to the basics, it is seeming like nobody really knows how to answer the question. If I cannot reach the intended site on the LoadBalancer IP this would suggest that something is blocking the server before it hits our firewall.
I will repeat again, that the site can be reached without DNS on both IP’s
Did you receive a ticket number? Did you actually receive a response apart from an auto response? Sometimes the ticket gets automatically closed, in which case you just need to reply.
I see the ticket and see it’s assigned to an engineer asking about a HAR file. I suspect once they circle back to the ticket, they’ll still need more detail than in this thread as the HAR shows requests & responses your browser makes with Cloudflare.
The problem here is that an HAR file will not show anything. If I cannot get to the webpage in question, how will you determine what is wrong??
When trying to go to the page its not opening… it just sits as if to suggest there is no DNS, however when I ping the address in question using the a-record it pings to the foreign IP that cloudflare assigns as the LoadBalancer.
Finally got my answer. It appears that the Load Balancer will not support traffic on port 5001.
This is due to the Load Balancer requiring the Cloudflare proxy.
By default, Cloudflare proxies traffic destined for the HTTP/HTTPS ports listed below.
Sandro, How would I have known that proxy has limitations? It does not say this anywhere on the load balancer help pages. Further I did post my screenshots which shows the rule of testing port 5001
Also when I mentioned that trying to do an HAR would be impossible as the page failed to load. Perhaps better asking of questions would have been best here in this case.
Your assuming too much here, and perhaps because your super familiar to this function your overlooking people who have never used this on CloudFlare… Further why in the world are there limitations? Seems crazy to me that the Name Load balancing used by CloudFlare should be called Limited Load Balancing. All I wanted to do was have CloudFlare change destination IP’s when one is detected as down, not have an application/restricted network layer LB.
That of course not. But if you had posted the URL, as I asked, it would have been obvious which port you are trying to proxy.
Thats not load balancing related. Cloudflare only supports a certain set of ports in general. Unless you are using Spectrum, but thats a different story.
