Parse config error: proxy 0: 'ws-opts.headers' expected a map, got 'string
See original GitHub issue内核日志提示: 2021-11-19 12:06:13 level=fatal msg=“Parse config error: proxy 0: ‘ws-opts.headers’ expected a map, got ‘string’” 2021-11-19 12:06:08 level=fatal msg=“Parse config error: proxy 0: ‘ws-opts.headers’ expected a map, got ‘string’”
设置项:ws-opts-headers
卡这里了,不管如何设置都报错
日志: OpenClash 调试日志
生成时间: 2021-11-19 12:19:03 插件版本: v0.43.09-beta 隐私提示: 上传此日志前请注意检查、屏蔽公网IP、节点、密码等相关敏感信息
#===================== 系统信息 =====================#
主机型号: Intel(R) Core(TM) i5 CPU @ 2.90GHz : 6 Core 12 Thread
固件版本: OpenWrt SNAPSHOT r3900-95a749a92
LuCI版本: git-21.320.49600-21168d4-1
内核版本: 5.4.158
处理器架构: x86_64
#此项有值时,如不使用IPv6,建议到网络-接口-lan的设置中禁用IPV6的DHCP
IPV6-DHCP:
#此项结果应仅有配置文件的DNS监听地址
Dnsmasq转发设置: 127.0.0.1#5333
#===================== 依赖检查 =====================#
dnsmasq-full: 已安装
coreutils: 已安装
coreutils-nohup: 已安装
bash: 已安装
curl: 已安装
ca-certificates: 已安装
ipset: 已安装
ip-full: 已安装
iptables-mod-tproxy: 已安装
kmod-ipt-tproxy: 已安装
iptables-mod-extra: 已安装
kmod-ipt-extra: 已安装
libcap: 已安装
libcap-bin: 已安装
ruby: 已安装
ruby-yaml: 已安装
ruby-psych: 已安装
ruby-pstore: 已安装
ruby-dbm: 已安装
kmod-tun(TUN模式): 已安装
luci-compat(Luci-19.07): 已安装
#===================== 内核检查 =====================#
运行状态: 未运行
已选择的架构: linux-amd64
#下方无法显示内核版本号时请确认您的内核版本是否正确或者有无权限
Tun内核版本: 2021.09.15
Tun内核文件: 存在
Tun内核运行权限: 正常
Dev内核版本: v1.7.1-24-gebbc960
Dev内核文件: 存在
Dev内核运行权限: 正常
#===================== 插件设置 =====================#
当前配置文件: /etc/openclash/config/config.yaml
启动配置文件: /etc/openclash/config.yaml
运行模式: redir-host
默认代理模式: rule
UDP流量转发(tproxy): 停用
DNS劫持: 启用
自定义DNS: 停用
IPV6代理: 停用
IPV6-DNS解析: 停用
禁用Dnsmasq缓存: 停用
自定义规则: 停用
仅允许内网: 停用
仅代理命中规则流量: 停用
仅允许常用端口流量: 停用
绕过中国大陆IP: 停用
#启动异常时建议关闭此项后重试
混合节点: 停用
保留配置: 停用
#启动异常时建议关闭此项后重试
第三方规则: 启用
#===================== 配置文件 =====================#
proxy-groups:
- name: Auto - UrlTest
type: url-test
proxies:
- HI-TEST
url: https://cp.cloudflare.com/generate_204
interval: '600'
tolerance: '150'
- name: Proxy
type: select
proxies:
- Auto - UrlTest
- DIRECT
- HI-TEST
- name: Domestic
type: select
proxies:
- DIRECT
- Proxy
- name: Others
type: select
proxies:
- Proxy
- DIRECT
- Domestic
- name: Microsoft
type: select
proxies:
- DIRECT
- Proxy
- name: Apple
type: select
proxies:
- DIRECT
- Proxy
- HI-TEST
- name: Scholar
type: select
proxies:
- DIRECT
- Proxy
- HI-TEST
- name: Bilibili
type: select
proxies:
- AsianTV
- DIRECT
- HI-TEST
- name: Bahamut
type: select
proxies:
- GlobalTV
- DIRECT
- HI-TEST
- name: HBO
type: select
proxies:
- GlobalTV
- DIRECT
- HI-TEST
- name: Pornhub
type: select
proxies:
- GlobalTV
- DIRECT
- HI-TEST
- name: Netflix
type: select
proxies:
- GlobalTV
- DIRECT
- HI-TEST
- name: Disney
type: select
proxies:
- GlobalTV
- DIRECT
- HI-TEST
- name: Youtube
type: select
disable-udp: true
proxies:
- GlobalTV
- DIRECT
- HI-TEST
- name: Spotify
type: select
proxies:
- GlobalTV
- DIRECT
- HI-TEST
- name: Steam
type: select
proxies:
- DIRECT
- Proxy
- HI-TEST
- name: AdBlock
type: select
proxies:
- REJECT
- DIRECT
- Proxy
- name: AsianTV
type: select
proxies:
- DIRECT
- Proxy
- HI-TEST
- name: GlobalTV
type: select
proxies:
- Proxy
- DIRECT
- HI-TEST
- name: Speedtest
type: select
proxies:
- Proxy
- DIRECT
- HI-TEST
- name: Telegram
type: select
proxies:
- Proxy
- DIRECT
- HI-TEST
- name: PayPal
type: select
proxies:
- DIRECT
- Proxy
- HI-TEST
rules:
#===================== 防火墙设置 =====================#
#IPv4 NAT chain
# Generated by iptables-save v1.8.7 on Fri Nov 19 12:19:04 2021
*nat
:PREROUTING ACCEPT [20464:973590]
:INPUT ACCEPT [17635:864691]
:OUTPUT ACCEPT [371:27306]
:POSTROUTING ACCEPT [161:11489]
:MINIUPNPD - [0:0]
:MINIUPNPD-POSTROUTING - [0:0]
:postrouting_VPN_rule - [0:0]
:postrouting_docker_rule - [0:0]
:postrouting_lan_rule - [0:0]
:postrouting_rule - [0:0]
:postrouting_vpn_rule - [0:0]
:postrouting_wan_rule - [0:0]
:prerouting_VPN_rule - [0:0]
:prerouting_docker_rule - [0:0]
:prerouting_lan_rule - [0:0]
:prerouting_rule - [0:0]
:prerouting_vpn_rule - [0:0]
:prerouting_wan_rule - [0:0]
:zone_VPN_postrouting - [0:0]
:zone_VPN_prerouting - [0:0]
:zone_docker_postrouting - [0:0]
:zone_docker_prerouting - [0:0]
:zone_lan_postrouting - [0:0]
:zone_lan_prerouting - [0:0]
:zone_vpn_postrouting - [0:0]
:zone_vpn_prerouting - [0:0]
:zone_wan_postrouting - [0:0]
:zone_wan_prerouting - [0:0]
-A PREROUTING -m comment --comment "!fw3: Custom prerouting rule chain" -j prerouting_rule
-A PREROUTING -i br-lan -m comment --comment "!fw3" -j zone_lan_prerouting
-A PREROUTING -i eth1 -m comment --comment "!fw3" -j zone_wan_prerouting
-A PREROUTING -i docker0 -m comment --comment "!fw3" -j zone_docker_prerouting
-A PREROUTING -p udp -m udp --dport 53 -j REDIRECT --to-ports 53
-A PREROUTING -p tcp -m tcp --dport 53 -j REDIRECT --to-ports 53
-A POSTROUTING -m comment --comment "!fw3: Custom postrouting rule chain" -j postrouting_rule
-A POSTROUTING -o br-lan -m comment --comment "!fw3" -j zone_lan_postrouting
-A POSTROUTING -o eth1 -m comment --comment "!fw3" -j zone_wan_postrouting
-A POSTROUTING -o docker0 -m comment --comment "!fw3" -j zone_docker_postrouting
-A zone_VPN_postrouting -m comment --comment "!fw3: Custom VPN postrouting rule chain" -j postrouting_VPN_rule
-A zone_VPN_prerouting -m comment --comment "!fw3: Custom VPN prerouting rule chain" -j prerouting_VPN_rule
-A zone_docker_postrouting -m comment --comment "!fw3: Custom docker postrouting rule chain" -j postrouting_docker_rule
-A zone_docker_prerouting -m comment --comment "!fw3: Custom docker prerouting rule chain" -j prerouting_docker_rule
-A zone_lan_postrouting -m comment --comment "!fw3: Custom lan postrouting rule chain" -j postrouting_lan_rule
-A zone_lan_prerouting -m comment --comment "!fw3: Custom lan prerouting rule chain" -j prerouting_lan_rule
-A zone_vpn_postrouting -m comment --comment "!fw3: Custom vpn postrouting rule chain" -j postrouting_vpn_rule
-A zone_vpn_postrouting -m comment --comment "!fw3" -j FULLCONENAT
-A zone_vpn_prerouting -m comment --comment "!fw3: Custom vpn prerouting rule chain" -j prerouting_vpn_rule
-A zone_vpn_prerouting -m comment --comment "!fw3" -j FULLCONENAT
-A zone_wan_postrouting -j MINIUPNPD-POSTROUTING
-A zone_wan_postrouting -m comment --comment "!fw3: Custom wan postrouting rule chain" -j postrouting_wan_rule
-A zone_wan_postrouting -m comment --comment "!fw3" -j FULLCONENAT
-A zone_wan_prerouting -j MINIUPNPD
-A zone_wan_prerouting -m comment --comment "!fw3: Custom wan prerouting rule chain" -j prerouting_wan_rule
-A zone_wan_prerouting -m comment --comment "!fw3" -j FULLCONENAT
COMMIT
# Completed on Fri Nov 19 12:19:04 2021
#IPv4 Mangle chain
# Generated by iptables-save v1.8.7 on Fri Nov 19 12:19:04 2021
*mangle
:PREROUTING ACCEPT [44647:10307445]
:INPUT ACCEPT [39918:9730137]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [36691:19988384]
:POSTROUTING ACCEPT [37185:20006624]
:RRDIPT_FORWARD - [0:0]
:RRDIPT_INPUT - [0:0]
:RRDIPT_OUTPUT - [0:0]
-A INPUT -j RRDIPT_INPUT
-A FORWARD -j RRDIPT_FORWARD
-A FORWARD -o eth1 -p tcp -m tcp --tcp-flags SYN,RST SYN -m comment --comment "!fw3: Zone wan MTU fixing" -j TCPMSS --clamp-mss-to-pmtu
-A FORWARD -i eth1 -p tcp -m tcp --tcp-flags SYN,RST SYN -m comment --comment "!fw3: Zone wan MTU fixing" -j TCPMSS --clamp-mss-to-pmtu
-A OUTPUT -j RRDIPT_OUTPUT
-A RRDIPT_FORWARD -s 192.168.0.171/32 -j RETURN
-A RRDIPT_FORWARD -d 192.168.0.171/32 -j RETURN
-A RRDIPT_FORWARD -s 192.168.0.252/32 -j RETURN
-A RRDIPT_FORWARD -d 192.168.0.252/32 -j RETURN
-A RRDIPT_FORWARD -s 192.168.0.254/32 -j RETURN
-A RRDIPT_FORWARD -d 192.168.0.254/32 -j RETURN
-A RRDIPT_FORWARD -s 192.168.0.247/32 -j RETURN
-A RRDIPT_FORWARD -d 192.168.0.247/32 -j RETURN
-A RRDIPT_FORWARD -s 192.168.0.1/32 -j RETURN
-A RRDIPT_FORWARD -d 192.168.0.1/32 -j RETURN
-A RRDIPT_FORWARD -s 192.168.0.3/32 -j RETURN
-A RRDIPT_FORWARD -d 192.168.0.3/32 -j RETURN
-A RRDIPT_FORWARD -s 192.168.0.11/32 -j RETURN
-A RRDIPT_FORWARD -d 192.168.0.11/32 -j RETURN
-A RRDIPT_FORWARD -s 192.168.0.111/32 -j RETURN
-A RRDIPT_FORWARD -d 192.168.0.111/32 -j RETURN
-A RRDIPT_FORWARD -s 192.168.0.112/32 -j RETURN
-A RRDIPT_FORWARD -d 192.168.0.112/32 -j RETURN
-A RRDIPT_INPUT -i eth0 -j RETURN
-A RRDIPT_INPUT -i eth1 -j RETURN
-A RRDIPT_OUTPUT -o eth0 -j RETURN
-A RRDIPT_OUTPUT -o eth1 -j RETURN
COMMIT
# Completed on Fri Nov 19 12:19:04 2021
#IPv6 NAT chain
# Generated by ip6tables-save v1.8.7 on Fri Nov 19 12:19:04 2021
*nat
:PREROUTING ACCEPT [373:62908]
:INPUT ACCEPT [70:10005]
:OUTPUT ACCEPT [65:5512]
:POSTROUTING ACCEPT [65:5512]
-A PREROUTING -p udp -m udp --dport 53 -j REDIRECT --to-ports 53
-A PREROUTING -p tcp -m tcp --dport 53 -j REDIRECT --to-ports 53
COMMIT
# Completed on Fri Nov 19 12:19:04 2021
#IPv6 Mangle chain
# Generated by ip6tables-save v1.8.7 on Fri Nov 19 12:19:04 2021
*mangle
:PREROUTING ACCEPT [1067:151692]
:INPUT ACCEPT [602:74524]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [336:35822]
:POSTROUTING ACCEPT [336:35822]
-A FORWARD -o eth1 -p tcp -m tcp --tcp-flags SYN,RST SYN -m comment --comment "!fw3: Zone wan MTU fixing" -j TCPMSS --clamp-mss-to-pmtu
-A FORWARD -i eth1 -p tcp -m tcp --tcp-flags SYN,RST SYN -m comment --comment "!fw3: Zone wan MTU fixing" -j TCPMSS --clamp-mss-to-pmtu
COMMIT
# Completed on Fri Nov 19 12:19:04 2021
#===================== IPSET状态 =====================#
Name: cn
Name: ct
Name: cnc
Name: cmcc
Name: crtc
Name: cernet
Name: gwbn
Name: othernet
Name: music
Name: mwan3_connected_v4
Name: mwan3_connected_v6
Name: mwan3_source_v6
Name: mwan3_dynamic_v4
Name: mwan3_dynamic_v6
Name: mwan3_custom_v4
Name: mwan3_custom_v6
Name: china
Name: mwan3_connected
#===================== 路由表状态 =====================#
#route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 192.168.0.112 0.0.0.0 UG 0 0 0 eth1
172.17.0.0 0.0.0.0 255.255.0.0 U 0 0 0 docker0
192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 br-lan
192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1
#ip route list
default via 192.168.0.112 dev eth1 proto static src 192.168.0.3
172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown
192.168.0.0/24 dev br-lan proto kernel scope link src 192.168.0.1
192.168.0.0/24 dev eth1 proto kernel scope link src 192.168.0.3
#ip rule show
0: from all lookup local
32766: from all lookup main
32767: from all lookup default
#===================== 端口占用状态 =====================#
#===================== 测试本机DNS查询 =====================#
Server: 127.0.0.1
Address: 127.0.0.1:53
Non-authoritative answer:
www.baidu.com canonical name = www.a.shifen.com
Name: www.a.shifen.com
Address: 14.215.177.38
Name: www.a.shifen.com
Address: 14.215.177.39
Non-authoritative answer:
www.baidu.com canonical name = www.a.shifen.com
#===================== resolv.conf.d =====================#
# Interface wan
nameserver 61.128.128.68
search lan
#===================== 测试本机网络连接 =====================#
HTTP/1.1 200 OK
Accept-Ranges: bytes
Cache-Control: private, no-cache, no-store, proxy-revalidate, no-transform
Connection: keep-alive
Content-Length: 277
Content-Type: text/html
Date: Fri, 19 Nov 2021 04:19:04 GMT
Etag: "575e1f72-115"
Last-Modified: Mon, 13 Jun 2016 02:50:26 GMT
Pragma: no-cache
Server: bfe/1.0.8.18
#===================== 测试本机网络下载 =====================#
HTTP/1.1 200 OK
Connection: keep-alive
Content-Length: 80
Cache-Control: max-age=300
Content-Security-Policy: default-src 'none'; style-src 'unsafe-inline'; sandbox
Content-Type: text/plain; charset=utf-8
ETag: "ade92b0bfd2951f6f2167a0db2526a0ba2121e8ae1a073846f6c9c10d3849c05"
Strict-Transport-Security: max-age=31536000
X-Content-Type-Options: nosniff
X-Frame-Options: deny
X-XSS-Protection: 1; mode=block
X-GitHub-Request-Id: A6E0:17A2:40BA6:EDDC5:6196ED68
Accept-Ranges: bytes
Date: Fri, 19 Nov 2021 04:19:05 GMT
Via: 1.1 varnish
X-Served-By: cache-tyo11923-TYO
X-Cache: HIT
X-Cache-Hits: 1
X-Timer: S1637295545.153818,VS0,VE0
Vary: Authorization,Accept-Encoding,Origin
Access-Control-Allow-Origin: *
X-Fastly-Request-ID: 5b84845274f66c7f18a87694761586888beb0b7f
Expires: Fri, 19 Nov 2021 04:24:05 GMT
Source-Age: 1
#===================== 最近运行日志 =====================#
2021-11-19 12:10:47 Step 5: Check The Core Status...
time="2021-11-19T04:10:47Z" level=fatal msg="Parse config error: proxy 0: 'ws-opts.headers' expected a map, got 'string'"
2021-11-19 12:10:51 Step 6: Wait For The File Downloading...
2021-11-19 12:10:51 Error: OpenClash Can Not Start, Try Use Backup Rules Start Again...
2021-11-19 12:10:51 Tip: Detected The Exclusive Function of The TUN Core, Use TUN Core to Start...
time="2021-11-19T04:10:51Z" level=fatal msg="Parse config error: proxy 0: 'ws-opts.headers' expected a map, got 'string'"
2021-11-19 12:10:55 Error: OpenClash Can Not Start, Try Use Raw Config Restart Again...
2021-11-19 12:10:55 Error: Get DNS 'listen' Option Error, OpenClash Can Not Start With Raw Config File
2021-11-19 12:10:57 Error: Get DNS 'enhanced-mode' Option Error, OpenClash Can Not Start With Raw Config File
2021-11-19 12:10:59 Error: Get General 'redir-port' Option Error, OpenClash Can Not Start With Raw Config File
2021-11-19 12:11:01 OpenClash Stoping...
2021-11-19 12:11:01 Step 1: Backup The Current Groups State...
2021-11-19 12:11:01 Step 2: Delete OpenClash Firewall Rules...
2021-11-19 12:11:02 Step 3: Close The OpenClash Daemons...
2021-11-19 12:11:02 Step 4: Close The Clash Core Process...
2021-11-19 12:11:02 Step 5: Restart Dnsmasq...
2021-11-19 12:11:02 Step 6: Delete OpenClash Residue File...
2021-11-19 12:15:13 OpenClash Stoping...
2021-11-19 12:15:13 Step 1: Backup The Current Groups State...
2021-11-19 12:15:13 Step 2: Delete OpenClash Firewall Rules...
2021-11-19 12:15:14 Step 3: Close The OpenClash Daemons...
2021-11-19 12:15:14 Step 4: Close The Clash Core Process...
2021-11-19 12:15:14 Step 5: Restart Dnsmasq...
2021-11-19 12:15:14 Step 6: Delete OpenClash Residue File...
2021-11-19 12:15:14 OpenClash Start Running...
2021-11-19 12:15:14 Step 1: Get The Configuration...
2021-11-19 12:15:14 Step 2: Check The Components...
2021-11-19 12:15:14 Step 3: Modify The Config File...
2021-11-19 12:15:15 Step 4: Start Running The Clash Core...
2021-11-19 12:15:15 Tip: Detected The Exclusive Function of The TUN Core, Use TUN Core to Start...
2021-11-19 12:15:15 Step 5: Check The Core Status...
time="2021-11-19T04:15:15Z" level=fatal msg="Parse config error: proxy 0: 'ws-opts.headers' expected a map, got 'string'"
2021-11-19 12:15:19 Step 6: Wait For The File Downloading...
2021-11-19 12:15:19 Error: OpenClash Can Not Start, Try Use Backup Rules Start Again...
2021-11-19 12:15:19 Tip: Detected The Exclusive Function of The TUN Core, Use TUN Core to Start...
time="2021-11-19T04:15:19Z" level=fatal msg="Parse config error: proxy 0: 'ws-opts.headers' expected a map, got 'string'"
2021-11-19 12:15:23 Error: OpenClash Can Not Start, Try Use Raw Config Restart Again...
2021-11-19 12:15:23 Error: Get DNS 'listen' Option Error, OpenClash Can Not Start With Raw Config File
2021-11-19 12:15:25 Error: Get DNS 'enhanced-mode' Option Error, OpenClash Can Not Start With Raw Config File
2021-11-19 12:15:27 Error: Get General 'redir-port' Option Error, OpenClash Can Not Start With Raw Config File
2021-11-19 12:15:29 OpenClash Stoping...
2021-11-19 12:15:29 Step 1: Backup The Current Groups State...
2021-11-19 12:15:29 Step 2: Delete OpenClash Firewall Rules...
2021-11-19 12:15:30 Step 3: Close The OpenClash Daemons...
2021-11-19 12:15:30 Step 4: Close The Clash Core Process...
2021-11-19 12:15:30 Step 5: Restart Dnsmasq...
2021-11-19 12:15:30 Step 6: Delete OpenClash Residue File...
2021-11-19 12:18:34 【Dev】Core Has Not Been Updated, Stop Continuing Operation!
2021-11-19 12:18:34 【TUN】Core Has Not Been Updated, Stop Continuing Operation!
2021-11-19 12:18:37 OpenClash Has not Been Updated, Stop Continuing!
#===================== 活动连接信息 =====================#
Issue Analytics
- State:
- Created 2 years ago
- Comments:11 (5 by maintainers)
Top Results From Across the Web
[Bug]Parse config error #1878 - vernesong/OpenClash - GitHub
When create proxy through GUI Servers and Groups if there is 2 proxy with partially identical name Openclash wont start with Parse config...
Read more >Could not parse http response. expected a header value for ...
A detailed guide on how to resolve errors related to "could not parse http response. expected a header value for header"
Read more >ATS V1.5) Enterprise Transport API C Edition 3.6.7.L1
Information about the Login domain and expected content formatting is available in the Enterprise Transport API C Edition Refinitiv Domain.
Read more >HTTP - Rosetta Code
Task Access and print a URL's content (the located resource) to the console. There is a separate task for HTTPS Requests.
Read more >Check-in [a73b896a5e] - cycu.org
proxy ws to wsss on 23030 check-in: dd3470bc81 user: pj2022 tags: trunk ... JSON.parse(data); } var wsOpts = { packMessage, unpackMessage, ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
中间少了空格
ok,it would be fixed in next release