Website URL
(please specify the URL of the site on which you are experiencing the problem)
Error Message
403 FORBIDDEN NGINX
(please share the FULL error message you see, if applicable)
https://haytell.ru/ Website URL
(please specify the URL of the site on which you are experiencing the problem)
403 forbidden Error Message
403 forbidden nginx
please help me, my site gives out a 403 nginx error in the main yandex bot how to fix it.
Don’t create multiple topics on the same issue. I merged them for you
6 Likes
thank you and forgive me for this
Same problem. How to solve it? What is the point of this hosting if search robots cannot access it?
Based on the page content, the error is not caused by InfinityFree’s filter.
Instead, it look slike your custom code is returning a 403, usually this is configured via .htaccess, maybe you can check that?
Search Robots are allowed and not blocked, what error are you facing?
3 Likes
403 FORBIDDEN
USER-AGENT: Mozilla/5.0 (compatible; YandexBot/3.0; +http://yandex.com/bots)
YandexBot is blocked by your hosting and is given error code 403. Google is given code 200.
Admin, answer whether Yandexbot will have access to your hosting or not. My site is losing ground, this is an urgent critical issue. I spent the whole day migrating and setting up the site here, and now I find out such unpleasant things. If this is a political decision, it should be written about before user registration and in promotional materials.
What is your website’s URL? Are you also using Cloudflare like the original poster is?
If so, have you checked Cloudflare’s Firewall to ensure it isn’t being blocked there?
5 Likes
I don’t use Cloudflare. The URL doesn’t matter, the site is fine. The problem is described above, you can paste the URL from the top post into the verification service, the result will be similar - 403.
No url = no help, we need to know what is your site using.
HTML Verification methods are known to be not working, and dns verification is always suggested.
5 Likes
It doesn’t matter to me anymore, I changed the hosting. There was no point in waiting for help here, apparently this nonsense is in the admins’ heads - to block the Yandex bot.
The main thing is that the Yandex verification service produces the same code as others, so there is no need to instill nonsense in me here, I’m not an idiot. My site has nothing to do with this, the default domain of this hosting, with one index page has 403, what can I say, and if you like it, continue to endure the restrictions)
MY htacces
RewriteEngine on
Options All -Indexes
# Security flags for HTML headers
<IfModule mod_headers.c>
# Protect against XSS attacks
Header set X-XSS-Protection "1; mode=block"
# Protect against page-framing and click-jacking
Header always append X-Frame-Options SAMEORIGIN
# Protect against content-sniffing (MIME)
Header set X-Content-Type-Options nosniff
</IfModule>
# Unless directory, remove trailing slash
RewriteCond %{HTTP_HOST} !^wiki\.rpcs3\.net$ [NC]
RewriteCond %{REQUEST_FILENAME} !-d
RewriteCond %{REQUEST_URI} !^/[0-9]+\..+\.cpaneldcv$
RewriteCond %{REQUEST_URI} !^/[A-F0-9]{32}\.txt(?:\ Comodo\ DCV)?$
RewriteCond %{REQUEST_URI} !^/\.well-known/acme-challenge/[0-9a-zA-Z_-]+$
RewriteCond %{REQUEST_URI} !^/\.well-known/pki-validation/[A-F0-9]{32}\.txt(?:\ Comodo\ DCV)?$
RewriteCond %{REQUEST_URI} !^/\.well-known/cpanel-dcv/[0-9a-zA-Z_-]+$
RewriteCond %{REQUEST_URI} !^/\.well-known/pki-validation/(?:\ Ballot169)?
RewriteRule ^([^/]+)/$ http://%{HTTP_HOST}/$1 [R=301,L]
# Resolve .php file for extension-less php urls
RewriteCond %{REQUEST_URI} !^/[0-9]+\..+\.cpaneldcv$
RewriteCond %{REQUEST_URI} !^/[A-F0-9]{32}\.txt(?:\ Comodo\ DCV)?$
RewriteCond %{REQUEST_URI} !^/\.well-known/acme-challenge/[0-9a-zA-Z_-]+$
RewriteCond %{REQUEST_URI} !^/\.well-known/pki-validation/[A-F0-9]{32}\.txt(?:\ Comodo\ DCV)?$
RewriteCond %{REQUEST_URI} !^/\.well-known/cpanel-dcv/[0-9a-zA-Z_-]+$
RewriteCond %{REQUEST_URI} !^/\.well-known/pki-validation/(?:\ Ballot169)?
RewriteRule ^([^/.]+)$ $1.php [L]
# Disables page caching for real-time updating
# <filesMatch "\.(html|htm|js|css|php)$">
# FileETag None
# Header unset ETag
# Header set Cache-Control "max-age=0, no-cache, no-store, must-revalidate"
# Header set Pragma "no-cache"
# Header set Expires "Wed, 11 Jan 1984 05:00:00 GMT"
# </filesMatch>
# Compatibility: Rewrite URLs
Redirect "/nightly" "/compatibility?b"
Redirect "/builds" "/compatibility?b"
Redirect "/compat" "/compatibility"
Redirect "/library" "/compatibility?l"
# Assigns an error page
ErrorDocument 404 /404.php
ErrorDocument 403 /403.php
ErrorDocument 401 /401.php
ErrorDocument 400 /400.php
anyway, the bot has a 403 forbidden error
what could be the mistake?
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.