[GH-ISSUE #4] 开启账户名称保护之后,检查完毕账号不可再登陆。 #4

Open
opened 2026-03-04 23:18:35 +03:00 by kerem · 26 comments
Owner

Originally created by @ghost on GitHub (Jul 3, 2022).
Original GitHub issue: https://github.com/luolongfei/netflix/issues/4

[2022-07-03 12:49:22.152] DEBUG    | 8:__main__:_login:434 - 已成功登录。当前地址为:https://www.netflix.com/browse
[2022-07-03 12:49:22.153] DEBUG    | 8:__main__:__handle_account_lock:1386 - 开始处理账户被锁 PIN 的问题
[2022-07-03 12:49:24.735] DEBUG    | 8:__main__:__handle_account_lock:1423 - 第 1 个账户是正常的,无需解锁
[2022-07-03 12:49:25.787] DEBUG    | 8:__main__:__handle_account_lock:1423 - 第 2 个账户是正常的,无需解锁
[2022-07-03 12:49:26.960] DEBUG    | 8:__main__:__handle_account_lock:1423 - 第 3 个账户是正常的,无需解锁
[2022-07-03 12:49:28.009] DEBUG    | 8:__main__:__handle_account_lock:1423 - 第 4 个账户是正常的,无需解锁
[2022-07-03 12:49:29.068] DEBUG    | 8:__main__:__handle_account_lock:1423 - 第 5 个账户是正常的,无需解锁
[2022-07-03 12:49:29.069] DEBUG    | 8:__main__:__handle_account_lock:1430 - 账户被锁 PIN 问题处理结束
[2022-07-03 12:49:29.070] DEBUG    | 8:__main__:__handle_account_name:1289 - 开始处理用户名被篡改的问题
[2022-07-03 12:49:30.811] DEBUG    | 8:__main__:__handle_account_name:1323 - 用户名处理结束
[2022-07-03 12:49:30.812] DEBUG    | 8:__main__:_logout:1257 - 尝试登出 [账户:xx@xx.xx]
[2022-07-03 12:49:32.463] DEBUG    | 8:__main__:_logout:1264 - 登出成功 [账户:xx@xx.xx]
[2022-07-03 12:53:25.168] DEBUG    | 8:__main__:_login:405 - 尝试登录账户:xx@xx.xx
[2022-07-03 12:53:30.803] WARNING  | 8:__main__:has_unknown_error_alert:590 - 页面出现未知错误:We are having technical difficulties and are actively working on a fix. Please try again in a few minutes.
[2022-07-03 12:53:30.804] DEBUG    | 8:__main__:protect_account:1450 - 账户 xx@xx.xx可能正处于风控期间,无法登录,本次操作将被忽略
[2022-07-03 12:53:30.804] DEBUG    | 8:__main__:run:1551 - 开始下一轮监听

清理cookie之后手动登录也失败

We are having technical difficulties and are actively working on a fix. Please try again in a few minutes.

Originally created by @ghost on GitHub (Jul 3, 2022). Original GitHub issue: https://github.com/luolongfei/netflix/issues/4 ```[2022-07-03 12:49:13.797] DEBUG | 8:__main__:_login:405 - 尝试登录账户:xx@xx.xx [2022-07-03 12:49:22.152] DEBUG | 8:__main__:_login:434 - 已成功登录。当前地址为:https://www.netflix.com/browse [2022-07-03 12:49:22.153] DEBUG | 8:__main__:__handle_account_lock:1386 - 开始处理账户被锁 PIN 的问题 [2022-07-03 12:49:24.735] DEBUG | 8:__main__:__handle_account_lock:1423 - 第 1 个账户是正常的,无需解锁 [2022-07-03 12:49:25.787] DEBUG | 8:__main__:__handle_account_lock:1423 - 第 2 个账户是正常的,无需解锁 [2022-07-03 12:49:26.960] DEBUG | 8:__main__:__handle_account_lock:1423 - 第 3 个账户是正常的,无需解锁 [2022-07-03 12:49:28.009] DEBUG | 8:__main__:__handle_account_lock:1423 - 第 4 个账户是正常的,无需解锁 [2022-07-03 12:49:29.068] DEBUG | 8:__main__:__handle_account_lock:1423 - 第 5 个账户是正常的,无需解锁 [2022-07-03 12:49:29.069] DEBUG | 8:__main__:__handle_account_lock:1430 - 账户被锁 PIN 问题处理结束 [2022-07-03 12:49:29.070] DEBUG | 8:__main__:__handle_account_name:1289 - 开始处理用户名被篡改的问题 [2022-07-03 12:49:30.811] DEBUG | 8:__main__:__handle_account_name:1323 - 用户名处理结束 [2022-07-03 12:49:30.812] DEBUG | 8:__main__:_logout:1257 - 尝试登出 [账户:xx@xx.xx] [2022-07-03 12:49:32.463] DEBUG | 8:__main__:_logout:1264 - 登出成功 [账户:xx@xx.xx] [2022-07-03 12:53:25.168] DEBUG | 8:__main__:_login:405 - 尝试登录账户:xx@xx.xx [2022-07-03 12:53:30.803] WARNING | 8:__main__:has_unknown_error_alert:590 - 页面出现未知错误:We are having technical difficulties and are actively working on a fix. Please try again in a few minutes. [2022-07-03 12:53:30.804] DEBUG | 8:__main__:protect_account:1450 - 账户 xx@xx.xx可能正处于风控期间,无法登录,本次操作将被忽略 [2022-07-03 12:53:30.804] DEBUG | 8:__main__:run:1551 - 开始下一轮监听 ``` --- 清理cookie之后手动登录也失败 `We are having technical difficulties and are actively working on a fix. Please try again in a few minutes.`
Author
Owner

@luolongfei commented on GitHub (Jul 3, 2022):

这个是 netflix 的风控。如果没有很严重的被改名和锁 pin 情况不建议开启相关功能,这两个功能会频繁登录,更容易触发风控。

<!-- gh-comment-id:1173041361 --> @luolongfei commented on GitHub (Jul 3, 2022): 这个是 netflix 的风控。如果没有很严重的被改名和锁 pin 情况不建议开启相关功能,这两个功能会频繁登录,更容易触发风控。
Author
Owner

@luolongfei commented on GitHub (Jul 3, 2022):

其实也可以做到不频繁登录,不过我暂时没时间写。当时这样处理一是为了防止程序占用一个观看名额,二是为了节省服务器资源。

<!-- gh-comment-id:1173084525 --> @luolongfei commented on GitHub (Jul 3, 2022): 其实也可以做到不频繁登录,不过我暂时没时间写。当时这样处理一是为了防止程序占用一个观看名额,二是为了节省服务器资源。
Author
Owner

@ghost commented on GitHub (Jul 3, 2022):

请问触发风控之后我该如何做才能取消风控呢?


单纯是在chrome中登录并不观看影片也会占用名额吗?


非常感谢

<!-- gh-comment-id:1173108620 --> @ghost commented on GitHub (Jul 3, 2022): 请问触发风控之后我该如何做才能取消风控呢? --- 单纯是在chrome中登录并不观看影片也会占用名额吗? --- 非常感谢
Author
Owner

@luolongfei commented on GitHub (Jul 3, 2022):

风控会自动消除,可以尝试换 ip 和浏览器尝试。
我以为是,具体不太清楚。

<!-- gh-comment-id:1173109600 --> @luolongfei commented on GitHub (Jul 3, 2022): 风控会自动消除,可以尝试换 ip 和浏览器尝试。 我以为是,具体不太清楚。
Author
Owner

@ghost commented on GitHub (Jul 4, 2022):

经过一晚上账号已经可以正常登陆了,请问一下这个报错是什么原因呢,不是规定的异常类型,用的服务器是 Linode,25 587 端口未被占用。发送到 gmail 与 qq 都失败。发件的邮箱已开启 POP 与 SMTP。谢谢


[2022-07-03 09:02:17.733] ERROR | 8:__main__:send_mail:1171 - 邮件送信失败:[Errno 99] Cannot assign requested address

<!-- gh-comment-id:1173295874 --> @ghost commented on GitHub (Jul 4, 2022): 经过一晚上账号已经可以正常登陆了,请问一下这个报错是什么原因呢,不是规定的异常类型,用的服务器是 Linode,25 587 端口未被占用。发送到 gmail 与 qq 都失败。发件的邮箱已开启 POP 与 SMTP。谢谢 --- `[2022-07-03 09:02:17.733] ERROR | 8:__main__:send_mail:1171 - 邮件送信失败:[Errno 99] Cannot assign requested address`
Author
Owner

@luolongfei commented on GitHub (Jul 4, 2022):

Linode 默认是封了邮件相关端口的,需要开工单让客服给你开通。

<!-- gh-comment-id:1173389463 --> @luolongfei commented on GitHub (Jul 4, 2022): Linode 默认是封了邮件相关端口的,需要开工单让客服给你开通。
Author
Owner

@ghost commented on GitHub (Jul 4, 2022):

请问有没有推荐的可以正常发件的服务器商呢。

<!-- gh-comment-id:1173397650 --> @ghost commented on GitHub (Jul 4, 2022): 请问有没有推荐的可以正常发件的服务器商呢。
Author
Owner

@luolongfei commented on GitHub (Jul 4, 2022):

搬瓦工的可以:
https://bwh81.net/aff.php?aff=24499&pid=57

<!-- gh-comment-id:1173420716 --> @luolongfei commented on GitHub (Jul 4, 2022): 搬瓦工的可以: https://bwh81.net/aff.php?aff=24499&pid=57
Author
Owner

@ghost commented on GitHub (Jul 4, 2022):

瓦工好贵呀 哈哈哈

<!-- gh-comment-id:1173439426 --> @ghost commented on GitHub (Jul 4, 2022): 瓦工好贵呀 哈哈哈
Author
Owner

@luolongfei commented on GitHub (Jul 4, 2022):

那你可以买 pr 的,它们家的目前 10 刀一年:
https://pacificrack.com/portal/aff.php?aff=1150&pid=108&billingcycle=annually&promocode=JR049TTGG2

<!-- gh-comment-id:1173443836 --> @luolongfei commented on GitHub (Jul 4, 2022): 那你可以买 pr 的,它们家的目前 10 刀一年: https://pacificrack.com/portal/aff.php?aff=1150&pid=108&billingcycle=annually&promocode=JR049TTGG2
Author
Owner

@luolongfei commented on GitHub (Jul 4, 2022):

可以两年付或者三年付,它们家续费可能会贵一点,基本可以用两三年换了就是了

<!-- gh-comment-id:1173444944 --> @luolongfei commented on GitHub (Jul 4, 2022): 可以两年付或者三年付,它们家续费可能会贵一点,基本可以用两三年换了就是了
Author
Owner

@ghost commented on GitHub (Jul 4, 2022):

我有几个RN,一会儿试试去。PR听他们说太灵车了。

<!-- gh-comment-id:1173446522 --> @ghost commented on GitHub (Jul 4, 2022): 我有几个RN,一会儿试试去。PR听他们说太灵车了。
Author
Owner

@luolongfei commented on GitHub (Jul 4, 2022):

pr 的话两年抛或者三年抛还是很香的,用了优惠码后配置各方面还不错,主要是它们去年开始涨价了,不然总体来说还是挺稳定的。

<!-- gh-comment-id:1173448559 --> @luolongfei commented on GitHub (Jul 4, 2022): pr 的话两年抛或者三年抛还是很香的,用了优惠码后配置各方面还不错,主要是它们去年开始涨价了,不然总体来说还是挺稳定的。
Author
Owner

@ghost commented on GitHub (Jul 4, 2022):

image

2C2G 一年25也不便宜了哇 他家性能咋样呢

<!-- gh-comment-id:1173453585 --> @ghost commented on GitHub (Jul 4, 2022): ![image](https://user-images.githubusercontent.com/76741724/177104051-4697ec80-dfda-4b48-81ca-bfa6c30488f4.png) --- 2C2G 一年25也不便宜了哇 他家性能咋样呢
Author
Owner

@luolongfei commented on GitHub (Jul 4, 2022):

这个可能是涨价后的了,之前这个活动是可以做到更便宜的。这个配置还是可以,2C2G,性能的话带本项目是完全没问题的。

<!-- gh-comment-id:1173456337 --> @luolongfei commented on GitHub (Jul 4, 2022): 这个可能是涨价后的了,之前这个活动是可以做到更便宜的。这个配置还是可以,2C2G,性能的话带本项目是完全没问题的。
Author
Owner

@luolongfei commented on GitHub (Jul 4, 2022):

怎么说也比搬瓦工的便宜,当然最便宜的 RN 限制也是最多的,不允许长时间占用资源。

<!-- gh-comment-id:1173457362 --> @luolongfei commented on GitHub (Jul 4, 2022): 怎么说也比搬瓦工的便宜,当然最便宜的 RN 限制也是最多的,不允许长时间占用资源。
Author
Owner

@luolongfei commented on GitHub (Jul 4, 2022):

如果主要是用来上网的话,搬瓦工的线路应该是最强的,如果是单纯部署项目的话,那可以考虑

<!-- gh-comment-id:1173458409 --> @luolongfei commented on GitHub (Jul 4, 2022): 如果主要是用来上网的话,搬瓦工的线路应该是最强的,如果是单纯部署项目的话,那可以考虑
Author
Owner

@ghost commented on GitHub (Jul 4, 2022):

好的 非常感谢大佬 还想请问一下那个检测时间间隔在哪里改呢 我将

            # 保护账户免受篡改与锁定
            if int(os.getenv('ENABLE_ACCOUNT_PROTECTION', 0)):
                now = time.time()
                if now - last_protection_time >= 124:
                    last_protection_time = now
                    self.protect_account()

            logger.debug('开始下一轮监听')

修改为

            # 保护账户免受篡改与锁定
            if int(os.getenv('ENABLE_ACCOUNT_PROTECTION', 0)):
                now = time.time()
                if now - last_protection_time >= 1800:
                    last_protection_time = now
                    self.protect_account()

            logger.debug('开始下一轮监听')

并不生效。是需要进入docker内部修改文件吗。

<!-- gh-comment-id:1173459340 --> @ghost commented on GitHub (Jul 4, 2022): 好的 非常感谢大佬 还想请问一下那个检测时间间隔在哪里改呢 我将 ``` # 保护账户免受篡改与锁定 if int(os.getenv('ENABLE_ACCOUNT_PROTECTION', 0)): now = time.time() if now - last_protection_time >= 124: last_protection_time = now self.protect_account() logger.debug('开始下一轮监听') ``` 修改为 ``` # 保护账户免受篡改与锁定 if int(os.getenv('ENABLE_ACCOUNT_PROTECTION', 0)): now = time.time() if now - last_protection_time >= 1800: last_protection_time = now self.protect_account() logger.debug('开始下一轮监听') ``` 并不生效。是需要进入docker内部修改文件吗。
Author
Owner

@luolongfei commented on GitHub (Jul 4, 2022):

修改了要重新 build 容器,因为代码已经构建到容器里面了,你修改的外部代码,容器内不生效的。

<!-- gh-comment-id:1173461174 --> @luolongfei commented on GitHub (Jul 4, 2022): 修改了要重新 build 容器,因为代码已经构建到容器里面了,你修改的外部代码,容器内不生效的。
Author
Owner

@ghost commented on GitHub (Jul 4, 2022):

好的我尝试一下

<!-- gh-comment-id:1173463670 --> @ghost commented on GitHub (Jul 4, 2022): 好的我尝试一下
Author
Owner

@ghost commented on GitHub (Jul 4, 2022):

image
买了个这个 测试了一下可以发件
https://greencloudvps.com/billing/store/budget-kvm-sale/4th-of-july-special

<!-- gh-comment-id:1173486885 --> @ghost commented on GitHub (Jul 4, 2022): ![image](https://user-images.githubusercontent.com/76741724/177110050-1c4d3f5d-4fbf-4550-b5b7-9c678f166bfe.png) 买了个这个 测试了一下可以发件 `https://greencloudvps.com/billing/store/budget-kvm-sale/4th-of-july-special`
Author
Owner

@luolongfei commented on GitHub (Jul 4, 2022):

没听说过这个厂商

<!-- gh-comment-id:1173492912 --> @luolongfei commented on GitHub (Jul 4, 2022): 没听说过这个厂商
Author
Owner

@ghost commented on GitHub (Jul 4, 2022):

还是不错的,在线率和流媒体情况都很好

image
image

<!-- gh-comment-id:1173496048 --> @ghost commented on GitHub (Jul 4, 2022): 还是不错的,在线率和流媒体情况都很好 ![image](https://user-images.githubusercontent.com/76741724/177111541-f658a0b9-4651-4698-8b1f-20e1c6ee8abe.png) ![image](https://user-images.githubusercontent.com/76741724/177111570-820dff41-69f9-46a4-b154-330d9316648b.png)
Author
Owner

@luolongfei commented on GitHub (Jul 4, 2022):

多少钱一年

<!-- gh-comment-id:1173497178 --> @luolongfei commented on GitHub (Jul 4, 2022): 多少钱一年
Author
Owner

@ghost commented on GitHub (Jul 4, 2022):

image


2年 $47 4C8G 7T/Month

<!-- gh-comment-id:1173503668 --> @ghost commented on GitHub (Jul 4, 2022): ![image](https://user-images.githubusercontent.com/76741724/177112779-d126d9fb-f3aa-4aaa-ab8f-1e00837f3e51.png) --- 2年 $47 4C8G 7T/Month
Author
Owner

@luolongfei commented on GitHub (Jul 4, 2022):

性价比挺高

<!-- gh-comment-id:1173657279 --> @luolongfei commented on GitHub (Jul 4, 2022): 性价比挺高
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/netflix#4
No description provided.