403 Forbidden even for a simple static HTML file

Website URL

https://mojpiespl.free.je

Error Message

403 Forbidden

Other Information

Current issue

The website returns 403 Forbidden.

The same 403 error occurs for the simple static test.html file, so the problem does not appear to be related to Site.pro or PHP.

Expected behavior

The static HTML file should open normally in the browser.

Attempted solutions
Confirmed that the hosting account is Active.
Confirmed that the domain points to htdocs.
Confirmed that index.php exists directly in htdocs.
Checked the .htaccess file.
Deleted index2.html.
Created a simple static test.html file in htdocs.
The static HTML file also returns 403.

Could you please check whether there is a server-side or account/domain configuration issue causing the 403 error?

Welcome to the InfinityFree community forum! Good to have you here.

  • Most people answering here are volunteers. They’re often the fastest source of help. Admin (the only staff member) checks in about once a day for issues on our end.
  • Volunteers can’t see your account or website. Share what you actually see, like error messages and what happens when you try something. That’s more useful than your theory of what’s wrong.
  • AI tools often get InfinityFree wrong. If a volunteer’s advice differs from what an AI told you, please try the volunteer’s suggestion first.
  • Solving an issue is a joint effort. Try the suggestions you get and report back what happened.

Welcome to the forum

It’s worth having a read through this article from admin to make sure you’ve tried everything

If that doesn’t work. It’s also worth double checking if your dashboard has any reports or banners showing

I checked your website and it seems to be working fine from here. I just see a Site.Pro website, no 403 page.

Do you still get the 403 page? Because if so, it’s not your website that’s down, it’s something specific to your connection.

If so, can you also share a screenshot of the exact 403 page you see? That might give us some clues as to what could be producing that 403 page.