-
Notifications
You must be signed in to change notification settings - Fork 48
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
一直提示连接失败 #1
Comments
我这边弄了一个新环境测试了一下,也能正常使用,你重新更新下key试下 |
pyfofa 3.6以上的都能用,亲测有效 |
好的大佬,太敬业了!我把我这个程序写完我看下,感谢大佬的回复!
…------------------ 原始邮件 ------------------
发件人: "Miagz/XrayFofa" <[email protected]>;
发送时间: 2020年10月8日(星期四) 晚上7:30
收件人: "Miagz/XrayFofa"<[email protected]>;
抄送: "不挽留不强求"<[email protected]>;"Author"<[email protected]>;
主题: Re: [Miagz/XrayFofa] 一直提示连接失败 (#1)
我这里使用的python环境时3.8环境
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
我知道哪里出问题了😂😂😂,我先看下能不能解决哈 |
大佬加油!
…------------------ 原始邮件 ------------------
发件人: "Miagz/XrayFofa" <[email protected]>;
发送时间: 2020年10月8日(星期四) 晚上7:37
收件人: "Miagz/XrayFofa"<[email protected]>;
抄送: "不挽留不强求"<[email protected]>;"Author"<[email protected]>;
主题: Re: [Miagz/XrayFofa] 一直提示连接失败 (#1)
我知道哪里出问题了😂😂😂,我先看下能不能解决哈
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
没关系的大佬,我换个py环节就是了
…------------------ 原始邮件 ------------------
发件人: "Miagz/XrayFofa" <[email protected]>;
发送时间: 2020年10月8日(星期四) 晚上9:49
收件人: "Miagz/XrayFofa"<[email protected]>;
抄送: "不挽留不强求"<[email protected]>;"Author"<[email protected]>;
主题: Re: [Miagz/XrayFofa] 一直提示连接失败 (#1)
抱歉我无能为力😰😰
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
我看看能不能解决吧 |
注册用户报这个错误,未授权 |
|
能让我看看https://fofa.so/api/v1/search/[email protected]&key=XXXXXXXXXXXXXXXXXXX&qbase64=IkRJUi04NTBMIg==%E5%9C%A8%E8%BF%99%E9%87%8C%E6%8F%92%E5%85%A5%E4%BB%A3%E7%A0%81%E7%89%87 这种的返回结果吗,输入你的邮箱和你的key |
同样的认证,其他的工具就没有问题
The text was updated successfully, but these errors were encountered: