 Show Posts
|
|
Pages: [1]
|
i think you do need a tld (domainname) if you want to use certbot... IIRC, you'd have to execute following command after nginx is running correctly: certbot --nginx -d yourdomain.com -d www.yourdomain.com There's always the option of creating a self signed certificate, but you'll probably be confronted with warning messages later on if you do so... After some tinkering around in nginx and certbot, I realized that I never actually created server blocks for Let's Encrypt to verify, LOL I created the server block for my domain and tried to run certbot to obtain my SSL certificates, and ran into a weird error... not sure if you might know what's going on:  After doing this, I checked the DNS Zone Editor of my site and the DNS records list a bunch of TXT records that I haven't seen before  |
|
|
|
The correct sequence is: start bitcoind as a daemon: Wait untill it's running, if you're unsure wait 5 minutes then look at the debug.log tail -f ~/.bitcoin/debug.log
press ctrl+c if you're sure bitcoind is running nbxplorer connects to bitcoind. It builds a database of unspent outputs and lets other services query this database. nbxlorer needs to be running so btcpayserver can use it's services! in order to do this, you'll eventually make a service, but for now, open a screen session (it's possible you'll need to install screen first) within this screen session, start nbxplorer... Without killing nbxplorer, leave your screen session by pressing cltr-a, release ctrl-a, then press the letter d now, wait another 5 minutes to make sure nbxplorer is properly running, then check if it's listening on port 24445 like we configured here's what i see when looking at my server: lsof -i :24445
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
BTCPaySer 5092 root 278u IPv4 18588382 0t0 TCP localhost:41210->localhost:24445 (ESTABLISHED)
BTCPaySer 5092 root 282u IPv4 18587254 0t0 TCP localhost:41220->localhost:24445 (ESTABLISHED)
dotnet 11889 root 156u IPv4 1753666419 0t0 TCP localhost:24445 (LISTEN)
dotnet 11889 root 188u IPv4 18590828 0t0 TCP localhost:24445->localhost:41210 (ESTABLISHED)
dotnet 11889 root 191u IPv4 18587256 0t0 TCP localhost:24445->localhost:41220 (ESTABLISHED)
without starting btcpayserver you won't see these connections, but you should see some output... If you don't get any return, nbxplorer is not listening on the correct port now, open a second screen session and run btcpayserver in this screen session you don't need to do anything with the run.sh bash script. The only thing this script contains is the command you're running right now: dotnet run --no-launch-profile --no-build -c Release -p ~/source/btcpayserver/BTCPayServer/BTCPayServer.csproj --@ for shutting down, it's exactly the opposite order: take over the btcpayserver screen by finding out the pid of the 2 screen sessions: then take over the screen session of btcpayserver screen -r [pid from previous command]
ctrl-c you can stop this screen session by giving the following command withing the screen session then stop the nbxplorer in the same way as you stopped btcpayserver then stop bitcoin daemon by entering Hi Mocacinno, I followed your sequence and got everything to run correctly from bitcoind to NBXplorer and BTCPayServer. From there I figured that I needed to continue the setup of BTCPayServer to run on my site so I followed the guide here to do it manually: [quotehttps://docs.btcpayserver.org/ManualDeploymentExtended/[/quote] I skipped ahead to the nginx Let's Encrypt section and attempted to use certbot to get my TLS certificate and get everything set up. I think I'm running into yet another problem with setting up certificates here. I followed the first two commands and restarted nginx, then tried to check Let's Encrypt and when I typed the command: sudo certbot certificates I got the following prompt: myuser@rpi:~ $ sudo certbot certificates
Saving debug log to /var/log/letsencrypt/letsencrypt.log
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
No certs found.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Now I think this is happening because I input some code snippet incorrectly, perhaps something to do with writing down the SSL certificate URLs on the configuration file for nginx, but I'm not sure. Some guidance would be appreciated if possible  Thanks! |
|
|
|
Hi Mocacinno, below I've included a snippet of code detailing what happens when I try to run the service how you've explained to do: [myuser]@rpi:~ $ dotnet run --no-launch-profile --no-build -c Release -p ~/source/btcpayserver/BTCPayServer/BTCPayServer.csproj -- info: Configuration: Data Directory: /home/admin/.btcpayserver/Main info: Configuration: Configuration File: /home/admin/.btcpayserver/Main/settings.config info: Configuration: Network: Mainnet info: Configuration: Supported chains: BTC info: BTCPayServer.Plugins.PluginManager: Loading plugins from /home/admin/.btcpayserver/Extensions info: Configuration: Network: Mainnet info: Configuration: Supported chains: BTC info: Configuration: Postgres DB used info: Configuration: Root Path: / info: Configuration: BTC: Explorer url is http://127.0.0.1:24445/info: Configuration: BTC: Cookie file is /home/admin/.nbxplorer/Main/.cookie info: PayServer: Starting listening NBXplorer (BTC) info: PayServer: Start watching invoices fail: PayServer: BTC: NBXplorer error `Connection refused`info: PayServer: Starting payment request expiration watcher info: PayServer: 0 pending payment requests being checked since last run info: Configuration: Listening on http://0.0.0.0:23001It seems like the NBXplorer service is failing for some reason. However, when I go into the NBXplorer directory and try to run the dotnet run -- command it seems fine: myuser@rpi:~ $ cd ~/NBXplorer/NBXplorer myuser@rpi:~/NBXplorer/NBXplorer $ dotnet run -- info: Configuration: Data Directory: /home/admin/.nbxplorer/Main info: Configuration: Configuration File: /home/admin/.nbxplorer/Main/settings.config info: Configuration: Network: Mainnet info: Configuration: Supported chains: BTC info: Configuration: DBCache: 50 MB info: Configuration: Network: Mainnet info: Configuration: Supported chains: BTC info: Configuration: DBCache: 50 MB info: Explorer: Defragmenting transaction tables... info: Explorer: Defragmentation succeed, 0 bytes saved info: Explorer: Applying migration if needed, do not close NBXplorer... info: Configuration: BTC: Testing RPC connection to http://localhost:8332/Hosting environment: Development Content root path: /home/admin/NBXplorer/NBXplorer/bin/Debug/netcoreapp3.1/ Now listening on: http://127.0.0.1:24445Application started. Press Ctrl+C to shut down. info: Configuration: BTC: RPC connection successful info: Configuration: BTC: Full node version detected: 200100 info: Configuration: BTC: Node banlist loaded info: Events: BTC: Node state changed: NotStarted => CoreSynching Do I need to change something about how NBXplorer is running? If I have a service that starts NBXplorer when the raspberry pi turns on, will that solve my issue? One more note, I'm confused on how/where to use the run.sh command, and if necessary, how to copy the command into a service file to run it. |
|
|
|
You have a valid point @mocacinno ... With this in mind I decided to delete the docker files and try to reinstall BTCPayServer using a manual setup following the guide here: I hadn't installed PostGreSQL on my Pi yet so I followed this guide to try and set it up. Created a username and password and copied my lightning fingerprint into the settings.config and ran into an issue on... Step 4: Install BTCPayServer I ran into a problem verifying the install worked correctly using dotnet. I tried running the command: dotnet run -p ~/source/btcpayserver/BTCPayServer/BTCPayServer.csproj -c ~/.btcpayserver/Main/settings.config --network=mainnet
and was met with this big wall of warnings and errors:  More confusion... looking for some guidance. Thanks! |
|
|
|
|
@HCP, as a noob, just confused that I had to run it through a directory as there have been other things I've run that did not need to go through a directory.
@Mocacinno, thanks for the advice. Once everything is set up, I will create a set of services that runs these things as soon as I turn on the raspberry pi, but I'm not sure how to do that.
I managed to download BTCPayServer-Docker on the pi and got it to run successfully. I set up a host A record on my website that is supposed to use BTCPayServer (btcpay.website.com) but it's not working and I'm not sure how to proceed (maybe it's related to the ports or something, I can't find where to change those). Maybe you can provide some insight? Thanks for sticking around in the thread!
|
|
|
|
So after lots of troubleshooting and internet searching, I've made some progress! I found the folder ~/.nbxplorer/Main/settings.config and had to uncomment the following code snippets: #btc.rpc.auth=walletuser:password
#port=24444 (Changed to port=24445)
#mainnet=1
I saved this and found the bitcoin.conf file by entering the following command: sudo nano ~/.bitcoin/bitcoin.conf
and edited the file to add these missing lines: daemon=1
maxmempool=50
mempoolexpiry=2
rpcauth=[user]:[pass]
dbcache=1024 (Changed from #dbcache=2000)
whitelist=127.0.0.1
Finally, and this is weird, to run NBXplorer I had to go to the directory: cd ~/NBXplorer/NBXplorer
and enter the command: dotnet run --
It seems like NBXplorer actually ran successfully:  I have three questions stemming from this: - Why did I need to use the dotnet run -- command through a different directory, and is this okay?
- How do I know NBXplorer is running? How do I use it?
- Is the next step to set up btcpayserver?
|
|
|
|
A couple of potential issues: - bitcoind, is it running, can you execute "lsof -i :8332"
- I've listed my bitcoin.conf and nbxplore config's underneath
Do notice the rpcuser/rpcpassword from bitcoin.conf match the user and pass in settings.config  bitcoind: ~/.bitcoin/bitcoin.conf daemon=1
server=1
rpcuser=[rpc user]
rpcpassword=[rpc pass]
maxmempool=50
mempoolexpiry=2
rpcauth=[user]:[pass]
dbcache=1024
zmqpubrawblock=tcp://127.0.0.1:28332
zmqpubrawtx=tcp://127.0.0.1:28332
whitelist=127.0.0.1
nbxplore: ~/.nbxplorer/Main/settings.config btc.rpc.auth=[rpc user]:[rpc pass]
port=24445
mainnet=1
Hi mocacinno, - Bitcoind does appear to be running on the bitcoin user on the pi, can execute "lsof -i :8332" on the bitcoin user and get some feedback but on any other user the command does not return any information. - I opened the bitcoin.conf file and was able to find the information you supplied in your post. It seems like NBXplorer does not have a config file as entering that code results in an error stating the file can't be found, and one command led to a "Permission denied" error. Not sure if I installed Dotnet or NBXplorer incorrectly. I would appreciate some further guidance in this. Thank you so much for all your help so far, you've been a big help. Looking forward to a reply, cheers. |
|
|
|
I downloaded .NET Core 3.1.8 (ARM32) and installed it using the following commands: sudo mkdir -p $HOME/dotnet sudo tar zxf ~/Downloads/dotnet-sdk-3.1.402-linux-arm.tar.gz -C $HOME/dotnet export DOTNET_ROOT=$HOME/dotnet export PATH=$PATH:$HOME/dotnet Then ran sudo nano .profile and added the path commands to the end of the file to permanently link them to the command line to call the dotnet list of commands. Then I installed NBXplorer following a YouTube guide and entered the following commands: git clone https://github.com/dgarage/NBXplorercd NBXplorer/NBxplorer dotnet run -- --help Finally, tried to enter the command dotnet run -- and was met with this RPC server error:  Not sure why the RPC server is unable to connect. Hoping that I can get some clarity on this so I can proceed, it looks like the YouTube video I watched referenced a cookie file on their computer but since I am trying to do this over the Pi I cannot find the right file and it seems like the rpccookiefile command does not work (if I even need it, not sure). |
|
|
|
Well when you put it like that... everything becomes much more clear. It is going to be a clearnet site, and it is a combination of WooCommere + Wordpress. I will have to manually generate some invoices, but majority of the time, the prices will be set and I would like the shop to handle the accounting logistics (and if I could figure out a way for people to place bids, that would be super cool). Not trying to evade taxes or hide from the IRS, and I am already doxed, so realistically I just want the ability to accept crypto payments the right way. I have bitcoind and lnd already installed. Just need to figure out the wallet situation and download a block explorer; I already planned on using btcpayserver . And by no means am I an expert, quite the opposite actually. Would rather start with a beginner setup that I can handle and if anything progress towards the more technical, complex setups further down the line once I have a better handle on things. |
|
|
|
|
For my use case, I am trying to determine the level of privacy that is actually necessary.
FYI, I am building a website and would like to have the capacity to accept BTC and lightning network payments. Not sure if that changes anything, but the main factors I am looking for are safety, privacy, and efficiency. With that in mind, do you think going through the extra hurdles to get electrum up and running is worth it? Or is it just not worth the extra effort? I plan on moving the coins to a hardware wallet most of the time anyways, so this would just be for sending/receiving and temporary short-term storage. I thought that having electrum available on multiple devices might prove beneficial, but maybe I am mistaken or overvaluing the utility it provides? I already have Wasabi downloaded, and am very close to just using that and calling it a day.
As for Discord, yes I am aware it is not the most privacy savvy. However, I do have 2fa enables and take the necessary precautions that are available to protect myself. I have no problems hanging out on this Bitcoin talk forum, however, I assume I will be much less active on here and check it much less frequently than I would a discord server. As we all know, there does come a point where privacy compromises convenience..
|
|
|
|
Funny you say that... I thought to myself the other day that this seemed quite complicated for what was supposed to be a rather simple setup. As this is just the wallet, I would probably be fine settling for something like a Wasabi. Is that the consensus best alternative, and do I download it to the pi or my local desktop? Only reason I went with Electrum in the first place is because it was in the guide and not cutting any corners seemed like the right thing to do. However, if there is no real difference in privacy, I would much rather use the easier, more efficient, updated wallet. I am just about over troubleshooting lol  Out of curiosity, is there perhaps a discord forum for bitcoin talk? I am online much more often over there. Regardless, I appreciate all the guidance! P.s. Thank you for the first merit. Happy to stick around as one of the good guys |
|
|
|
Hi, I checked the Tor configuration and all seems correct. Restarted Tor and ran the commands to start, enable, and start Tor through service. Typed in journalctl -xe and was met with this.  All seems like it's running okay, no apparent issues. However, even without using proxy, I still cannot connect to my raspberry Pi via IP address (showing red light on Electrum). The proxy is working through public servers when I have the Tor browser open on my computer, but still does not work when I use my Pi's IP. |
|
|
|
Looks like I am running into a problem where Electrum (on my computer) will not connect to my Raspberry Pi via its IP. I think this is related to the issue I am having - I keep getting hit with a red light, even without a proxy on. Not sure how to proceed, it worked before but I have reinstalled Electrum several times at this point. In relation to my issues with the Tor proxy, I tried typing in "tor" on the SSH command line prompt to my Pi and was greeted with this snippet of information. Maybe this is related to my problem?  |
|
|
|
Hi everyone, So I uninstalled Electrum and restarted the Electrum section of the Stadicus guide to see if I missed anything (any command line entries or improper file writing). Still ending up with no connection. I followed HCP's advice and found the debug.log in the %appdata% folder. Everything seems to be working up until this error comes up:  In response to BitMaxz, the Tor proxy I am using appears to be online - Tor has been locally installed on my computer - not sure how to run it first through command, I simply open the Tor client prior to opening Electrum. In response to bob123, I'm not sure how to check the logs from my server. My apologies for the lack of experience with command line and technical jargon, I am new to all of this. Hoping this info can help you help me. Thanks! |
|
|
|
Hi all, I reinstalled Electrum 4.0.3 to get the most up-to-date version of the software so I can follow along with your help. I recreated my test wallet (nothing in it to make sure I'm not playing around with real funds yet) and attempted to connect to my Raspberry Pi using the device IP and port 50002. It seems like Electrum will not even connect to the Pi anymore (red light on connection) and I can't figure out why. The service works just fine when I check "Select server automatically", the light turns green. Here's a screenshot of the client in action:  Not sure what is going wrong here, would appreciate some further assistance. Thanks! |
|
|
|
Greetings all, This is my first time in this forum, as I have tried everything else before capitulating to posting in a public forum. It is my hope that by posting this, I will not only be able to solve my problem, but maybe help somebody else that might be experiencing similar difficulties. I have been following the guide by @stadicus ( https://stadicus.github.io/RaspiBolt/ ), and I am at the electrum section. For some reason, I can not get it to connect via proxy. I have followed the guide exactly, and think I have executed every required step. I have done everything from changing the server and proxy settings to going into the command line and console and manually inputting code. I have even manually changed the config files in %appdata%. I have tried the latest version 4.0.3, and even downgraded the version to the one in the guide as a last ditch attempt. Still, nothing. This is obviously a crucial step, as connecting via Tor and using a proxy is your protection from compromising yourself. It is an absolutely critical, non-negotiable step if you do not want to risk getting exposed. If anybody can provide some assistance or point me in the right direction, it would be greatly appreciated! This is one of the last hurdles (hopefully) in my project, so I would like to figure this out ASAP. If you need me to provide any more information, please, let me know! Thanks in advance, Corayee |
|
|
|
|
