Repository navigation
EN FAQ
dongle edited this page Oct 25, 2026
·
4 revisions
This page summarizes common issues users encounter during the configuration and use of SniShaper.
- Cause: MITM/QUIC modes are active without the local CA root certificate being trusted.
-
Solution:
- Click "Certificate Management" -> "Click to Reinstall Certificate".
- Restart your browser.
- Rule Expiry: Built-in rules may become invalid due to network changes or GFW iterations. You can manually fix them (e.g., by changing modes, SNI, or upstream IPs).
- Check Proxy Status: Ensure the "Start Proxy" button on the main dashboard has been clicked.
- Connectivity: Check your network's ability to reach Cloudflare edge IPs.
- Manual Reset: Clear the IP pool and restart the search process.
- Support: Not all websites support ECH. If the connection fails consistently even with optimized IPs, try switching to MITM or TLS-RF mode.
-
No: since v0.7.0
rules/config.jsonis the hand-editable effective state andrules/config.upstream.jsonthe pristine upstream backup (replaced wholesale by updates); your edits/additions/deletions — including direct hand edits of the file — survive updates automatically. - Reverting: to discard the local changes of a single rule, use the "Revert to default" action (history icon) on the Rules page.
- Home
- 完整使用指南
- CLI 命令参考
- 核心模式详解
- 智能分流详解
- 规则自定义指南
- 界面配置指南
- 证书重新安装
- macOS 菜单栏应用
- Linux 软件包
- 代码结构
- Snishaper-Core 核心库
- CI 与 PR 自动化
- 便携式自动更新器
- 常见问题与排障
- Home
- Usage Guide
- CLI Reference
- Core Proxy Modes
- Auto Routing
- Custom Rules Guide
- GUI Configuration
- Certificate Installation
- macOS Menu Bar App
- Linux Packages
- Code Structure
- Snishaper-Core Library
- CI & PR Automation
- Portable Auto-Updater
- FAQ