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.

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

Ropsten API seems to produce 403 Bad Response? #110

Open
walesdata opened this issue Aug 23, 2021 · 4 comments
Open

Ropsten API seems to produce 403 Bad Response? #110

walesdata opened this issue Aug 23, 2021 · 4 comments

Comments

@walesdata
Copy link

Hello!

I would like to use your library to access the Ropsten network. I saw that the main change to switch networks was the base URL. I cloned your repo, and added a flag to the Account and Client init functions for use_ropsten=False. Then added an if in the init to change the URL if that is true. Testing this produced a 403 error.

I then put the Account class back to its original state, and replaced client.py with client.ropsten.py and tried again. Again, this produced a 403 bad response.

Have you encountered this issue before, and do you know the root cause of it? If I can get this working, I will submit the code.

Thank you!

@jj13jj
Copy link

jj13jj commented Aug 23, 2021 via email

@antliv
Copy link

antliv commented Nov 4, 2021

U robbd me

@zhagao12138
Copy link

Hello!

I would like to use your library to access the Ropsten network. I saw that the main change to switch networks was the base URL. I cloned your repo, and added a flag to the Account and Client init functions for use_ropsten=False. Then added an if in the init to change the URL if that is true. Testing this produced a 403 error.

I then put the Account class back to its original state, and replaced client.py with client.ropsten.py and tried again. Again, this produced a 403 bad response.

Have you encountered this issue before, and do you know the root cause of it? If I can get this working, I will submit the code.

Thank you!

hello

I meet the same problem error 403.


Essentially Etherscan is blocking requests that don't provide a User-agent so add a User-agent header property if using the Python requests module. ----https://stackoverflow.com/questions/52343308/how-to-run-shell-script-file-on-ipython-at-google-colab

that might help you.

Thank you!

@zhagao12138
Copy link

https://stackoverflow.com/questions/38489386/python-requests-403-forbidden/38489588#38489588

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants
@walesdata @jj13jj @zhagao12138 @antliv and others