【已解答】突然导致所有站点访问显示403/nginx，重启也无用
为了能快速了解并处理您的问题，请提供以下基础信息：面板、插件版本：宝塔：v11.3.0
nginx：1.20.1
系统版本：
centos 8.6
问题描述：
所有站点原本访问正常，但是突然出现403，重启nginx无效，更新nginx升级到1.20.2仍然一样。最终重启服务器解决
相关截图（日志、错误）：
/www/wwwlogs/nginx_error.log
86 thread '<unnamed>' panicked at src/parser/expressions.rs:208:33:
87 invalid octal integer literal: `&2`
88
89 thread '<unnamed>' panicked at src/parser/expressions.rs:208:33:
90 invalid octal integer literal: `&1`
91
92 thread '<unnamed>' panicked at src/parser/expressions.rs:208:33:
93 invalid octal integer literal: `&7`
94
95 thread '<unnamed>' panicked at src/parser/expressions.rs:208:33:
96 invalid octal integer literal: `&3`
97
98 thread '<unnamed>' panicked at src/parser/expressions.rs:208:33:
99 invalid octal integer literal: `&5`
100
101 thread '<unnamed>' panicked at src/parser/expressions.rs:208:33:
102 invalid octal integer literal: `&5`
103
104 thread '<unnamed>' panicked at src/parser/expressions.rs:208:33:
105 invalid octal integer literal: `&1`
106
107 thread '<unnamed>' panicked at src/parser/expressions.rs:208:33:
108 invalid octal integer literal: `&7`
109
110 thread '<unnamed>' panicked at src/parser/expressions.rs:208:33:
111 invalid octal integer literal: `&2`
112
113 thread '<unnamed>' panicked at src/parser/expressions.rs:208:33:
114 invalid octal integer literal: `&5`
115
116 thread '<unnamed>' panicked at src/parser/expressions.rs:208:33:
117 invalid octal integer literal: `&1`
118
119 thread '<unnamed>' panicked at src/parser/expressions.rs:208:33:
120 invalid octal integer literal: `&2`
121
122 thread '<unnamed>' panicked at src/parser/expressions.rs:208:33:
123 invalid octal integer literal: `&5`
124
125 thread '<unnamed>' panicked at src/parser/expressions.rs:208:33:
126 invalid octal integer literal: `&5`
127
128 thread '<unnamed>' panicked at src/parser/expressions.rs:208:33:
129 invalid octal integer literal: `&2`
130
131 thread '<unnamed>' panicked at src/parser/expressions.rs:208:33:
132 invalid octal integer literal: `&2`
133
134 thread '<unnamed>' panicked at src/parser/expressions.rs:208:33:
135 invalid octal integer literal: `&1`
136
137 thread '<unnamed>' panicked at src/parser/expressions.rs:208:33:
138 invalid octal integer literal: `&2`
139
140 thread '<unnamed>' panicked at src/parser/expressions.rs:208:33:
141 invalid octal integer literal: `&1`
142
144 invalid octal integer literal: `&2`
145
146 thread '<unnamed>' panicked at src/parser/expressions.rs:208:33:
147 invalid octal integer literal: `&6`
148
149 thread '<unnamed>' panicked at src/parser/expressions.rs:208:33:
150 invalid octal integer literal: `&1`
151 invalid stream version invalid stream version [] invalid stream version [] invalid stream version invalid stream version invalid stream version [] invalid stre am version [] invalid stream version invalid stream version invalid stream version invalid stream version invalid stream version invalid stream ve rsion invalid stream version invalid stream version invalid stream version invalid stream version invalid stream version invalid stream v ersion
152 thread '<unnamed>' panicked at src/lexer/generated.rs:458:32:
153 not implemented: KwLike
154 note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
155 invalid stream version
156 thread '<unnamed>' panicked at src/lexer/generated.rs:486:32:
157 not implemented: KwStatic
158
159 thread '<unnamed>' panicked at src/parser/hierarchy.rs:366:18:
160 Expected `explicit` after `option`
161
162 thread '<unnamed>' panicked at src/parser/hierarchy.rs:366:18:
163 Expected `explicit` after `option`
164
165 thread '<unnamed>' panicked at src/parser/hierarchy.rs:366:18:
166 Expected `explicit` after `option`
167 invalid stream version invalid stream version invalid stream version invalid stream version invalid stream version invalid stream version invalid stream version invalid stream version invalid stream version invalid stream version
168 thread '<unnamed>' panicked at src/parser/hierarchy.rs:366:18:
169 Expected `explicit` after `option`
170 note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
171
172 thread '<unnamed>' panicked at src/lexer/generated.rs:458:32:
173 not implemented: KwLike
174
175 thread '<unnamed>' panicked at src/parser/hierarchy.rs:366:18:
176 Expected `explicit` after `option`
177
178 thread '<unnamed>' panicked at src/lexer/generated.rs:486:32:
179 not implemented: KwStatic
180 invalid stream version
181 thread '<unnamed>' panicked at src/parser/hierarchy.rs:366:18:
182 Expected `explicit` after `option`
183
184 thread '<unnamed>' panicked at src/lexer/generated.rs:434:32:
185 not implemented: KwCurrency
186 note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
187
188 thread '<unnamed>' panicked at src/parser/hierarchy.rs:366:18:
189 Expected `explicit` after `option`
190 invalid stream version invalid stream version invalid stream version invalid stream version invalid stream version invalid stream version [] invalid stream version invalid stream version []
191 thread '<unnamed>' panicked at src/parser/expressions.rs:208:33:
192 invalid octal integer literal: `&2`
193 note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
194
195 thread '<unnamed>' panicked at src/parser/expressions.rs:208:33:
196 invalid octal integer literal: `&1`
197
上面的信息中没有关于403 的
403错误是HTTP状态代码之一，通常表示"禁止访问"或"拒绝访问"。当你的网站返回403错误时，意味着您当前没有权限访问请求的页面或资源。
1.权限设置不正确：这是最常见的原因之一，如果请求的资源的权限设置禁止公共访问，那么当用户尝试访问它时就会返回403错误，另外，如果站点目录的权限不是www用户权限也有可能触发该问题。您可以检查一下您的站点目录是否拥有足够的运行访问权限。
2.未经授权的访问：如果您的网站要求用户进行身份验证或登录才能访问特定的页面或资源，用户未登录或没有必要的权限，就会返回403错误。您可以检查一下您当前站点是否有针对性设置了“访问限制”功能呢？
3.IP地址受限：如果您的站点设置了指定的IP名单访问，那么在这IP名单外的就可能会导致403错误。您可以检查一下您的站点配置是否设置了限制IP名单访问，如果有的话可以先临时解除相关限制排查。
4.网站防火墙规则：如果您使用了Nginx/Apache防火墙，可能触发了防火墙规则导致的403错误。可以检查一下Nginx/Apache防火墙的拦截日志是否触发了拦截规则。
5.站点配置错误：错误的服务器配置可能会导致意外的403错误。这可能包括错误的目录索引设置、不正确的访问控制规则等。您可以检查一下您的站点配置是否设置正确。
总得来说，403通常表示"禁止访问"或"拒绝访问"网站的403错误，通常可以通过网站日志来进行排查。网站日志记录了来自访问者的请求以及服务器对这些请求的响应。通过分析网站日志，你可以获得关于403错误的有用信息，通过逐步排
页:
[1]