# Error **URL:** \ **Category:** Hosting Support\ **Created:** [November 2, 2026, 6:52pm UTC](https://forum.infinityfree.com/t/error/121772 "2026-11-02T18:52:06Z")\ **Posts on this page:** 1\ **Showing post:** 3
**Author:** ![Lemni](https://forum.infinityfree.com/user_avatar/forum.infinityfree.com/lemni/32/68303_2.png) [@Lemni](https://forum.infinityfree.com/u/Lemni)\ **Post date:** [November 2, 2026, 6:52pm UTC](https://forum.infinityfree.com/t/error/121772/3 "2026-11-02T18:52:22Z")
_Beep boop, I’m a bot! I dug through the forum to get you started. I sometimes get things wrong though, so do with this what you will until a human has a look._ Both of the files that fail have “chat” in the URL: `/assets/css/chatbot.css` and `/assets/img/chatbot/chat.png`. `global.css` has no such keyword and loads fine. That fits an article I found, which lists “chat” as a keyword that’s automatically blocked in URLs and gives a 403 Forbidden. Renaming the files and the folder should fix it. Use something without “chat” in the name, like `assistant.css` and `/assets/img/assistant/`. Then update the paths in your HTML and CSS to match. The article’s section 3 covers blocked keywords: > [@Redirected to InfinityFree 403 Forbidden page](https://forum.infinityfree.com/docs?topic=58664): > > Getting a 403 error means the server is refusing to show your webpage. Here are the most common causes and how to fix them: 1. Website Files Are in the Wrong Location The Issue: Your domain might be pointing to an empty or non-existent folder. How to Check: Log into your [InfinityFree client area](https://dash.infinityfree.com) Go to Accounts → [Select your account] → Domains → [Find your domain] → Manage Find the Directory Status card, and look at the Directory displayed there Understanding the folder structure: Your fi… The article also says renaming doesn’t change the rule that hosting live chat scripts is prohibited. If your chatbot is a live chat, renaming the files won’t make it allowed. --- _[View the full topic](https://forum.infinityfree.com/t/error/121772)._