We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Describe the bug I have flashed my node's sd card as pointed in documentation by using this mystberry.zip image.
OS started and myst was running there but webui was not accessible.
After running a standard install script, everything is fixed and node is up and running.
To Reproduce Steps to reproduce the behavior:
Additional context
2020-04-16T21:53:15.198 ERR source/tequilapi/client/http_client.go:107 > error="Get http://127.0.0.1:4050/proposals?lowerGBPriceBound=0&lowerTimePriceBound=0&upperGBPriceBound=7000000&upperTimePriceBound=50000: dial tcp 0.0.0.0:0->127.0.0.1:4050: connect: connection refused" [WARNING] Get http://127.0.0.1:4050/proposals?lowerGBPriceBound=0&lowerTimePriceBound=0&upperGBPriceBound=7000000&upperTimePriceBound=50000: dial tcp 0.0.0.0:0->127.0.0.1:4050: connect: connection refused Mysterium Node Version: 0.22.5 Build info: Branch: 0.22.5. Build id: 126951870. Commit: 23c656f7
The text was updated successfully, but these errors were encountered:
@etherunit could you recheck if you can reproduce this issue?
Sorry, something went wrong.
@chompomonim will check
@etherunit Any news?
Hey, I have tried to install it few times already, did not notice any issues during installation or startup.
etherunit
No branches or pull requests
Describe the bug
I have flashed my node's sd card as pointed in documentation by using this mystberry.zip image.
OS started and myst was running there but webui was not accessible.
After running a standard install script, everything is fixed and node is up and running.
To Reproduce
Steps to reproduce the behavior:
Additional context
The text was updated successfully, but these errors were encountered: