-
Notifications
You must be signed in to change notification settings - Fork 395
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
Explorer says "We encountered an error. Please try again later." #28
Comments
@metacoin thank you for the report The first step you quote from the README indeed implies that you are already running on localhost an instance of blockstream/electrs (a modified version of the original electrs) and you can use the blockstream.info live instance if you just want to test out/setup your local config (as per shell comment). As per the docker run, it will take several hours if not days depending on how powerful is the machine to synchronize. We should improve the README and clarify the above points as well as improve the explorer to inform the status of the synchronization directly from the explorer on a web page and end point. |
How can I check on the synchronization status via command-line or viewing logs? bitocind is fully synced, and checking |
@metacoin see #26 (comment) (you can either read them directly, which may need sudo because docker sets the file as readable by root only) or you can enter the docker instance with 'exec' and tail from within. |
Thanks, I was looking for a status update on which block the explorer was up-to-date with, though looking through the logs I don't think it's possible to evaluate that at this time. My strategy was to watch Also, I am still confused about what might be running on port 3000, as both As I posted in my other comment, I fixed this problem on my end, after hunting through logs the issue was not enough HDD space on my device. |
@metacoin 3000 is only if you skip docker and run https://github.com/blockstream/electrs locally manually, we should clarify better in the readme |
closing if you encounter a problem against the latest master version please feel free to reopen or raise a new issue. thanks |
Environment:
Ubuntu 18.04.1 LTS
Steps to reproduce:
Followed README...
Also running from the docker command at the same time:
The line
export API_URL=http://localhost:3000/
is confusing because I'm not sure what is supposed to be running on port 3000.netstat -plunt
only shows SSH, the explorer front-end running on port 5000, and the explorer API(?) running on port 8080.Even with
export API_URL=http://localhost:8080/
I am getting the same results.What is supposed to be running on port 3000?
Attached is a screenshot of the error page, which is what I see when I navigate to port 5000,
The text was updated successfully, but these errors were encountered: