System requirements
The browsers, cookie and network settings Fuxam Web needs, plus how to fix common problems.
System requirements are the browsers, cookie settings and network conditions Fuxam Web needs to run. Open Fuxam in a supported browser with first-party cookies allowed for fuxam.app. There is nothing to install.
Why it matters
Fuxam Web is a browser app. The wrong browser version, blocked cookies, a strict privacy extension or a firewall that blocks Fuxam domains can stop sign-in, chat or pages from loading. Checking these settings once saves repeated support tickets.
Supported browsers
| Browser | Supported version |
|---|---|
| Google Chrome | 111 or later |
| Microsoft Edge | 111 or later |
| Mozilla Firefox | 111 or later |
| Apple Safari | 16.4 or later |
JavaScript must be turned on. Fuxam has no fallback when scripts are blocked.
Cookie settings
Allow first-party cookies and site data for fuxam.app. Normal sign-in does not need third-party cookies. Sign-in and sign-up run as first-party routes on Fuxam.
Third-party (cross-site) cookies are needed only when you launch Fuxam from an external LMS through LTI. Everyday use does not need them.
| Setting | Why it matters |
|---|---|
| Allow cookies / site data for fuxam.app | Your session lives in first-party cookies. If they are blocked, you cannot sign in or you are signed out right away. |
| Do not clear site data on every visit | Clearing cookies and site data for Fuxam ends your session and resets preferences stored locally. |
| Allow pop-ups for fuxam.app (optional flows) | Sign-in itself does not need pop-ups. Some optional flows (for example Marketplace OAuth or Google Assignments) prefer a pop-up and fall back to a full page if blocked. |
Allow cookies in your browser
Paths vary by browser version. Open your browser's cookie or privacy settings and add an exception for fuxam.app (and [*.]fuxam.app where the browser supports subdomain rules):
- Chrome: Settings → Privacy and security → Cookies (or Third-party cookies) → add a site exception
- Edge: Settings → Cookies and site permissions → manage exceptions for fuxam.app
- Firefox: shield icon on the site, or Settings → Privacy & Security → exceptions
- Safari: Safari → Settings → Privacy → manage website data; allow fuxam.app
Things to avoid
| Avoid | What goes wrong |
|---|---|
| Incognito / private windows | Sessions and site data are cleared when you close the window; third-party cookies are often blocked by default. |
| Strict ad / privacy blockers and tracking modes | Extensions such as uBlock, Ghostery or Brave Shields, and "strict" tracking protection, can block scripts, CDN assets, API calls or WebSockets. Allowlist fuxam.app or turn them off for Fuxam. |
| Page-rewriting extensions | Translate, grammar and autofill tools that rewrite the page can break the React app. |
| Outdated browsers | Versions below the table above are not supported. |
| VPN / proxy / firewall blocking Fuxam | Corporate networks sometimes block Fuxam domains or WebSocket upgrades. See the domain list below. |
Troubleshooting
Try these in order when a page fails to load, sign-in loops, or chat stays offline.
Hard-refresh the page: Ctrl+Shift+R (Windows / Linux) or Cmd+Shift+R (Mac).
Clear cache and cookies for fuxam.app only, then sign in again.
Leave any incognito or private window. Open Fuxam in a normal window.
Disable extensions for this site, or try a fresh browser profile with no extensions.
Allow pop-ups and first-party cookies for fuxam.app.
Try another supported browser, check your connection, and update the browser.
Common pitfalls
| Pitfall | What happens | What to do |
|---|---|---|
| Cookies blocked for fuxam.app | Sign-in fails or you are signed out immediately | Allow first-party cookies / site data for fuxam.app |
| Private / incognito window | Session disappears when the window closes | Use a normal window |
| Ad blocker or strict tracking mode | Blank page, missing UI, or chat offline | Allowlist fuxam.app or disable the blocker for Fuxam |
| Extension rewrites the page | Layout breaks or buttons stop working | Disable translate / grammar / autofill on Fuxam |
| Firewall blocks WebSockets | Chat or the support widget never connects | Ask IT to allow HTTPS and wss to the domains below |
Domains for strict networks
If your institution uses a strict firewall, VPN or proxy, ask IT to allow HTTPS (TCP 443) and secure WebSocket upgrades (wss) to Fuxam and its services. Fuxam needs both for chat and the in-app support widget.
App, API and auth
| Purpose | Domains |
|---|---|
| App and API | fuxam.app, *.fuxam.app, mobile.fuxam.app |
| Auth | clerk.fuxam.app, accounts.google.com (Google SSO) |
Chat, support and payments
| Purpose | Domains |
|---|---|
| Chat | chat.stream-io-api.com (including wss), *.stream-io-cdn.com |
| Support widget | Intercom hosts (including wss) |
| Payments | js.stripe.com, pay.stripe.com |
Files, SCORM and embeds
| Purpose | Domains |
|---|---|
| PDF viewer | cdn.cloud.pspdfkit.com |
| SCORM | scorm.fuxam.app |
| File storage | Cloudflare R2 worker URLs, firebasestorage.googleapis.com |
| Embeds (frames) | YouTube, Vimeo, Loom, Google Docs / Drive / Classroom / Assignments |
FAQ
Do I need third-party cookies for everyday sign-in?
No. Normal Clerk sign-in uses first-party cookies on fuxam.app. Third-party cookies are only required when launching Fuxam from an external LMS (LTI).
Does Fuxam Web use my camera or microphone?
No. Camera and microphone are blocked in the browser. Camera and microphone features belong to the Fuxam mobile app.
Is there a minimum screen size or RAM?
No minimum screen size is required; the layout is responsive. No minimum RAM is stated.
Chat or the support widget will not connect
Those features need HTTPS and secure WebSockets (wss). Check blockers, try another network, and ask IT to allow the chat and support domains above.