#8383 – 4SEO - issue getting started 403 error on homepage

Hello Yannick

I have just installed 4seo on my site www.xxxx.com and I have fallen at the first hurdle. The site analysis is stuck at 0% and I am getting a 403 error on the homepage. I think that this might have something to do with a rule in the robots.txt file. From memory my host company put in a number of lines in the robots.txt a few years ago because I was getting a lot of bots visiting the site and eating up the resources. I used to use Jsitemap on this site to create a sitemap, but it is not playing nicely with a component I use called JomHoliday. So that is why I have switched to 4SEO (plus it makes sense given I have used sh404sef for years).

Site details & login

https://www.xxxx.com/administrator/

user: xxxx

pass: xxxx

Thanks

Iain Laverock

Thanks Yannick

Yes, I noticed that issue with the com_installer_type. I can't delete/uninstall it. I think it is a legacy from when I used the Jomres component. That was why I moved to JomHoliday, because Jomres became unworkable. I will contact my host and see if they can have a look at the .htaccess.

Thanks for your help

Iain

Hi Yannick My host thought that they had got 4seo running ok, but it is still triggering a 403 error on the homepage. These are the rules at the top of the .htaccess file. Do you think that they could be preventing 4seo from running properly?

#redirect non-www to www

RewriteEngine On

RewriteCond %{HTTP_HOST} !^www\.

RewriteRule ^(.*)$ https://www.%{HTTP_HOST}/$1 [R=301,L]

#Block all bots except known crawlers

RewriteCond %{HTTP_USER_AGENT} ^$ [OR]

RewriteCond %{HTTP_USER_AGENT} (bot|crawl|robot|spider)

RewriteCond %{HTTP_USER_AGENT} !(uptimerobot|bing|Google|msn|MSR|Twitter|Yandex|Yahoo|Jetpack) [NC]

RewriteRule ^(.*)$ - [F,L]

#SetEnvIfNoCase User-agent guzzlehttp not-allowed=1

#Order Allow,Deny

#Allow from ALL

#Deny from env=not-allowed