You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When attempting to start and test firefly on windows a few errors appear. The first error was "Error: dial tcp 127.0.0.1:5100: connectex: No connection could be made because the target machine actively refused it." After doing a bit of digging the error seems to come about when attempting to start the Firefly stack. After the stack is started a new error is present. This error is "Fatal: Failed to start mining: etherbase missing: etherbase must be explicitly specified".
What did you expect to happen?
The expected result is to determine if the removal of reset corrects the namespace issue as mentioned in #1615 and #1650
How can we reproduce it (as minimally and precisely as possible)?
Open a terminal and docker desktop. Start the application and view logs as shown in docker desktop.
Anything else we need to know?
No response
OS version
# On Linux:
$ cat /etc/os-release
# paste output here
$ uname -a
# paste output here
# On Windows:C:\> wmic os get Caption, Version, BuildNumber, OSArchitecture
# paste output here
The text was updated successfully, but these errors were encountered:
I think this issue should be raised against the FireFly-CLI as it's about setting up Geth correctly see related issue from geth ethereum/go-ethereum#26860
What happened?
When attempting to start and test firefly on windows a few errors appear. The first error was "Error: dial tcp 127.0.0.1:5100: connectex: No connection could be made because the target machine actively refused it." After doing a bit of digging the error seems to come about when attempting to start the Firefly stack. After the stack is started a new error is present. This error is "Fatal: Failed to start mining: etherbase missing: etherbase must be explicitly specified".
What did you expect to happen?
The expected result is to determine if the removal of reset corrects the namespace issue as mentioned in #1615 and #1650
How can we reproduce it (as minimally and precisely as possible)?
Open a terminal and docker desktop. Start the application and view logs as shown in docker desktop.
Anything else we need to know?
No response
OS version
The text was updated successfully, but these errors were encountered: