Question

403 forbidden in server header error and 503 https status code error

Posted December 14, 2021 150 views
CachingCDN

I am having a very hard time in maintaining the server as I have appointed many cloud developers but nobody is able to solve the problem or find the exact error.when I check the server header checker it # shows 403 Forbidden in server Header
and 503 Https header Response when I check https status code it should be 301 and 200 instead.I know that’s not your part of job.But I have no options left than to contact you also my website all pages are working fine but the updated pages are not ranking/or showing Cached version of it.I want answer to 2 questions.website working fine only problem in post updation and ranking I only see post updated 3 -5 days ago not showing that it was updated today’s
Q-1 can you provide with the code to solve the issue or provide a developer to solve the issue?
Q-2 Will creating another droplet and migrating my website to new droplet will solve the issue?
I am using CloudFlare free version and Nginx server.
one can check error on the below Website:: by entering my domain url ********************* https://npsc.co.in ****on the below websites.

[https://httpstatus.io]
one can also check the server response code BELOW:


Request

GET npsc.co.in HTTP/1.1
Host:
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/42.0.2311.135 Safari/537.36 Edge/12.246
Response
< HTTP/1.1 301 Moved Permanently
< Date: Tue, 14 Dec 2021 17:22:07 GMT
< Transfer-Encoding: chunked
< Connection: keep-alive
< Cache-Control: max-age=3600
< Expires: Tue, 14 Dec 2021 18:22:07 GMT
< Location: https://npsc.co.in/
< Report-To: {“endpoints”:[{“url”:“https:\/\/a.nel.cloudflare.com\/report\/v3?s=nzvHKf3b%2FQ8SiGQH3QF%2BA%2Bh1zspAtBNM7XDY3NUh%2F2Tuo6K0vEByBpZ1QHztTMs7orODzCGyWMDp0MR7gRWZuwIvDxzGGaR%2FekKUlRarjV4RXq7UZEsH3bs%2FVfTjigKtG1n6It3XY%2B6V”}],“group”:“cf-nel”,“maxage”:604800}
< NEL: {“success
fraction”:0,“reportto”:“cf-nel”,“maxage”:604800}
< Server: cloudflare
< CF-RAY: 6bd91ccb5e8224d6-SJC
< alt-svc: h3=“:443”; ma=86400, h3-29=“:443”; ma=86400, h3-28=“:443”; ma=86400, h3-27=“:443”; ma=86400
Request
GET npsc.co.in HTTP/1.1
Host:
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/42.0.2311.135 Safari/537.36 Edge/12.246
Response
< HTTP/1.1 403 Forbidden
< Date: Tue, 14 Dec 2021 17:22:07 GMT
< Content-Type: text/html; charset=UTF-8
< Transfer-Encoding: chunked
< Connection: close
< CF-Chl-Bypass: 1
< Permissions-Policy: accelerometer=(),autoplay=(),camera=(),clipboard-read=(),clipboard-write=(),fullscreen=(),geolocation=(),gyroscope=(),hid=(),interest-cohort=(),magnetometer=(),microphone=(),payment=(),publickey-credentials-get=(),screen-wake-lock=(),serial=(),sync-xhr=(),usb=()
< Cache-Control: private, max-age=0, no-store, no-cache, must-revalidate, post-check=0, pre-check=0
< Expires: Thu, 01 Jan 1970 00:00:01 GMT
< X-Frame-Options: SAMEORIGIN
< Expect-CT: max-age=604800, report-uri=“https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct
< Report-To: {“endpoints”:[{“url”:“https:\/\/a.nel.cloudflare.com\/report\/v3?s=G4fAas7a2xsPBYOh7D6%2BmdYZ8NAoHPXvlmAPKstTRJ90ncnLthuij12LXXe6Amc5TsWyzj%2B6M1%2Fgx4wXfFBpBfIRtS6cilExzoZpE3AZxerMMtbnwjc0QRIqLAvXVfxFBpCNAKDXBynP”}],“group”:“cf-nel”,“maxage”:604800}
< NEL: {“success
fraction”:0,“reportto”:“cf-nel”,“maxage”:604800}
< Server: cloudflare
< CF-RAY: 6bd91ccbbe0f252c-SJC
< alt-svc: h3=“:443”; ma=86400, h3-29=“:443”; ma=86400, h3-28=“:443”; ma=86400, h3-27=“:443”; ma=86400

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

×
Submit an Answer
1 answer

Hi there,

In case that you are using Cloudflare’s browser check/protection, this could explain the 403 error.

What Cloudflare does is to check the visitor’s browser and if the check fails then the visitor is not allowed to access the site.

In case that you do not need this behavior, you could try disabling the browser Integrity Check via your Cloudflare account.

Best,
Bobby