I ran into a bug on Evebiohaztech that’s stopping the site from working the way it should. It started after I tried using a feature and now pages are acting broken or not loading correctly. I need help figuring out what caused it and how to fix it so the site works normally again.
Start with the boring stuff first.
- Hard refresh the site. Ctrl + F5 on Windows, Cmd + Shift + R on Mac.
- Open it in a private tab. If it works there, your cache, cookies, or an extension is the issue.
- Disable extensions one by one. Ad blockers, script blockers, privacy add-ons break features all the time.
- Check DevTools. Press F12, open Console and Network.
- Look for red errors. Common ones are 404, 500, CORS, failed JS files, or a request stuck pending.
- Test another browser and another device. This tells you fast if the bug is local or site-wide.
- Log out, then back in. If the bug started after using one feature, your session data might be borked.
- Clear site data for Evebiohaztech only, not your whole browser.
If you want people to help fast, post this:
- exact page URL
- what feature you used
- what you expected
- what happened instead
- browser and version
- screenshots
- console errors
- time it happened
If pages are failing with 500s, that points to the site. If only your browser breaks, it’s on your side. If you post the error text, ppl can narrow it down quick.
If it started right after using one feature, I’d stop treating it like a generic browser glitch and assume that feature saved some bad state on your account or in local storage. That’s the part I kinda disagree with when people jump straight to cache stuff. Sometimes it is cache, sure, but a broken saved preference or malformed draft can wreck every page after that.
A few things I’d check that complement what @sterrenkijker said:
- Open DevTools, go to Application or Storage, and look at localStorage/sessionStorage for the site
- Delete only keys that look tied to the feature you used
- If the site has drafts, saved filters, workspace layout, or recent-project data, remove/reset those first
- Check if the URL has weird query params or hashes stuck on it after using the feature
- If you can still hit the API directly in Network, compare a broken page load vs a normal unauthenticated one
- Watch for a bad response payload, not just HTTP errors. A 200 with broken JSON can still nuke the page
- If there’s a service worker, unregister it once. Those things can get cursed real fast lol
- See if your account works on a second account or guest mode. That helps prove whether it’s account-level
If you can, post the exact action that triggered it. “Clicked feature” is too vague tbh. “Imported X, saved Y, then page Z started white-screening” is way more useful. Screenshots of the Console plus the failing request response body would probly narrow it down fast.
I’d test one thing people skip: version mismatch after a partial deploy. I slightly disagree with @sterrenkijker-style storage-first debugging as the first move, because if Evebiohaztech is serving old JS with new API/schema, clearing your stuff won’t fix the root cause.
Check this instead:
- Hard reload and inspect the JS/CSS filenames loaded on a broken page.
- Look for chunk load errors, MIME type errors, or
Unexpected token <in Console. - Compare response headers on working vs broken pages, especially cache-control, etag, and content-type.
- Disable browser extensions, especially ad blockers, privacy filters, script blockers.
- Try another network. Corporate VPN, DNS filtering, or antivirus web shields break sites in weird ways.
- Check system time. Bad clock skew can mess with auth and signed requests.
- If there’s a CSP error, that points to blocked scripts, not bad page data.
For Evebiohaztech bug reports, the most useful bundle is: exact timestamp, browser version, console errors, request IDs, and whether mobile behaves the same.
Pros for ‘’: readable, can help organize the report. Cons for ‘’: no real value if you don’t include technical evidence.