Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Esplora is currently unavailable, please try again later
See original GitHub issueI have spun up a new docker instance of blockstream/esplora and I get the above message when I try to access the frontend. Using the browser’s (chrome) developers console in the network tab I could see that a request to <my-ip>:8080/api/blocks/ failed with 502 Bad Gateway.
I ran the docker container like described on the github page under “How to run the explorer for Bitcoin mainnet”. According to the logs, the docker container has finished synchronizing the blockchain blocks (up to the current time) within a few hours. I have also already re-created the container, but no luck.
What is the source of my problem?
Issue Analytics
- State:
- Created 4 years ago
- Comments:6
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Thanks for the suggestion @cloakedch! Added in https://github.com/Blockstream/esplora/commit/57b267b9f645fae7abe99bec5fe85e8b54a1d1c1.
Suggestion:
If you follow the readme and build the docker container inside the cloned repository (
docker build -t esplora), you should adddata_bitcoin_mainnetto the .dockerignore file, so that when doing agit pulland re-build later, it will not push the whole data folder into the docker context.