btc-rpc-explorer VS docker-swag

Get a non-custodial wallet: This is where you start to believe you really have Bitcoin, but it is still not perfect. A non-custodial wallet (like BlueWallet) is one of the slow types of Bitcoin wallets (on-chain) but this is where I think you, as a inquisitive mind, should start. Others will start with lightning wallets so they can buy beer right away. BlueWalllet has you create a "wallet" and gives you "seed words" to write down and keep safe. This is private. Do not take pictures of it, screenshots of it, and do not save it to a digital file. Paper is really easy and there's no risk of undiscovered malware being able to see what you write on paper. You'll very quickly learn the lingo: "wallet", "addresses", "utxo", etc. When you receive funds, the wallet will show you your balance like Coinbase does, but it will also show you a "transaction id". This, you can use to check that your transaction is real by checking a blockchain explorer like "https://mempool.space" or "https://bitcoinexplorer.org/". You are now able to check multiple sources, increasing your belief that the Bitcoin is real.

- Bitcoinexplorer.org https://github.com/janoside/btc-rpc-explorer (lang: nodejs, db: none) I would like to prioritize practical issues such as displaying fees and general ease of use for viewing transaction details, these are the topics of discussion. I am looking forward to your opinions.

I'm not aware of a desktop explorer, but it probably wouldn't be as advanced as something like https://github.com/janoside/btc-rpc-explorer

BitcoinExplorer — https://bitcoinexplorer.org/

It depends what you're running. Raspiblitz, for example, allows you to use btc rpc explorer (https://github.com/janoside/btc-rpc-explorer) and mempool (https://github.com/mempool/mempool) quite easily.

BTC RPC Explorer v3.3.0 (Released: 7th December 2021) - https://github.com/janoside/btc-rpc-explorer/releases

I have a NAS on .0.181 and a swag container (on a different port than nginx) on .0.180 that points to my public facing services. For obvious reasons, I don't want my public domain to point to any other ports/addresses on my home network. Additionally, as elegant as swag is, it requires authentication and so won't work for simple local DNS. I now have one local domain for each server and an nginx instance on each that resolves to my different services on each.

OP is even linking the Github... https://github.com/linuxserver/docker-swag

I have an UnRAID server with a few services (Jellyfin, Nextcloud, etc.) running on it behind Linux Servers' SWAG reverse proxy container, which is built on Nginx and Let's Encrypt. This is pointed to a DuckDNS link, which is then pointed at my domain with a CNAME. So I can access Jellyfin, for example, at jellyfin.mydomain.com. A few weeks ago, due to seemingly unrelated issues, I got a new modem/router, an Arris SURFboard G34. For the first few weeks, everything was working as before. But now, when on my LAN, I can't get to my services at the proxied domain. It times out every time. There are no errors in SWAG's logs, nothing seems amiss in the router's web interface, and the services are available both at their IP:port address and, when not on my LAN, I can access them at the domain no problem.

Reverse proxy, probably? I use Docker SWAG, setup here, with DuckDNS and it works really well for me. There are of course many ways to reverse proxy, as I linked to earlier.