Open JustForUsing opened 1 year ago
同样遇到这个问题,好像是freenom现在登录需要验证码了
收到。看起来是增加了验证。
我也遇到这个问题了: [2023-05-31 10:24:59] 当前程序版本 v0.5.1 [2023-05-31 10:24:59] 共发现 1 个 freenom 账户 [2023-05-31 10:24:59] 开始处理第 1 个 freenom 账户:****@live.cn [1/1] [2023-05-31 10:25:00] 出错:登录 freenom 出错。错误信息:Client error: POST https://my.freenom.com/dologin.php resulted in a 405 Not Allowed
用上了 AWS WAF CAPTCHA 做验证。
插个眼,有办法解决嘛 🤔
解题思路:通过切换语音验证码,下载语音文件,交给 meta 的 ai 语音识别转文字,回填。
不过我暂时没时间弄。有兴趣的可以提前研究。
看来只能手动一段时间了 等待大佬解决
YesCaptcha 可以解决一切
@jinwyp 目前网上没看到支持 aws waf 验证码的,你说的这个也不支持:https://yescaptcha.atlassian.net/wiki/spaces/YESCAPTCHA/pages/164286
同样的问题,插个眼,期待大佬解决
解题思路:通过切换语音验证码,下载语音文件,交给 meta 的 ai 语音识别转文字,回填。
不过我暂时没时间弄。有兴趣的可以提前研究。
可以用 OpenAI's Whisper. 离线 语音生成文字 https://github.com/chidiwilliams/buzz
还得看大神来弄。
插眼 同样的问题
主人,出错了,登录 freenom 出错。错误信息:Client error: `POST https://my.freenom.com/dologin.php` resulted in a `405 Not Allowed` response:
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width (truncated...)
(Error code: 34520002)
具体是在/app/app/Console/FreeNom.php文件的第131行,抛出了一个异常。异常的内容是登录 freenom 出错。错误信息:Client error: `POST https://my.freenom.com/dologin.php` resulted in a `405 Not Allowed` response:
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width (truncated...)
(Error code: 34520002),快去看看吧。(账户:xxx@example.com)
一样的问题·,等作者更新吗?
插眼,等更新
插眼 一样的问题
插眼 同样报错
能否提供cookie 直接登录 一种选项, 跳过用账号密码登录 这样可以手动填入cookie 登录
能否提供cookie 直接登录 一种选项, 跳过用账号密码登录 这样可以手动填入cookie 登录
没有意义,ck失效很快
能否提供cookie 直接登录 一种选项, 跳过用账号密码登录 这样可以手动填入cookie 登录
我试了,cookie登录后无验证码也是有有效期的,过期后就又需要过一次aws waf 验证码。
大家应该都不行了,一样的报错,5月28日开始的
同样的问题,插个眼,期待大佬解决.感谢~
同样的问题,插个眼,期待大佬解决。感谢~
插眼
亲们,别回复插眼了 页面拉到最上边,右边把这个小铃铛点一下,就插好眼了。 这个issues有更新立马就看到了。
亲们,别回复插眼了 页面拉到最上边,右边把这个小铃铛点一下,就插好眼了。 这个issues有更新立马就看到了。
你是懂Github的√
开始出验证了
解题思路:通过切换语音验证码,下载语音文件,交给 meta 的 ai 语音识别转文字,回填。
不过我暂时没时间弄。有兴趣的可以提前研究。
语音包含了两人,男的在说背景音,女的要求写出她说的两个单词 🤔️ amzn-captcha-modal.zip
有没有可能临时推出一个“提醒续期”的功能,在域名到期前提醒手动续期。(有可能现在已经有了但是我没有看到过)
有没有可能临时推出一个“提醒续期”的功能,在域名到期前提醒手动续期。(有可能现在已经有了但是我没有看到过)
你说 有没有一种可能 Freenom官方给你发了邮件
有没有可能临时推出一个“提醒续期”的功能,在域名到期前提醒手动续期。(有可能现在已经有了但是我没有看到过)
你说 有没有一种可能 Freenom官方给你发了邮件
主要有些人没有用常用邮箱注册,又没有开转发or代收邮件。 虽然确实“用这个项目来提醒还不如折腾一下自己的邮箱提醒”
看来 freenom-renew 做的太好了以至于我都没有收到过这个邮件😂,pass
发件人: Pesy @.> 发送时间: 2023年6月10日 16:10 收件人: @.> 抄送: @.>; @.> 主题: Re: [luolongfei/freenom] freenom更新了登录接口模拟登录报405 (Issue #225)
有没有可能临时推出一个“提醒续期”的功能,在域名到期前提醒手动续期。(有可能现在已经有了但是我没有看到过)
你说 有没有一种可能 Freenom官方给你发了邮件
— Reply to this email directly, view it on GitHubhttps://github.com/luolongfei/freenom/issues/225#issuecomment-1585555345, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AHZQUO5GA23IPXA7GSSRWXLXKQTXDANCNFSM6AAAAAAYUZANJA. You are receiving this because you commented.Message ID: @.***>
坐等大佬给个解决方案~大佬YYDS
坐等大佬给个解决方案~大佬YYDS
有人成功了https://t.me/misakanoxpz/74435
没法验证真伪。
https://github.com/a-maliarov/amazoncaptcha 破解验证码机会比较高,建议整合
@pai1233 这个库我之前见过,它应该是破解那种图片验证码,非交互式的那种,所以不适用
有时候可以正常显示,有时候不行,大家一样吗?
有时候可以正常显示,有时候不行,大家一样吗?
嗯,是。 最近(这个月)偶尔会出现直接成功登录的情况。
https://github.com/luolongfei/freenom/releases/tag/v0.6.0
久等了。v0.6.0 使用我几个月前提出的语音识别方案了。各位可以试试。
[2024-01-27 23:14:36] getAwsWafToken error: cURL error 7: Failed to connect to aws-waf-solver port 2018: Connection refused (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for http://aws-waf-solver:2018/aws_waf_token
[2024-01-27 23:14:37] getAwsWafToken error: cURL error 7: Failed to connect to aws-waf-solver port 2018: Connection refused (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for http://aws-waf-solver:2018/aws_waf_token
[2024-01-27 23:14:38] getAwsWafToken error: cURL error 7: Failed to connect to aws-waf-solver port 2018: Connection refused (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for http://aws-waf-solver:2018/aws_waf_token
[2024-01-27 23:14:39] getAwsWafToken error: cURL error 7: Failed to connect to aws-waf-solver port 2018: Connection refused (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for http://aws-waf-solver:2018/aws_waf_token
[2024-01-27 23:14:40] 出错:未能获取到 AWS WAF Token(Error code: 34520018)
aws-waf-solver | INFO: 172.24.0.3:56240 - "GET /aws_waf_token/d20d8906-95af-456e-a223-c8d1f25e6cfb HTTP/1.1" 200 OK
aws-waf-solver | INFO: 172.24.0.3:56240 - "GET /aws_waf_token/d20d8906-95af-456e-a223-c8d1f25e6cfb HTTP/1.1" 200 OK
aws-waf-solver | INFO: 172.24.0.3:56240 - "GET /aws_waf_token/d20d8906-95af-456e-a223-c8d1f25e6cfb HTTP/1.1" 200 OK
aws-waf-solver | [2024-01-27 23:36:04.050] ERROR | 30:app.freenom:__recognize_voice:65 - 识别出错:Message: 查找 id 为 amzn-captcha-verify-button 的元素未果
aws-waf-solver | [2024-01-27 23:36:04.050] INFO | 30:app.freenom:start:17 - 尝试识别语音答案 [8/100]
aws-waf-solver | INFO: 172.24.0.3:56240 - "GET /aws_waf_token/d20d8906-95af-456e-a223-c8d1f25e6cfb HTTP/1.1" 200 OK
aws-waf-solver | INFO: 172.24.0.3:56240 - "GET /aws_waf_token/d20d8906-95af-456e-a223-c8d1f25e6cfb HTTP/1.1" 200 OK
aws-waf-solver | INFO: 172.24.0.3:56240 - "GET /aws_waf_token/d20d8906-95af-456e-a223-c8d1f25e6cfb HTTP/1.1" 200 OK
aws-waf-solver | INFO: 172.24.0.3:56240 - "GET /aws_waf_token/d20d8906-95af-456e-a223-c8d1f25e6cfb HTTP/1.1" 200 OK
aws-waf-solver | INFO: 172.24.0.3:56240 - "GET /aws_waf_token/d20d8906-95af-456e-a223-c8d1f25e6cfb HTTP/1.1" 200 OK
aws-waf-solver | INFO: 172.24.0.3:56240 - "GET /aws_waf_token/d20d8906-95af-456e-a223-c8d1f25e6cfb HTTP/1.1" 200 OK
aws-waf-solver | INFO: 172.24.0.3:56240 - "GET /aws_waf_token/d20d8906-95af-456e-a223-c8d1f25e6cfb HTTP/1.1" 200 OK
aws-waf-solver | INFO: 172.24.0.3:56240 - "GET /aws_waf_token/d20d8906-95af-456e-a223-c8d1f25e6cfb HTTP/1.1" 200 OK
aws-waf-solver | INFO: 172.24.0.3:56240 - "GET /aws_waf_token/d20d8906-95af-456e-a223-c8d1f25e6cfb HTTP/1.1" 200 OK
aws-waf-solver | [2024-01-27 23:36:30.187] ERROR | 30:app.freenom:__recognize_voice:65 - 识别出错:Message: 查找 id 为 amzn-captcha-verify-button 的元素未果
aws-waf-solver | [2024-01-27 23:36:30.189] INFO | 30:app.freenom:start:17 - 尝试识别语音答案 [9/100]
aws-waf-solver | INFO: 172.24.0.3:56240 - "GET /aws_waf_token/d20d8906-95af-456e-a223-c8d1f25e6cfb HTTP/1.1" 200 OK
aws-waf-solver | INFO: 172.24.0.3:56240 - "GET /aws_waf_token/d20d8906-95af-456e-a223-c8d1f25e6cfb HTTP/1.1" 200 OK
aws-waf-solver | INFO: 172.24.0.3:56240 - "GET /aws_waf_token/d20d8906-95af-456e-a223-c8d1f25e6cfb HTTP/1.1" 200 OK
aws-waf-solver | INFO: 172.24.0.3:56240 - "GET /aws_waf_token/d20d8906-95af-456e-a223-c8d1f25e6cfb HTTP/1.1" 200 OK
aws-waf-solver | INFO: 172.24.0.3:56240 - "GET /aws_waf_token/d20d8906-95af-456e-a223-c8d1f25e6cfb HTTP/1.1" 200 OK
aws-waf-solver | INFO: 172.24.0.3:56240 - "GET /aws_waf_token/d20d8906-95af-456e-a223-c8d1f25e6cfb HTTP/1.1" 200 OK
aws-waf-solver | INFO: 172.24.0.3:56240 - "GET /aws_waf_token/d20d8906-95af-456e-a223-c8d1f25e6cfb HTTP/1.1" 200 OK
aws-waf-solver | INFO: 172.24.0.3:56240 - "GET /aws_waf_token/d20d8906-95af-456e-a223-c8d1f25e6cfb HTTP/1.1" 200 OK
aws-waf-solver | [2024-01-27 23:36:56.329] ERROR | 30:app.freenom:__recognize_voice:65 - 识别出错:Message: 查找 id 为 amzn-captcha-verify-button 的元素未果
aws-waf-solver | [2024-01-27 23:36:56.329] INFO | 30:app.freenom:start:17 - 尝试识别语音答案 [10/100]
aws-waf-solver | INFO: 172.24.0.3:56240 - "GET /aws_waf_token/d20d8906-95af-456e-a223-c8d1f25e6cfb HTTP/1.1" 200 OK
aws-waf-solver | INFO: 172.24.0.3:56240 - "GET /aws_waf_token/d20d8906-95af-456e-a223-c8d1f25e6cfb HTTP/1.1" 200 OK
aws-waf-solver | INFO: 172.24.0.3:56240 - "GET /aws_waf_token/d20d8906-95af-456e-a223-c8d1f25e6cfb HTTP/1.1" 200 OK
aws-waf-solver | INFO: 172.24.0.3:56240 - "GET /aws_waf_token/d20d8906-95af-456e-a223-c8d1f25e6cfb HTTP/1.1" 200 OK
aws-waf-solver | INFO: 172.24.0.3:56240 - "GET /aws_waf_token/d20d8906-95af-456e-a223-c8d1f25e6cfb HTTP/1.1" 200 OK
aws-waf-solver | INFO: 172.24.0.3:56240 - "GET /aws_waf_token/d20d8906-95af-456e-a223-c8d1f25e6cfb HTTP/1.1" 200 OK
aws-waf-solver | INFO: 172.24.0.3:56240 - "GET /aws_waf_token/d20d8906-95af-456e-a223-c8d1f25e6cfb HTTP/1.1" 200 OK
aws-waf-solver | INFO: 172.24.0.3:56240 - "GET /aws_waf_token/d20d8906-95af-456e-a223-c8d1f25e6cfb HTTP/1.1" 200 OK
aws-waf-solver | INFO: 172.24.0.3:56240 - "GET /aws_waf_token/d20d8906-95af-456e-a223-c8d1f25e6cfb HTTP/1.1" 200 OK
aws-waf-solver | [2024-01-27 23:37:22.436] ERROR | 30:app.freenom:__recognize_voice:65 - 识别出错:Message: 查找 id 为 amzn-captcha-verify-button 的元素未果
aws-waf-solver | [2024-01-27 23:37:22.437] INFO | 30:app.freenom:start:17 - 尝试识别语音答案 [11/100]
aws-waf-solver | INFO: 172.24.0.3:56240 - "GET /aws_waf_token/d20d8906-95af-456e-a223-c8d1f25e6cfb HTTP/1.1" 200 OK
aws-waf-solver | INFO: 172.24.0.3:56240 - "GET /aws_waf_token/d20d8906-95af-456e-a223-c8d1f25e6cfb HTTP/1.1" 200 OK
aws-waf-solver | INFO: 172.24.0.3:56240 - "GET /aws_waf_token/d20d8906-95af-456e-a223-c8d1f25e6cfb HTTP/1.1" 200 OK
aws-waf-solver | INFO: 172.24.0.3:56240 - "GET /aws_waf_token/d20d8906-95af-456e-a223-c8d1f25e6cfb HTTP/1.1" 200 OK
aws-waf-solver | INFO: 172.24.0.3:56240 - "GET /aws_waf_token HTTP/1.1" 200 OK
aws-waf-solver | [2024-01-27 23:37:48.842] ERROR | 30:app.freenom:__recognize_voice:65 - 识别出错:Message: 查找 id 为 amzn-captcha-verify-button 的元素未果
aws-waf-solver | [2024-01-27 23:37:48.844] INFO | 30:app.freenom:start:17 - 尝试识别语音答案 [12/100]
aws-waf-solver | [2024-01-27 23:38:14.582] ERROR | 30:app.freenom:__recognize_voice:65 - 识别出错:Message: 查找 id 为 amzn-captcha-verify-button 的元素未果
aws-waf-solver | [2024-01-27 23:38:14.582] INFO | 30:app.freenom:start:17 - 尝试识别语音答案 [13/100]
aws-waf-solver | [2024-01-27 23:38:22.118] INFO | 30:app.freenom:__recognize_voice:39 - wit.ai: PM. Forest
aws-waf-solver | [2024-01-27 23:38:27.786] WARNING | 30:app.freenom:__recognize_voice:54 - 未跳转,答案错误:Forest
aws-waf-solver | [2024-01-27 23:38:27.790] ERROR | 30:app.freenom:__recognize_voice:65 - 识别出错:未跳转,答案错误
aws-waf-solver | [2024-01-27 23:38:27.790] INFO | 30:app.freenom:start:17 - 尝试识别语音答案 [14/100]
aws-waf-solver | [2024-01-27 23:38:35.434] INFO | 30:app.freenom:__recognize_voice:39 - wit.ai: Reader
aws-waf-solver | [2024-01-27 23:38:41.960] WARNING | 30:app.freenom:__recognize_voice:54 - 未跳转,答案错误:Reader
aws-waf-solver | [2024-01-27 23:38:41.963] ERROR | 30:app.freenom:__recognize_voice:65 - 识别出错:未跳转,答案错误
aws-waf-solver | [2024-01-27 23:38:41.963] INFO | 30:app.freenom:start:17 - 尝试识别语音答案 [15/100]
aws-waf-solver | [2024-01-27 23:39:07.987] ERROR | 30:app.freenom:__recognize_voice:65 - 识别出错:Message: 查找 id 为 amzn-captcha-verify-button 的元素未果
aws-waf-solver | [2024-01-27 23:39:07.988] INFO | 30:app.freenom:start:17 - 尝试识别语音答案 [16/100]
识别率不太行。
哪里不对,按照教程来的。
freenom | [2024-01-27 23:42:49] getAwsWafToken error: cURL error 7: Failed to connect to aws-waf-solver port 2018: Connection refused (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for http://aws-waf-solver:2018/aws_waf_token
freenom | [2024-01-27 23:42:50] getAwsWafToken error: cURL error 7: Failed to connect to aws-waf-solver port 2018: Connection refused (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for http://aws-waf-solver:2018/aws_waf_token
freenom | [2024-01-27 23:42:51] getAwsWafToken error: cURL error 7: Failed to connect to aws-waf-solver port 2018: Connection refused (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for http://aws-waf-solver:2018/aws_waf_token
freenom | [2024-01-27 23:42:52] getAwsWafToken error: cURL error 7: Failed to connect to aws-waf-solver port 2018: Connection refused (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for http://aws-waf-solver:2018/aws_waf_token
freenom | [2024-01-27 23:42:53] getAwsWafToken error: cURL error 7: Failed to connect to aws-waf-solver port 2018: Connection refused (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for http://aws-waf-solver:2018/aws_waf_token
freenom | [2024-01-27 23:42:54] getAwsWafToken error: cURL error 7: Failed to connect to aws-waf-solver port 2018: Connection refused (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for http://aws-waf-solver:2018/aws_waf_token
freenom | [2024-01-27 23:42:55] 出错:未能获取到 AWS WAF Token(Error code: 34520018)
必须用2019吗?改个端口就不行,2019 caddy占用了。
换台服务器,你 ip 太黑了
2019 可以自行改 yml 文件中的端口,比如2010:2019,那么宿主就只占用2010
描述问题
重现步骤
截图&日志
你做了哪些尝试
环境信息
额外的备注