-
Notifications
You must be signed in to change notification settings - Fork 19
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
site issue #79
Comments
|
ye the bot was working fine but then it just stopped. when switched over to safebooru it works but when i switch back to rule34 it gives me the error |
I can't reproduce that error, I think it's some network error between your computer and rule34 (Firewall blocking it? Network blocking connections to nsfw sites? Rule34 IP banning you? I'm not sure) |
the issue is caused by replit, they blocked nsfw websites, and to fetch nsfw content it needs some kind of proxy to bypass that (tried with rule34 api without the npm module using proxy and it worked) |
Ah, that would make sense The only way for booru to get around that would be by exposing http config settings for a proxy, but unless there's an actual need outside of replit I likely won't |
the bot was working fine but recently its been showing me this error, the error gets fixed when switched to other sites
heres my code:
const Booru = require('booru');
module.exports = {
name: 'rule34',
return console.log(posts[0].fileUrl)
The text was updated successfully, but these errors were encountered: