{"id":1527,"date":"2020-06-07T21:50:43","date_gmt":"2020-06-07T13:50:43","guid":{"rendered":"https:\/\/www.wesbytes.com\/guide\/?post_type=kb&p=1527"},"modified":"2026-01-12T14:42:16","modified_gmt":"2026-01-12T06:42:16","slug":"how-do-i-check-my-servers-response-directly-without-cloudflare","status":"publish","type":"kb","link":"https:\/\/www.servergigabit.com\/guide\/kb\/how-do-i-check-my-servers-response-directly-without-cloudflare","title":{"rendered":"How do I check my server\u2019s response directly without Cloudflare?"},"content":{"rendered":"

\"server\u2019s<\/h3>\n

How do I check my server\u2019s response directly without Cloudflare?<\/strong><\/h3>\n

When troubleshooting an issue with a HTTP response from Cloudflare<\/a>, often your origin server may be the cause of this. Therefore, it is useful to request the same URL directly from your server to compare with the response from Cloudflare. In these examples, the domain is\u00a0example.com<\/code>\u00a0and the IP address for the origin server is\u00a0123.123.123.123<\/code>First of all, to do this you\u2019ll need to identify the IP address of your origin server \u2013 if you don\u2019t know this already you can find this in your Cloudflare DNS settings by looking at the DNS records for your domain.We\u2019re going to use the command line tool cURL here to check your server\u2019s response. For full information on the options available, take a look at the cURL manual page.curl (versions 7.21.3 and newer)<\/strong><\/p>\n

curl --silent --verbose \/\/example.com\/example-url\/here --resolve example.com:443:123.123.123.123 --insecure<\/code><\/p>\n

If you wanted to use HTTP instead of HTTPS, you would change the URL to http:\/\/ and also the Port number in the\u00a0--resolve<\/code>\u00a0argument would change from\u00a0443<\/code>\u00a0to\u00a080<\/code><\/p>\n

Note<\/strong>\u00a0we have included the\u00a0--insecure<\/code>\u00a0flag in this command as it skip\u2019s cURL\u2019s default behaviour of validating the SSL certificate presented by your server. If you have a valid certificate installed, you can remove this flag.<\/p>\n

The\u00a0--resolve<\/code>\u00a0flag allows you to neatly force a request to a specific IP address, but some older versions of cURL don\u2019t support it. If absolutely necessary, you can use a different way of doing this.<\/p>\n

curl (versions 7.21.2 and older)<\/strong><\/p>\n

curl --silent --verbose \/\/123.123.123.123\/example-url\/here --header \"Host: example.com\"<\/code><\/p>\n

The resulting output from cURL will show you the full HTTP response including headers direct from your origin server\u2019s IP address \u2013 removing Cloudflare from the equation entirely. Therefore if you still see the issue you\u2019re experiencing with this output, you can be sure you\u2019ll need to investigate what is happening on your server as the issue is not caused by Cloudflare. If its not obvious what the next step is from here, contacting your hosting provider<\/a> for assistance is the best way forward.<\/p>\n","protected":false},"excerpt":{"rendered":"

How do I check my server\u2019s response directly without Cloudflare? When troubleshooting an issue with a HTTP response from Cloudflare, often your origin server may be the cause of this. Therefore, it is useful to request the same URL directly from your server to compare with the response from Cloudflare. In these examples, the domain is\u00a0example.com\u00a0and the IP address for…<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"kbtopic":[43],"kbtag":[1124,1442],"class_list":["post-1527","kb","type-kb","status-publish","hentry","kbtopic-cloudflare","kbtag-cloudflare","kbtag-server-response"],"_links":{"self":[{"href":"https:\/\/www.servergigabit.com\/guide\/wp-json\/wp\/v2\/kb\/1527","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.servergigabit.com\/guide\/wp-json\/wp\/v2\/kb"}],"about":[{"href":"https:\/\/www.servergigabit.com\/guide\/wp-json\/wp\/v2\/types\/kb"}],"author":[{"embeddable":true,"href":"https:\/\/www.servergigabit.com\/guide\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.servergigabit.com\/guide\/wp-json\/wp\/v2\/comments?post=1527"}],"version-history":[{"count":4,"href":"https:\/\/www.servergigabit.com\/guide\/wp-json\/wp\/v2\/kb\/1527\/revisions"}],"predecessor-version":[{"id":6078,"href":"https:\/\/www.servergigabit.com\/guide\/wp-json\/wp\/v2\/kb\/1527\/revisions\/6078"}],"wp:attachment":[{"href":"https:\/\/www.servergigabit.com\/guide\/wp-json\/wp\/v2\/media?parent=1527"}],"wp:term":[{"taxonomy":"kbtopic","embeddable":true,"href":"https:\/\/www.servergigabit.com\/guide\/wp-json\/wp\/v2\/kbtopic?post=1527"},{"taxonomy":"kbtag","embeddable":true,"href":"https:\/\/www.servergigabit.com\/guide\/wp-json\/wp\/v2\/kbtag?post=1527"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}