got an issue after moving to BRS v.3.3.3 about foxy-miner HOT 11 CLOSED

Also tried to delete the foxy-miner.yaml but get the error like before but with different arguments:
Downloading scavenger: ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ | 0% | Speed: N/A(node:15332) UnhandledPromiseRejectionWarning: Error: read ECONNRESET
at TLSWrap.onStreamRead (internal/stream_base_commons.js:209:20)
(Use foxy-miner --trace-warnings ... to show where the warning was created)
(node:15332) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 4)
(node:15332) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

from foxy-miner.

It seems to fail to download the scav binary, can you make sure you can download it just fine from here? https://github.com/foxypool/foxy-miner/releases/download/0.0.0/scavenger-1.9.0-windows-x86_64-cpu-only.exe.zip

The file inside that zip is already named correctly for foxy-miner, so if the download via a browser works, but not in foxy-miner for some reason, then you can just put the exe fro mthe zip in the binary directory and it should work

from foxy-miner.

Thanks for the comment!
I've moved *.zip and *.exe file downloaded from source to /binaries folder, make a settings to foxy-miner.yaml and looks like it let me pass to the next error:
2022-02-18 02:37:35.791 [INFO] Config loaded from C:\Users.config\foxy-miner\foxy-miner.yaml successfully
2022-02-18 02:37:38.827 [ERROR] FoxyPool BHD | Connection outage detected ..
2022-02-18 02:37:38.828 [ERROR] FoxyPool SIGNA | Connection outage detected ..

Then I've reinstall Node.js and the problem have not gone.
So for now I've stucked at [ERROR] FoxyPool | Connection outage detected

from foxy-miner.

It looks like something is blocking foxy-miner from internet access, double check your firewall or similar is not blocking it

from foxy-miner.

the settings I've changed in foxy-miner.yaml:

upstreams:

• name: FoxyPool BHD
  type: foxypool
  color: '#e25898'
  coin: BHD
  distributionRatio: 0-100
  payoutAddress: "MY-BHD-PAYOUT ADDRESS"
  accountName: "some"
  minerName: "some"
  weight: 20
  doNotInterruptAbovePercent: 50
• name: FoxyPool SIGNA
  type: foxypool
  color: '#4959ff'
  coin: 'SIGNA'
  distributionRatio: 0-100
  payoutAddress: "MY-SIGNA-PAYOUT ADDRESS"
  accountName: "some"
  minerName: "some"
  weight: 10
  doNotInterruptAbovePercent: 50

from foxy-miner.

I've checked the firewall rules and add a rule for port at start of an issue:
non-local port: any (nothing)
local port: 8123
direction: IN-/OUT- going
protocol: TCP
non-local address: any (nothing)
local address: any (nothing)

from foxy-miner.

The same rule on router = checked;
Shut down the firewall = checked.

from foxy-miner.

some Node.js v.16.14.0 modules requires Python and VisualStudio Tools for compilation and it should install with Node.js package.
But when I'm installing the Node.js as is it rolls up some error when I've tried install Python and VisualStudio Tools from Node.js package.

I've uninstall the Node.js, then install Python 3.10 and then VisualStudio Tools 2022 with the following packets:

Then install Node.js.
I've started foxy-miner after all this proccess and got the same error with "connection outage".

I'm thinking that there is some errors with Node.js dependencies or maybe Node.js requires some specific port opened, but don't have any thoughts where to go.

Maybe someone got the same problems and have a solution?

from foxy-miner.

i dont think any of that is related to the issue, you can also try with the exe from the github release which includes all dependencies

it still looks like your firewall is blocking internet for foxy-miner, adding the signa p2p port does not help at all, rather you should whitelist the foxy miner binary/node.exe

from foxy-miner.

It's certainly because of some net settings rule, but there is no obvious reason for it.
I've made a trustworthy settings in firewall/antivirus for all applets that got dependencies with SIGNA node and foxy-miner too;
I've shut down antivirus before start of foxy-miner;
Downloaded and rolled-up the github release of foxy-miner (again);
Backed up foxy-miner.yaml and made the miner settings from scratch.

After all of that it still with "connection outage" after foxy-miner starts.
Maybe there is some other specific port that needs to be open including port 8123?

from foxy-miner.

again, port 8123 is the p2p port for the signum node, foxy miner does not connect to your signum node, nor does it open any port for external use. It connects to the pool gateway over http.

from foxy-miner.