Update documentation for cases when server has no public DNS name #186
Conversation
docs/user-level.md
Outdated
| @@ -197,7 +197,7 @@ BTC RPC Explorer is a very powerful Bitcoin explorer that uses your own full nod | |||
| * Tor onion domain is generated by default. | |||
| * Install `selfhost-clearnet` to activate clearnet domain **continue reading the docs!** | |||
| * Installation of `selfhost-clearnet` **requires interaction** because it asks for domain. | |||
| * **You must have a working domain pointing to your node for `selfhost-clearnet` to work!** | |||
| * **You must have a working domain pointing to your node for `selfhost-clearnet` to work!** Otherwise you can remove `selfhost-clearnet-certbot` to prevent certificate retrieval error during package configuration | |||
There was a problem hiding this comment.
Maybe instead of "Otherwise" write "If you installed it by mistake", I think it should be clearer. What do you think?
There was a problem hiding this comment.
In my case selfhost-clearnet-certbot wasn't installed by mistake. It just comes together with selfhost-clearnet. Just checked it in docker:
There was a problem hiding this comment.
Well, selfhost-clearnet doesn't work with working domain either (unless you path /etc/hosts but that's an edge case), so even installing that one is probably a mistake.
There was a problem hiding this comment.
Probably it is an undocumented hack, but selfhost-clearnet works fine if you provide ipv4 address as the domain name. The only issue is that selfhost-clearnet-certbot fails to configure in such case. So, removing selfhost-clearnet-certbot makes dpkg happy and keeps selfhost-clearnet available by ip address via http. It's definetly not a secure way to use selfhost dashboard, but the esiest to get it up and running. Maybe it makes sense to describe this way in documentation as possible but not recommended?
There was a problem hiding this comment.
Oh, it didn't occur to me it could be possible. I agree with documenting it is possible but a bad idea due to security issues. I also wouldn't be surprised if some applications didn't work.
…name" This reverts commit 4db4931.
Just a suggestion what to do with the error during
selfhost-clearnet-certbotconfiguration if server has no public DNS name