: Settings are managed in src/config.js , or by creating a config.js in the root folder to override defaults. Use Cases and Safety
If you choose to use Rammerhead, follow these best practices to minimize risk: rammerhead proxy
| Problem | Likely Cause | Solution | |---------|--------------|----------| | Blank white page | Site uses unsupported features | Refresh or try a different site. | | "ERR_CERT_AUTHORITY_INVALID" | Proxy uses self-signed SSL | On the warning page, click "Proceed anyway". | | Very slow loading | Public instance overloaded | Host your own or find a less popular instance. | | Infinite redirect loop | Site detects proxy | Use the "Reset Session" button if available. | | Login fails | Cross-domain cookie issues | Try using the proxied site's "Login" page directly (not a popup). | : Settings are managed in src/config
While the technology is impressive, using Rammerhead—especially public instances—comes with serious caveats. | | Very slow loading | Public instance