A Guide to DevTools

🧪 Debugging Network Errors with DevTools

Sometimes Janitor hides the real error when it doesn’t recognize the format. DevTools lets you peek behind the scenes and figure out exactly what’s going wrong, especially helpful when nothing else works.

Step 1: Open DevTools

Go to any bot chat on Janitor. Once the page loads, right click with your mouse and click on inspect element. You should see a panel pop up.

Step 2: Switch to the “Network” tab

At the top of the DevTools window, click the Network tab.

Step 3: Reset the data

Click the circle icon (🔴), it should be red, meaning it’s actively tracking requests.

Then click the (🚫) clear icon to wipe out any old data.

Step 4: Send a message to the bot

Now, type anything in chat and hit Send.

You’ll see one or more new lines appear in DevTools, usually a /generateAlpha, /proxy, or /completions entry depending on your setup.

Step 5: Check the status of the request

Look at the Status column. If the request failed, you’ll see something like NAME_NOT_RESOLVED or 400 codes. Click on the error and then the Response tab (near Headers and Preview). This is where the real error lives, the one Janitor may have swallowed. Copy everything in this tab and send it to someone helping you troubleshoot. It often gives the exact reason the request failed (wrong model name, bad API URL, missing key, etc.).

Updated on: 03/08/2025