BitcoinMechanic

I like that. The instinct to hover over something that looks like a problem is well established imo.

This is a different issue, but related: https://github.com/Start9Labs/embassy-os/issues/1724 tldr: This is probably another feature request where an error message needs to close any still-open previous error message. Currently new errors...

I currently have this issue on my test box. I won't disturb it in case investigation is possible.

To be clear though, being able to access embassy-xxxx.local is more than I can do. I can only access that via IP.

This gets things up and running again: `sudo service embassyd restart`

No, it seems to only happen the first time you do it on any particular build.

@chrisguida Has the issue too I believe

I don't currently have the issue.

Agreed, modified title.

Nothing else on my network is odd. Just triggered it downloading cryptpad. Request and response tabs both empty, so this seems to not have even gotten a response.