Unable to build and run NBXplorer Ubuntu

[ghost]

Hi, cannot even get past the 1st step of you're instructions:

From cloned NBXplorer root folder ./run.sh The application to execute does not exist '/root/NBXplorer/NBXplorer/bin/Release/netcoreapp2.1/NBXplorer.dll'

Also same message as above if I just execute command: dotnet run --no-launch-profile --no-build -c Release -p "NBXplorer/NBXplorer.csproj" -- $@ --chains=btc,ltc --network=testnet

[NicolasDorier]

the 1st step is .\build.sh not .\run.sh

[ghost]

Ah sorry my bad misread it, will try again

[ghost]

Issues with /.run.sh after building, please see below:

btcd, ltcd & dashd are installed and syncing, do I need to wait for full sync? Not sure what is going on here.... maybe missed something in configuration

[NicolasDorier]

Yes this is configuration. I can't tell you what is going on without all the command line that you ran for each of the nodes, as well as their log for each of them.

[ghost]

Bitcoind & Litecoind Followed this: https://github.com/mmgen/mmgen/wiki/Install-Bitcoind-from-Source-on-Debian-or-Ubuntu-Linux (Without optional ABC)

Dashd git clone https://github.com/dashpay/dash.git cd dash/ ./autogen.sh ./configure --disable-wallet --without-gui --without-miniupnpc make check

From: https://github.com/dashpay/dash/blob/master/doc/build-unix.md

NBXplorer ./run.sh --chains=btc,ltc,dash --network=testnet --port=91 --bind=0.0.0.0

Still looking for logs but did you mean logs from build or logs from NBXplorer ./Run.sh...?

[NicolasDorier]

This is not command line for starting dash, but for building dash. I need command line you used for starting dash as well as dash logs.

[ghost]

I just started dash via command dashd and the process started, that is all. I am not sure where can find logs, I am mainly a Windows guy and my VPS is all Ubuntu commandline, no GUI

[NicolasDorier]

I need the logs to help you, and I don't know where dash put it.

[ghost]

Ok I will find them, but also seems to be connection RPC error with BTC and LTC nodes as in the screenshot output images attached......

[NicolasDorier]

also, you are running network in testnet, so you need to run same on dash

[NicolasDorier]

so give me the logs.

[ghost]

Could only find DASH Config.log, no idea where any NBXplorer or other Dash logs are, do not know what they are names either so It makes hard to search, this is all i could find from commandline search.

I appreciate this will not help, do you know of a compatible configuration that will work for NBXplorer?

DASH_Config.log

[NicolasDorier]

not what I need, sorry I can't help you I don't know Dash.

[ghost]

You did not specify if you want a log from Dash or NBXplorer, anyway I will forget about Dash support but can you see there are also issues with BTC and LTC when running NBXplorer, as in the images......

[NicolasDorier]

so give me debug logs in ~/.litecoin

[ghost]

This is all in ~/.litecoin

aclocal.m4 configure doc Makefile.am autogen.sh configure.ac INSTALL.md Makefile.in autom4te.cache contrib libbitcoinconsensus.pc README.md build-aux CONTRIBUTING.md libbitcoinconsensus.pc.in share config.log COPYING libtool src config.status depends Makefile test

No logs except for Config.log

[NicolasDorier]

this is build log files. Sorry I don't know why there is no litecoin debug.log, search for it.

[ghost]

Cool that is all i needed the name of the actual logs to search ;)

Please see attached

logs.zip

[NicolasDorier]

I don't know. If you start bitcoind, litecoind and NBXplorer without any settings ~apart from -regtest~ (nothing if you run on mainnet) on same machine (either all using linux or all using windows), then it should connect. I don't see anything that can help in those file sadly.

[ghost]

How did you set it up while you were integrating with BTCPayServer?

[ghost]

Seems i need to edit the following:

btc.node.endpoint=127.0.0.1:BTC //Should be 0.0.0.0 for remote bind --bind=0.0.0.0 yes?

startheight defines from which block you will start scanning, if -1 is set, it will use current blockchain height

btc.startheight=-1

rescan forces a rescan from startheight

btc.rescan=0

This is the RPC Connection to your node

ltc.rpc.url=http://127.0.0.1:19332/ //Should be 0.0.0.0 for remote bind --bind=0.0.0.0 yes?

By user name and password

ltc.rpc.user=bitcoinuser

ltc.rpc.password=bitcoinpassword

By cookie file

ltc.rpc.cookiefile=yourbitcoinfolder/.cookie /usr/bin/litecoin/.cookie yes?

[NicolasDorier]

yes you use the configuration file.

[ghost]

Yes but the settings.config says at top of file: "####If Bitcoin Core is running with default settings, you should not need to modify this file####"

[NicolasDorier]

every parameter documented by ./run.sh --help can be set either through configuration file or environment variables.

[ghost]

Ok and how about here as per GitHub docs:

"If you are using Bitcoin core default settings: On Linux: ./build.sh"

Does ./build.sh have anything configurable of look into settings.config file????

[NicolasDorier]

no

[ghost]

Got it figured out

[ghost]

Sorry have to reopen this I ran into some config issues again on VPS server with bitcoind and NBXplorer, what is the issue here? Config file issue or i have to wait for bitcoin node to fully sync? Thanks

[ghost]

Looks like needs to be Synced yes