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
My node is running with these settings and is bootstrapped - so I assume it is connected to the mainnet:
avalanchego --http-host=0.0.0.0 --http-tls-enabled=true --http-tls-cert-file=/etc/nginx/certs/server.crt --http-tls-key-file=/etc/nginx/certs/server.key --plugin-dir=/usr/local/app/plugins
However - when I use this endpoint from the wallet - it gives me warnings that I am not connected to the mainnet
...and at the bottom of the screen it shows a red bar and reads:
Which I believe is wrong..
Am I doing something wrong here - or is this a UI bug ?
The text was updated successfully, but these errors were encountered:
Seems to be solved in the current master branch... Might be an idea to create tags for the wallet as well :)
Sorry, something went wrong.
Merge pull request ava-labs#75 from ava-labs/dev
9953887
fix mint out id bug on keyRow
No branches or pull requests
My node is running with these settings and is bootstrapped - so I assume it is connected to the mainnet:
avalanchego --http-host=0.0.0.0 --http-tls-enabled=true --http-tls-cert-file=/etc/nginx/certs/server.crt --http-tls-key-file=/etc/nginx/certs/server.key --plugin-dir=/usr/local/app/plugins
However - when I use this endpoint from the wallet - it gives me warnings that I am not connected to the mainnet
...and at the bottom of the screen it shows a red bar and reads:
Which I believe is wrong..
Am I doing something wrong here - or is this a UI bug ?
The text was updated successfully, but these errors were encountered: