当前位置:论坛首页 > BUG提交 > Linux面板

【待反馈】升级7.9.7后,登录界面陷入死循环

发表在 BUG提交2022-12-21 18:11 [复制链接] 4 2782

半个小时前升级7.9.7,然后登录界面就陷入了死循环
修改过默认端口,加过安全入口,开启过BasicAuth认证
现在的状况是,先经过BasicAuth认证登录,然后进入面板登录界面,登录后,又跳出BasicAuth认证登录框,一直死循环,无法进入到面板
iShot_2022-12-21_18.07.16.png
反复死循环后,面板登录界面还会提示密码错误,重启bt后又可以正常登录,然后继续上面的死循环……然后再出现下图的密码错误……
iShot_2022-12-21_17.55.41.png
尝试过重启云主机、ssh进终端,命令行重启bt,问题依旧,

最后尝试过在终端输入bt 23,关闭BasicAuth认证,

通过面板登录,输入账密,登入后,会自动跳回面板登录界面,然后继续死循环了……


下面是bt 22输出的信息
  File "/www/server/panel/pyenv/lib/python3.7/site-packages/urllib3/connectionpool.py", line 382, in _make_request
    self._validate_conn(conn)
  File "/www/server/panel/pyenv/lib/python3.7/site-packages/urllib3/connectionpool.py", line 1010, in _validate_conn
    conn.connect()
  File "/www/server/panel/pyenv/lib/python3.7/site-packages/urllib3/connection.py", line 421, in connect
    tls_in_tls=tls_in_tls,
  File "/www/server/panel/pyenv/lib/python3.7/site-packages/urllib3/util/ssl_.py", line 429, in ssl_wrap_socket
    sock, context, tls_in_tls, server_hostname=server_hostname
  File "/www/server/panel/pyenv/lib/python3.7/site-packages/urllib3/util/ssl_.py", line 472, in _ssl_wrap_socket_impl
    return ssl_context.wrap_socket(sock, server_hostname=server_hostname)
  File "/www/server/panel/pyenv/lib/python3.7/ssl.py", line 423, in wrap_socket
    session=session
  File "/www/server/panel/pyenv/lib/python3.7/ssl.py", line 870, in _create
    self.do_handshake()
  File "/www/server/panel/pyenv/lib/python3.7/ssl.py", line 1139, in do_handshake
    self._sslobj.do_handshake()
socket.timeout: _ssl.c:1074: The handshake operation timed out

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/www/server/panel/pyenv/lib/python3.7/site-packages/requests/adapters.py", line 449, in send
    timeout=timeout
  File "/www/server/panel/pyenv/lib/python3.7/site-packages/urllib3/connectionpool.py", line 756, in urlopen
    method, url, error=e, _pool=self, _stacktrace=sys.exc_info()[2]
  File "/www/server/panel/pyenv/lib/python3.7/site-packages/urllib3/util/retry.py", line 531, in increment
    raise six.reraise(type(error), error, _stacktrace)
  File "/www/server/panel/pyenv/lib/python3.7/site-packages/urllib3/packages/six.py", line 735, in reraise
    raise value
  File "/www/server/panel/pyenv/lib/python3.7/site-packages/urllib3/connectionpool.py", line 706, in urlopen
    chunked=chunked,
  File "/www/server/panel/pyenv/lib/python3.7/site-packages/urllib3/connectionpool.py", line 385, in _make_request
    self._raise_timeout(err=e, url=url, timeout_value=conn.timeout)
  File "/www/server/panel/pyenv/lib/python3.7/site-packages/urllib3/connectionpool.py", line 337, in _raise_timeout
    self, url, "Read timed out. (read timeout=%s)" % timeout_value
urllib3.exceptions.ReadTimeoutError: HTTPSConnectionPool(host='www.bt.cn', port=443): Read timed out. (read timeout=60)

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "class/http_requests.py", line 104, in post
    result = requests.post(url,data,timeout=timeout,headers=headers,verify=verify)
  File "/www/server/panel/pyenv/lib/python3.7/site-packages/requests/api.py", line 119, in post
    return request('post', url, data=data, json=json, **kwargs)
  File "/www/server/panel/pyenv/lib/python3.7/site-packages/requests/api.py", line 61, in request
    return session.request(method=method, url=url, **kwargs)
  File "/www/server/panel/pyenv/lib/python3.7/site-packages/requests/sessions.py", line 542, in request
    resp = self.send(prep, **send_kwargs)
  File "/www/server/panel/pyenv/lib/python3.7/site-packages/requests/sessions.py", line 655, in send
    r = adapter.send(request, **kwargs)
  File "/www/server/panel/pyenv/lib/python3.7/site-packages/requests/adapters.py", line 529, in send
    raise ReadTimeout(e, request=request)
requests.exceptions.ReadTimeout: HTTPSConnectionPool(host='www.bt.cn', port=443): Read timed out. (read timeout=60)

[2022-12-13 00:07:16][DEBUG] - 开始更新SSH登录日志...
[2022-12-13 00:07:16][DEBUG] - 更新ssh日志成功
[2022-12-14 00:07:38][DEBUG] - 开始更新SSH登录日志...
[2022-12-14 00:07:38][DEBUG] - 更新ssh日志成功
[2022-12-14 17:20:30][DEBUG] - mail
[2022-12-14 17:20:33][DEBUG] - 更新成功.
[2022-12-14 17:20:33][DEBUG] - 更新成功.
[2022-12-14 17:20:33][DEBUG] - 缓存更新成功,耗时: 1.67 秒
[2022-12-14 17:20:33][DEBUG] - 开始更新消息json...
[2022-12-14 17:20:33][DEBUG] - 缓存更新成功,耗时: 1.66 秒
[2022-12-14 17:20:33][DEBUG] - 开始更新消息json...
[2022-12-14 17:20:33][DEBUG] - 更新消息json成功
[2022-12-14 17:20:33][DEBUG] - 更新消息json成功
[2022-12-15 00:08:01][DEBUG] - 开始更新SSH登录日志...
[2022-12-15 00:08:01][DEBUG] - 更新ssh日志成功
[2022-12-16 00:08:24][DEBUG] - 开始更新SSH登录日志...
[2022-12-16 00:08:24][DEBUG] - 更新ssh日志成功
[2022-12-16 16:23:26][DEBUG] - mail
[2022-12-16 16:23:31][DEBUG] - 更新成功.
[2022-12-16 16:23:31][DEBUG] - 缓存更新成功,耗时: 0.85 秒
[2022-12-16 16:23:31][DEBUG] - 开始更新消息json...
[2022-12-16 16:23:31][DEBUG] - 更新消息json成功
[2022-12-17 00:08:47][DEBUG] - 开始更新SSH登录日志...
[2022-12-17 00:08:47][DEBUG] - 更新ssh日志成功
[2022-12-18 00:09:09][DEBUG] - 开始更新SSH登录日志...
[2022-12-18 00:09:09][DEBUG] - 更新ssh日志成功
[2022-12-19 00:09:32][DEBUG] - 开始更新SSH登录日志...
[2022-12-19 00:09:32][DEBUG] - 更新ssh日志成功
[2022-12-19 12:38:24][DEBUG] - mail
[2022-12-19 12:38:28][DEBUG] - 更新成功.
[2022-12-19 12:38:28][DEBUG] - 缓存更新成功,耗时: 1.69 秒
[2022-12-19 12:38:28][DEBUG] - 开始更新消息json...
[2022-12-19 12:38:28][DEBUG] - 更新消息json成功
[2022-12-19 12:38:29][DEBUG] - 更新成功.
[2022-12-19 12:38:29][DEBUG] - 缓存更新成功,耗时: 1.60 秒
[2022-12-19 12:38:29][DEBUG] - 开始更新消息json...
[2022-12-19 12:38:29][DEBUG] - 更新消息json成功
[2022-12-20 00:09:55][DEBUG] - 开始更新SSH登录日志...
[2022-12-20 00:09:55][DEBUG] - 更新ssh日志成功
[2022-12-21 00:00:18][DEBUG] - 开始更新SSH登录日志...
[2022-12-21 00:00:18][DEBUG] - 更新ssh日志成功

求教是遇到什么bug了么……
使用道具 举报 只看该作者 回复
发表于 2022-12-21 18:13:23 | 显示全部楼层
您好,尝试下使用ssh工具登录服务器或者使用服务器提供商的vnc ,执行命令修复面板
  1. bt 16
复制代码


更新完成后执行命令取消ip验证
  1. bt 11
复制代码

然后浏览器使用无痕模式访问是否可以?
使用道具 举报 回复 支持 反对
发表于 2022-12-21 18:29:48 | 显示全部楼层
执行 bt 16 重装7.9.7,再执行bt 11后,可以正常登录了,但是这个11提示“关闭此功能有被[重放攻击]的风险”,重开之后,就复现问题了,应该是它的问题,现在只有临时关闭才能正常登录
使用道具 举报 回复 支持 反对
发表于 2022-12-21 22:44:50 | 显示全部楼层
运维风光 发表于 2022-12-21 18:13
您好,尝试下使用ssh工具登录服务器或者使用服务器提供商的vnc ,执行命令修复面板

*期会有计划修复这个问题吗?
使用道具 举报 回复 支持 反对
发表于 2022-12-21 23:00:50 | 显示全部楼层
Mojelly 发表于 2022-12-21 22:44
*期会有计划修复这个问题吗?

这边后续会安排修复
使用道具 举报 回复 支持 反对
您需要登录后才可以回帖 登录 | 立即注册

本版积分规则

企业版年付运维跟进群

普通问题处理

论坛响应时间:72小时

问题处理方式:排队(仅解答)

工作时间:白班:9:00 - 18:00

紧急问题处理

论坛响应时间:10分钟

问题处理方式:1对1处理(优先)

工作时间:白班:9:00 - 18:00

工作时间:晚班:18:00 - 24:00

立即付费处理
快速回复 返回顶部 返回列表