Any issues for web3 on digital ocean?

by Sundeep Kumar   Last Updated June 30, 2020 02:28 AM - source

My dapp which is currently testing on ropsten works perfectly when i run the frontend from local but dosent return addresses when i run on a digital ocean server. it is successfully connected to ropsten which i determined using a console log but it dosent return any of the addresses so im guessing there is some issue with metamask or web3 with digital ocean. Has anyone else come across the same?



Answers 1


You account are only persisted in your local state and probably do not exist on Ropsten yet. If you have the account connected to metamask you can check

Samuel Dare
Samuel Dare
December 23, 2019 13:05 PM

Related Questions



web3 metamask, synchronous or asynchronous

Updated June 26, 2018 11:28 AM


How to replace Metamask Pop-Up with my own UI

Updated July 12, 2019 19:28 PM