Could not connect to BTCPay from external

[0xjacobb]

Hi

Use Case: I want to use BTCPay on mynode for selling goods as merchant on my own website. Customers must reach BTCPay from external network.

Setup problem: BTCPay internal port is 49392. My modem can not port forwarding port 80 (HTTP) and 443 (HTTPS) from external to the same internal port 49392.

Actual state: One feedback from mynode support was (thanks to @tehelsper for clarification):
"There are not current supported or suggested ways to run BTC Pay server outside of your local network. While it is possible, it opens up additional security risks I do not want to majority of myNode users to experience."

Questions/Issue:

1. Would it be possible to add this functionality to reach BTCPay from external? In my view, it doesn't make sense to have BTCPay on mynode without possibility to reach from external (merchant use case)
2. If 1) = yes. There are modems (like mine) which need not only one, but two internal BTCPay port

Many thanks.

[Transisto]

This is what most people expect of BTCPAY, generate invoices and get paid.

Seems like an explanation should be written in the UI to explain this is only available through Tor for XYZ reasons.

Also none of the browser I use go anywhere when trying to go to mynodebtc.local
and BTCPAY won't let me do anything

[0xjacobb]

Seems like an explanation should be written in the UI to explain this is only available through Tor for XYZ reasons.

It's possible via Tor? Did not know that. I've setup another Raspi4 just for BTCPay and they provide two ports: 80 and 433 so you can configure the modem 80<-> 80 and 443<->443.

It would be great to have that possibility on mynode in the future.

Many Thanks.

[Transisto]

@tehelsper

Please add BTCPAY in Tor service page with port 49392

[tehelsper]

BTCPay external access is not officially supported. Closing.

[0xjacobb]

Hi Tylor This is the 4th update which made some problems on mynode. I don't know why this time. Can't launch. [Bildschirmfoto 2020-08-19 um 23.15.57.png]

…

--> Services looking good [Bildschirmfoto 2020-08-19 um 23.16.27.png]

--> But this not [Bildschirmfoto 2020-08-19 um 23.17.01.png]

--> Reboot, power down didn't help Log: + set -e + date Tue 18 Aug 14:58:17 CDT 2020 + /usr/bin/mynode_stop_critical_services.sh Stopping myNode services... Warning: The unit file, source configuration file or drop-ins of glances.service changed on disk. Run 'systemctl daemon-reload' to reload units. Warning: The unit file, source configuration file or drop-ins of lndhub.service changed on disk. Run 'systemctl daemon-reload' to reload units. Warning: The unit file, source configuration file or drop-ins of netdata.service changed on disk. Run 'systemctl daemon-reload' to reload units. Warning: The unit file, source configuration file or drop-ins of rtl.service changed on disk. Run 'systemctl daemon-reload' to reload units. Warning: The unit file, source configuration file or drop-ins of webssh2.service changed on disk. Run 'systemctl daemon-reload' to reload units. Warning: The unit file, source configuration file or drop-ins of btc_rpc_explorer.service changed on disk. Run 'systemctl daemon-reload' to reload units. Dojo is already stopped. Warning: The unit file, source configuration file or drop-ins of electrs.service changed on disk. Run 'systemctl daemon-reload' to reload units. Warning: The unit file, source configuration file or drop-ins of loopd.service changed on disk. Run 'systemctl daemon-reload' to reload units. Warning: The unit file, source configuration file or drop-ins of lnd.service changed on disk. Run 'systemctl daemon-reload' to reload units. Warning: The unit file, source configuration file or drop-ins of quicksync.service changed on disk. Run 'systemctl daemon-reload' to reload units. Warning: The unit file, source configuration file or drop-ins of bitcoind.service changed on disk. Run 'systemctl daemon-reload' to reload units. + rm -rf /var/log/alternatives.log /var/log/apt /var/log/auth.log /var/log/auth.log.1 /var/log/auth.log.2 /var/log/bitcoind.log /var/log/bitcoind.log.1 /var/log/bitcoind.log.2 /var/log/boot.log /var/log/btmp /var/log/btmp.1 /var/log/caravan.log /var/log/caravan.log.1 /var/log/daemon.log /var/log/daemon.log.1 /var/log/daemon.log.2 /var/log/debug /var/log/debug.1 /var/log/debug.2 /var/log/dpkg.log /var/log/dpkg.log.1 /var/log/dpkg.log.2.gz /var/log/dpkg.log.3.gz /var/log/electrs.log /var/log/electrs.log.1 /var/log/electrs.log.2 /var/log/fail2ban.log /var/log/fail2ban.log.1 /var/log/fail2ban.log.2.gz /var/log/fail2ban.log.3.gz /var/log/fail2ban.log.4.gz /var/log/flask /var/log/flask.1 /var/log/flask.2 /var/log/gunicorn /var/log/kern.log /var/log/kern.log.1 /var/log/kern.log.2 /var/log/lastlog /var/log/lnd_backup.log /var/log/lnd_backup.log.1 /var/log/lnd_backup.log.2 /var/log/lndconnect.log /var/log/lndhub.log /var/log/lndhub.log.1 /var/log/lndhub.log.2 /var/log/lnd.log /var/log/lnd.log.1 /var/log/lnd.log.2 /var/log/log2ram.log /var/log/loopd.log /var/log/loopd.log.1 /var/log/loopd.log.2 /var/log/messages /var/log/messages.1 /var/log/messages.2 /var/log/mynode_docker_images.log /var/log/mynode_docker_images.log.1 /var/log/mynode_docker_images.log.2 /var/log/mynode.log /var/log/mynode.log.1 /var/log/mynode.log.2 /var/log/mynode_quicksync.log /var/log/mynode_quicksync.log.1 /var/log/mynode_quicksync.log.2 /var/log/nginx /var/log/openvpn.log /var/log/openvpn.log.1 /var/log/openvpn.log.2.gz /var/log/openvpn.log.3.gz /var/log/openvpn.log.4.gz /var/log/openvpn-status.log /var/log/private /var/log/redis /var/log/rtl.log /var/log/rtl.log.1 /var/log/rtl.log.2 /var/log/syslog /var/log/syslog.1 /var/log/syslog.2 /var/log/tor /var/log/ufw.log /var/log/ufw.log.1 /var/log/ufw.log.2.gz /var/log/ufw.log.3.gz /var/log/ufw.log.4.gz /var/log/unlock_lnd.log /var/log/unlock_lnd.log.1 /var/log/unlock_lnd.log.2 /var/log/user.log /var/log/user.log.1 /var/log/user.log.2 /var/log/wtmp /var/log/ www.log /var/log/ www.log.1 /var/log/ www.log.2 + mkdir -p /var/log/nginx + TORIFY= + '[' -f /mnt/hdd/mynode/settings/torify_apt_get ']' + systemctl stop https Warning: The unit file, source configuration file or drop-ins of https.service changed on disk. Run 'systemctl daemon-reload' to reload units. Thanks for the help Marc

[0xjacobb]

Hi Taylor I've have problems since 0.2.13. Always the same like described below. Fallback is always: Flash a new SD and go to latest version from Github. But this could not be the solution! I want to understand the problem and hopefully solve it. Could you assist me on that? [Bildschirmfoto 2020-08-31 um 21.13.24.png] Best Marc

[tehelsper]

What is the problem that requires a reflash? I may need to make a new RP4 image.

[0xjacobb]

As I described: 1. tried to "UPDATE" via button on mynode (premium verison) 2. Node is working and I can SSH via CLI 3. When I login via GUI, the sent description came up ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ Am Montag, 31. August 2020 21:48 schrieb Taylor Helsper <notifications@github.com>:

…

What is the problem that requires a reflash? I may need to make a new RP4 image. — You are receiving this because you authored the thread. Reply to this email directly, [view it on GitHub](#298 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/AHYCD6QWGOTSHIP5U5WYM2TSDP47JANCNFSM4MNG7ENA).

[tehelsper]

Ok weird. Im not seeing the images. What was the message?

[0xjacobb]

this was the log: =========================================================== === Upgrade Attempt #1 =========================================================== + set -e + date Mon 31 Aug 13:07:33 CDT 2020 + /usr/bin/mynode_stop_critical_services.sh Stopping myNode services... Warning: The unit file, source configuration file or drop-ins of glances.service changed on disk. Run 'systemctl daemon-reload' to reload units. Warning: The unit file, source configuration file or drop-ins of lndhub.service changed on disk. Run 'systemctl daemon-reload' to reload units. Warning: The unit file, source configuration file or drop-ins of rtl.service changed on disk. Run 'systemctl daemon-reload' to reload units. Warning: The unit file, source configuration file or drop-ins of webssh2.service changed on disk. Run 'systemctl daemon-reload' to reload units. Warning: The unit file, source configuration file or drop-ins of btc_rpc_explorer.service changed on disk. Run 'systemctl daemon-reload' to reload units. /usr/bin/mynode_stop_critical_services.sh: line 27: /opt/mynode/dojo/docker/my-dojo/dojo.sh: No such file or directory Warning: The unit file, source configuration file or drop-ins of electrs.service changed on disk. Run 'systemctl daemon-reload' to reload units. Warning: The unit file, source configuration file or drop-ins of loopd.service changed on disk. Run 'systemctl daemon-reload' to reload units. Warning: The unit file, source configuration file or drop-ins of lnd.service changed on disk. Run 'systemctl daemon-reload' to reload units. Warning: The unit file, source configuration file or drop-ins of quicksync.service changed on disk. Run 'systemctl daemon-reload' to reload units. Warning: The unit file, source configuration file or drop-ins of bitcoind.service changed on disk. Run 'systemctl daemon-reload' to reload units. + rm -rf /var/log/alternatives.log /var/log/apt /var/log/auth.log /var/log/auth.log.1 /var/log/auth.log.2 /var/log/bitcoind.log /var/log/bitcoind.log.1 /var/log/bitcoind.log.2 /var/log/boot.log /var/log/bootstrap.log /var/log/btmp /var/log/btmp.1 /var/log/daemon.log /var/log/daemon.log.1 /var/log/daemon.log.2 /var/log/debug /var/log/debug.1 /var/log/debug.2 /var/log/dpkg.log /var/log/dpkg.log.1 /var/log/dpkg.log.2.gz /var/log/electrs.log /var/log/electrs.log.1 /var/log/electrs.log.2 /var/log/fail2ban.log /var/log/fail2ban.log.1 /var/log/fail2ban.log.2.gz /var/log/fail2ban.log.3.gz /var/log/faillog /var/log/flask /var/log/flask.1 /var/log/flask.2 /var/log/fontconfig.log /var/log/gunicorn /var/log/kern.log /var/log/kern.log.1 /var/log/kern.log.2 /var/log/lastlog /var/log/lnd_backup.log /var/log/lnd_backup.log.1 /var/log/lnd_backup.log.2 /var/log/lndconnect.log /var/log/lndhub.log /var/log/lndhub.log.1 /var/log/lndhub.log.2 /var/log/lnd.log /var/log/lnd.log.1 /var/log/lnd.log.2 /var/log/log2ram.log /var/log/loopd.log /var/log/loopd.log.1 /var/log/loopd.log.2 /var/log/messages /var/log/messages.1 /var/log/messages.2 /var/log/mynode_docker_images.log /var/log/mynode_docker_images.log.1 /var/log/mynode_docker_images.log.2 /var/log/mynode.log /var/log/mynode.log.1 /var/log/mynode.log.2 /var/log/mynode_quicksync.log /var/log/mynode_quicksync.log.1 /var/log/mynode_quicksync.log.2 /var/log/openvpn /var/log/openvpn.log /var/log/openvpn.log.1 /var/log/openvpn-status.log /var/log/private /var/log/redis /var/log/rtl.log /var/log/rtl.log.1 /var/log/rtl.log.2 /var/log/syslog /var/log/syslog.1 /var/log/syslog.2 /var/log/sysstat /var/log/tor /var/log/ufw.log /var/log/ufw.log.1 /var/log/ufw.log.2.gz /var/log/ufw.log.3.gz /var/log/unlock_lnd.log /var/log/unlock_lnd.log.1 /var/log/user.log /var/log/user.log.1 /var/log/user.log.2 /var/log/wtmp /var/log/www.log /var/log/www.log.1 /var/log/www.log.2 + mkdir -p /var/log/nginx + TORIFY= + '[' -f /mnt/hdd/mynode/settings/torify_apt_get ']' + systemctl stop https Warning: The unit file, source configuration file or drop-ins of https.service changed on disk. Run 'systemctl daemon-reload' to reload units. ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ Am Dienstag, 1. September 2020 00:12 schrieb Taylor Helsper <notifications@github.com>:

…

Ok weird. Im not seeing the images. What was the message? — You are receiving this because you authored the thread. Reply to this email directly, [view it on GitHub](#298 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/AHYCD6VAS5BTNQX2TTBMF4LSDQN33ANCNFSM4MNG7ENA).