Website not work 403 Forbidden

[Ibrahim2006i]

dooo-admin.rf.gd

i cant enter the website how can i fix it?

[Greenreader9]

Redirected to InfinityFree 403 Forbidden page

While working on your website, you may be redirected to the InfinityFree 403 error page. This article explains why this can happen, and what you can do to solve it. The directory does not contain an index file If you try to request a URL without a file name in the URL (e.g. http://example.com/ or http://example.com/blog/), the server will look for a so-called index file. An index file is a file with the name index.php, index.html, index.htm or index2.html in the folder you’re trying to access.…

[YT_Xaos]

Your website was most likely affected by the outage we had last month:

Website files missing on vol1_7, vol1_8 and vol2_8

Website files missing on vol1_7, vol1_8 and vol2_8 Since the 6th of February, we have been receiving a large number of reports of website files having disappeared from hosting volumes vol1_7, vol1_8 and vol2_8. On hosting volume vol1_7 and vol1_8 it has been confirmed that data corruption problem has occurred, that has resulted in the loss of the files of some accounts on these volumes. iFastNet is currently investigating if any data can be recovered, but this will likely take some time, and it…

[Admin]

I checked your account and the issue is as described in the knowledge base article: no index file is set up.

Seeing how your site appears to be using Laravel, this may solve the issue for you:

.htaccess for Laravel

I was just playing around with a Laravel installation on free hosting. Normally, you should change the document root of your website to the public folder with Laravel. You can’t do this on free hosting, but you can simulate this with .htaccess rules. These are the the .htaccess rules I used: RewriteEngine On RewriteRule (.*) /public/$1 [L] Simply create a file with the name .htaccess and these contents and upload it directly to your htdocs folder. This should rewrite all web requests to the p…

@YT_Xaos

Your website was most likely affected by the outage we had last month

I checked the account and it’s not on the affected volume.

[Ibrahim2006i]

now that appears

[Admin]

I had a look at your site and you appear to have done a lot more than install that .htaccess code I suggested. You also appear to have been modifying the Laravel directory structure, and have been mixing both Laravel’s rules, the rules I suggested, and some other rules entirely.

I think that this has resulted in an invalid .htaccess file, which is why you see that error.

At this point, I would suggest the following:

1. Delete all the files currently there.
2. Upload your Laravel site, without any modifications to make it work on our hosting.
3. Pick one approach to make Laravel work without changing the document root, and apply it.

The method I suggested with the .htaccess file in the htdocs folder is one way to do it, but there are other ways (like moving the contents of the public folder into the htdocs folder and changing the index.php). There are multiple ways to do it, but you need to pick one, not try doing them all at the same time. If you do, you’ll likely end up with, well, something like what you see now.

[Ibrahim2006i]

Is this true what you did? Totally doesn’t work

[ChrisPAR]

What is your current .htaccess configuration, and how are the files and folders of your htdocs directory structured? Can you share the config and screenshots?

[Ibrahim2006i]

[Greenreader9]

You have multiple rewrite engine on lines. You should only have one, before the first line that needs it.

[Ibrahim2006i]

not work…

[KangJL]

What not work?
Write clearly…

And read these again

Website not work 403 Forbidden

I had a look at your site and you appear to have done a lot more than install that .htaccess code I suggested. You also appear to have been modifying the Laravel directory structure, and have been mixing both Laravel’s rules, the rules I suggested, and some other rules entirely. I think that this has resulted in an invalid .htaccess file, which is why you see that error. At this point, I would suggest the following: Delete all the files currently there. Upload your Laravel site, without any …

@Greenreader9

You have multiple rewrite engine on lines

[ChrisPAR]

I believe you’re still doing this:

@Admin

You also appear to have been modifying the Laravel directory structure, and have been mixing both Laravel’s rules, the rules I suggested, and some other rules entirely.

The Admin’s config is this, provided that your Laravel site has its public facing files in a public folder:

@.htaccess for Laravel

RewriteEngine On
RewriteRule (.*) /public/$1 [L]

If this is how your site is structured, then these are the only rules your .htaccess should have after line 3. If you have altered your site’s structure (the files are no longer in a public directory), then this rule can only break your site, not help it, so you should remove it and configure your rules to work well.

[Admin]

I see you made some changes, but haven’t actually done what I told you.

The contents of the public folder are back in their place, but the .htaccess file is still an amalgamation of different .htaccess rules from different guides.

To fix this, I recommend to:

• Delete the current .htaccess file in the public folder and replace it with the default Laravel .htaccess: https://raw.githubusercontent.com/laravel/laravel/11.x/public/.htaccess
• Add a new .htaccess file to the htdocs folder with the rules in the guide.