[bug]: Cannot curl my Embassy A from the SSH of my Embassy B

islandbitcoin commented 1 year ago

Prerequisites

[X] I have searched for existing issues that already report this problem.

embassyOS Version

0.3.2.1

Device

Laptop/Desktop

Device OS

MacOS

Device OS Version

Monterey

Browser

Other

Browser Version

tmux

Current Behavior


MacMax:Repos dread$ ssh start9@embassy-scarce-yawns.local

Welcome to
          |                        ,---.,---.
,---.,-.-.|---.,---.,---.,---.,   .|   |`---.
|---'| | ||   |,---|`---.`---.|   ||   |    |
`---'` ' '`---'`---^`---'`---'`---|`---'`---'
                              `---'
   GNU/Linux (5.10.92-v8+ aarch64)
   embassyOS v0.3.2.1 - 2f8a25ae2679a11161c7f3cc70be04ecedfbea1b

 * Documentation:  https://start9.com
 * Management:     https://embassy-scarce-yawns.local
 * Support:        https://t.me/start9_labs

start9@embassy-scarce-yawns:~ $ curl faded-soaps.local
curl: (6) Could not resolve host: faded-soaps.local

Expected Behavior

curl faded-soaps.local
<html>
<head><title>301 Moved Permanently</title></head>
<body>
<center><h1>301 Moved Permanently</h1></center>
<hr><center>nginx/1.18.0</center>
</body>
</html>

Steps to Reproduce

Start Embassy A
SSH into Embassy A
curl embassy-b.local

Anything else?

No response

islandbitcoin commented 1 year ago

Additional information: the curl was working before I started the migration process. tried a system rebuild, no luck.

start9@embassy-f5fb24ed:~ $ curl faded-soaps.local
<html>
<head><title>301 Moved Permanently</title></head>
<body>
<center><h1>301 Moved Permanently</h1></center>
<hr><center>nginx/1.18.0</center>
</body>
</html>
start9@embassy-f5fb24ed:~ $ sudo -i
root@embassy-f5fb24ed:~# mkdir -p .ssh
root@embassy-f5fb24ed:~# ssh-keygen -t ed25519 -N '' -f .ssh/embassy2.key
Generating public/private ed25519 key pair.
Your identification has been saved in .ssh/embassy2.key
Your public key has been saved in .ssh/embassy2.key.pub
The key fingerprint is:
[REDACTED] root@embassy-f5fb24ed
The key's randomart image is:
+--[ED25519 256]--+
|.E==o.           |
| *+oo            |
|..oo             |
|  o      o o     |
| . .  . S = .    |
| ....+ . . =     |
|. ==+.o o * o    |
|.+oO=  . * +     |
|..=oo. o= .      |
+----[SHA256]-----+
root@embassy-f5fb24ed:~# chmod 600 .ssh/embassy2.key*
root@embassy-f5fb24ed:~# cat .ssh/embassy2.key.pub
ssh-ed25519 [REDACTED] root@embassy-f5fb24ed
root@embassy-f5fb24ed:~# cd /embassy-data/package-data/volumes/bitcoind/data/main/
root@embassy-f5fb24ed:/embassy-data/package-data/volumes/bitcoind/data/main# rsync -e "ssh -i ~/.ssh/embassy2.key" -povgr --append-verify --rsync-path="sudo mkdir -p /embassy-data/package-data/volumes/bitcoind/data/main ; sudo rsync" ./{blocks,chainstate} start9@faded-soaps.local:/embassy-data/package-data/volumes/bitcoind/data/main/
ssh: Could not resolve hostname faded-soaps.local: Temporary failure in name resolution
rsync: connection unexpectedly closed (0 bytes received so far) [sender]
rsync error: unexplained error (code 255) at io.c(228) [sender=3.2.3]
root@embassy-f5fb24ed:/embassy-data/package-data/volumes/bitcoind/data/main# curl faded-soaps.local
curl: (6) Could not resolve host: faded-soaps.local
root@embassy-f5fb24ed:/embassy-data/package-data/volumes/bitcoind/data/main#

dr-bonez commented 1 year ago

unable to reproduce

islandbitcoin commented 1 year ago

I just recreated it again on my 0.3.3 Screenshot 2022-11-27 at 6 45 03 PM

kn0wmad commented 1 year ago

I just recreated it again on my 0.3.3

What did you do to repro?

islandbitcoin commented 1 year ago

nothing more than what's in the screenshot.

I have the crime scene if you want to dig in

kn0wmad commented 1 year ago

I was hoping you had reproduced since this is the only instance we have - have you gone through avahi to make sure it's healthy? Can you curl by IP?

MattDHill commented 1 year ago

Please reopen if you can reproduce and demo

islandbitcoin commented 1 year ago

I can reproduce and demo, and have many times, which is what the screenshot is above. Let me know what other steps are needed.

k0gen commented 1 year ago

@islandbitcoin it is not working because you are missing embassy- the proper command is:

curl embassy-faded-soaps.local

islandbitcoin commented 1 year ago

no, my box was made when we didn't have embassy as the prefix, so the name is correct.

islandbitcoin commented 1 year ago

I've also tried this between two boxes that have the name embassy-xxxx-xxxx and embassy-xxxx-xxxx

kn0wmad commented 1 year ago

@islandbitcoin reproduce means on systems that don't currently have this problem - not just recreating on the existing problem systems. Have you been able to repro on other systems besides the first ones?

Also does the bug persist if you use a different network?

islandbitcoin commented 1 year ago

understood. I'll leave this alone, it looks like it's specific to my network.

Start9Labs / start-os