Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Giving 403 Forbidden from AWS #18

Closed
piyush2dev opened this issue Jun 26, 2019 · 4 comments
Closed

Giving 403 Forbidden from AWS #18

piyush2dev opened this issue Jun 26, 2019 · 4 comments

Comments

@piyush2dev
Copy link

No description provided.

@piyush2dev piyush2dev changed the title Giving 403 Forbidden on Lambda Giving 403 Forbidden from AWS Jun 26, 2019
@rakemen
Copy link

rakemen commented Jul 2, 2019

Same issue on Heroku. Seems like the cricbuzz cloudflare server is blocking all Heroku and AWS IPs.

@codophobia
Copy link
Owner

I have never tried to use the library from any cloud servers. Cricbuzz servers will block you if you abuse their services.

@rakemen
Copy link

rakemen commented Jul 2, 2019 •
edited
Loading

I have never tried to use the library from any cloud servers. Cricbuzz servers will block you if you abuse their services.

@codophobia I have never used heroku for deploying a bot that pulls data from Cricbuzz ever, seems like they don't want any scripts pulling data from them from any cloud servers. (AWS, Heroku). Could there be any other way to deploy this apart from just running on the local machine?

@codophobia
Copy link
Owner

#19

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@rakemen @codophobia @piyush2dev