`umbrel-dev` wont boot up

[Christewart]

I cannot resolve the address that is displayed after the umbrel-dev boot command. This is running on f6546cba5768aac782de83735510d75cd2b229ce

This is the output from a umbrel-dev logs

[louneskmt]

What about http://umbrel-dev.local?

[Christewart]

What about http://umbrel-dev.local?

Same result

[louneskmt]

Can you try the Tor address? Just to be sure it's a local network issue.

[lukechilds]

@Christewart did you create this VM before updating to 1.3.0?

Could you try shutting down the vm with umbrel-dev shutdown and then in a fresh dir like tmp/umbrel-dev-test or something:

mkdir /tmp/umbrel-dev-test
cd /tmp/umbrel-dev-test
umbrel-dev init
umbrel-dev boot

Then see if that is accessible?

[Christewart]

@Christewart did you create this VM before updating to 1.3.0?

I did not, i rm -rf /my/directory/ && mkdir /my/directory && cd /my/directory/ && umbrel-dev init && umbrel-dev boot

Could you try shutting down the vm with umbrel-dev shutdown and then in a fresh dir like tmp/umbrel-dev-test or something:

mkdir /tmp/umbrel-dev-test
cd /tmp/umbrel-dev-test
umbrel-dev init
umbrel-dev boot

Then see if that is accessible?

Still same result :/

[lukechilds]

Hmmn that's really weird.

Can you curl localhost from within the VM? Just to check the server is definitely running.

umbrel-dev run "curl http://localhost"

Could you also confirm if you can access over the Tor hidden service in Tor Browser. You can get the address with:

umbrel-dev run "cat tor/data/web/hostname"

[Christewart]

[nevets963]

@Christewart When the VM booted, did it prompt you about using a bridge? If so, did you select a network interface? If possible, could you dump the logs from the boot process here when you ran umbrel-dev boot?

[lukechilds]

I can access your Umbrel fine over it's Tor address:

I wonder if maybe Vagrant is returning the wrong IP somehow? You're using the VirtualBox provider on Linux, right? If you view the VM in the VirtualBox UI does it show the same IP or a different one?

@nevets963 any ideas?

Edit: Oops beat me to it haha.

[Christewart]

If possible, could you dump the logs from the boot process here when you ran umbrel-dev boot?

When the VM booted, did it prompt you about using a bridge?

yes

If so, did you select a network interface?

yes

If possible, could you dump the logs from the boot process here when you ran umbrel-dev boot?

 chris@chris-Precision-7920-Tower  ~/dev/umbrel-dev  umbrel-dev boot                                                                                                               ✔  10963  09:46:11
Bringing machine 'umbrel-dev' up with 'virtualbox' provider...
==> umbrel-dev: Checking if box 'debian/buster64' version '10.20210829.1' is up to date...
==> umbrel-dev: A newer version of the box 'debian/buster64' for provider 'virtualbox' is
==> umbrel-dev: available! You currently have version '10.20210829.1'. The latest is version
==> umbrel-dev: '10.20211018.1'. Run `vagrant box update` to update.
==> umbrel-dev: Clearing any previously set forwarded ports...
==> umbrel-dev: Clearing any previously set network interfaces...
==> umbrel-dev: Specific bridge 'en0: Wi-Fi' not found. You may be asked to specify
==> umbrel-dev: which network to bridge to.
==> umbrel-dev: Available bridged network interfaces:
1) wlp3s0
2) enp2s0
3) enp0s31f6
4) br-cad8f6569fc2
5) br-fa728eb0c65c
6) br-2195333f07a6
7) br-a904681e28ab
8) docker0
==> umbrel-dev: When choosing an interface, it is usually the one that is
==> umbrel-dev: being used to connect to the internet.
==> umbrel-dev:
    umbrel-dev: Which interface should the network bridge to? 1
==> umbrel-dev: Preparing network interfaces based on configuration...
    umbrel-dev: Adapter 1: nat
    umbrel-dev: Adapter 2: bridged
    umbrel-dev: Adapter 3: hostonly
==> umbrel-dev: Forwarding ports...
    umbrel-dev: 22 (guest) => 2222 (host) (adapter 1)
==> umbrel-dev: Running 'pre-boot' VM customizations...
==> umbrel-dev: Booting VM...
==> umbrel-dev: Waiting for machine to boot. This may take a few minutes...
    umbrel-dev: SSH address: 127.0.0.1:2222
    umbrel-dev: SSH username: vagrant
    umbrel-dev: SSH auth method: private key
    umbrel-dev: Warning: Connection reset. Retrying...
==> umbrel-dev: Machine booted and ready!
==> umbrel-dev: Checking for guest additions in VM...
    umbrel-dev: The guest additions on this VM do not match the installed version of
    umbrel-dev: VirtualBox! In most cases this is fine, but in rare cases it can
    umbrel-dev: prevent things such as shared folders from working properly. If you see
    umbrel-dev: shared folder errors, please make sure the guest additions within the
    umbrel-dev: virtual machine match the version of VirtualBox you have installed on
    umbrel-dev: your host and reload your VM.
    umbrel-dev:
    umbrel-dev: Guest Additions Version: 5.2.0 r68940
    umbrel-dev: VirtualBox Version: 6.1
==> umbrel-dev: Setting hostname...
==> umbrel-dev: Configuring and enabling network interfaces...
==> umbrel-dev: Exporting NFS shared folders...
==> umbrel-dev: Preparing to edit /etc/exports. Administrator privileges will be required...
[sudo] password for chris:
==> umbrel-dev: Mounting NFS shared folders...
==> umbrel-dev: Checking for bindfs in VM...
    umbrel-dev: Package manager detected: apt-get
    umbrel-dev: Fuse kernel module is installed
==> umbrel-dev: Fuse kernel module seems to be not loaded on the virtual machine, loading now
    umbrel-dev: Fuse kernel module is loaded
    umbrel-dev: Bindfs 1.13.10 is installed
==> umbrel-dev: Machine is ready to use bindfs!
==> umbrel-dev: Creating bind mounts after synced_folders...
    umbrel-dev: All content in '/vagrant' as been removed before mount
    umbrel-dev: /code => /vagrant
==> umbrel-dev: Machine already provisioned. Run `vagrant provision` or use the `--provision`
==> umbrel-dev: flag to force provisioning. Provisioners marked to run always will still run.
==> umbrel-dev: Running provisioner: shell...
    umbrel-dev: Running: inline script
    umbrel-dev: Skipping status update when not on Umbrel OS
    umbrel-dev:
    umbrel-dev: ======================================
    umbrel-dev: ============= STARTING ===============
    umbrel-dev: ============== UMBREL ================
    umbrel-dev: ======================================
    umbrel-dev:
    umbrel-dev: Setting environment variables...
    umbrel-dev:
    umbrel-dev: Starting karen...
    umbrel-dev:
    umbrel-dev: Starting status monitors...
    umbrel-dev: Starting memory monitor...
    umbrel-dev:
    umbrel-dev: Starting backup monitor...
    umbrel-dev:
    umbrel-dev: Starting decoy backup trigger...
    umbrel-dev:
    umbrel-dev:
    umbrel-dev: Starting Docker services...
    umbrel-dev:
    umbrel-dev: Creating network "umbrel_main_network" with the default driver
    umbrel-dev: Building dashboard
    umbrel-dev: Sending build context to Docker daemon  2.395MB
    umbrel-dev: Step 1/9 : FROM node:12-buster-slim
    umbrel-dev:  ---> 44f66a685237
    umbrel-dev: Step 2/9 : WORKDIR /app
    umbrel-dev:  ---> Using cache
    umbrel-dev:  ---> e309ce4d137b
    umbrel-dev: Step 3/9 : ENV CHOKIDAR_USEPOLLING=true
    umbrel-dev:  ---> Using cache
    umbrel-dev:  ---> 654752bcbca5
    umbrel-dev: Step 4/9 : ENV CHOKIDAR_INTERVAL=1000
    umbrel-dev:  ---> Using cache
    umbrel-dev:  ---> d88076db8210
    umbrel-dev: Step 5/9 : ENV VUE_APP_MIDDLEWARE_API_URL=/api
    umbrel-dev:  ---> Using cache
    umbrel-dev:  ---> e7411303dd04
    umbrel-dev: Step 6/9 : ENV VUE_APP_MANAGER_API_URL=/manager-api
    umbrel-dev:  ---> Using cache
    umbrel-dev:  ---> f2efa12d3211
    umbrel-dev: Step 7/9 : EXPOSE 3004
    umbrel-dev:  ---> Using cache
    umbrel-dev:  ---> 6f53d502033f
    umbrel-dev: Step 8/9 : ENTRYPOINT ["bash"]
    umbrel-dev:  ---> Using cache
    umbrel-dev:  ---> e7ab5ff21f10
    umbrel-dev: Step 9/9 : CMD ["-c", "yarn && yarn vue-cli-service serve --port 3004 --skip-plugins eslint"]
    umbrel-dev:  ---> Using cache
    umbrel-dev:  ---> 24b3dc2d785f
    umbrel-dev: Successfully built 24b3dc2d785f
    umbrel-dev: Successfully tagged getumbrel/dashboard:latest
    umbrel-dev: Building manager
    umbrel-dev: Sending build context to Docker daemon  440.8kB
    umbrel-dev: Step 1/11 : FROM node:12-buster-slim as umbrel-manager-builder
    umbrel-dev:  ---> 44f66a685237
    umbrel-dev: Step 2/11 : RUN apt-get update && apt-get install -y build-essential libffi-dev libssl-dev python3
    umbrel-dev:  ---> Using cache
    umbrel-dev:  ---> 241c9f464e3d
    umbrel-dev: Step 3/11 : WORKDIR /app
    umbrel-dev:  ---> Using cache
    umbrel-dev:  ---> 44b005127062
    umbrel-dev: Step 4/11 : COPY yarn.lock package.json ./
    umbrel-dev:  ---> Using cache
    umbrel-dev:  ---> 0b8ed0f062f5
    umbrel-dev: Step 5/11 : RUN yarn install --production
    umbrel-dev:  ---> Using cache
    umbrel-dev:  ---> b848c579398f
    umbrel-dev: Step 6/11 : COPY . .
    umbrel-dev:  ---> Using cache
    umbrel-dev:  ---> 51ea50b7348a
    umbrel-dev: Step 7/11 : FROM node:12-buster-slim AS umbrel-manager
    umbrel-dev:  ---> 44f66a685237
    umbrel-dev: Step 8/11 : COPY --from=umbrel-manager-builder /app /app
    umbrel-dev:  ---> Using cache
    umbrel-dev:  ---> b15b82018fde
    umbrel-dev: Step 9/11 : WORKDIR /app
    umbrel-dev:  ---> Using cache
    umbrel-dev:  ---> cdf89841d2a0
    umbrel-dev: Step 10/11 : EXPOSE 3006
    umbrel-dev:  ---> Using cache
    umbrel-dev:  ---> f52cbe6a126c
    umbrel-dev: Step 11/11 : CMD [ "yarn", "start" ]
    umbrel-dev:  ---> Using cache
    umbrel-dev:  ---> f4a365979281
    umbrel-dev: Successfully built f4a365979281
    umbrel-dev: Successfully tagged getumbrel/manager:latest
    umbrel-dev: Building middleware
    umbrel-dev: Sending build context to Docker daemon  374.3kB
    umbrel-dev: Step 1/10 : FROM node:12-buster-slim AS umbrel-middleware-builder
    umbrel-dev:  ---> 44f66a685237
    umbrel-dev: Step 2/10 : WORKDIR /app
    umbrel-dev:  ---> Using cache
    umbrel-dev:  ---> e309ce4d137b
    umbrel-dev: Step 3/10 : COPY yarn.lock package.json ./
    umbrel-dev:  ---> Using cache
    umbrel-dev:  ---> f5f34974dbb3
    umbrel-dev: Step 4/10 : RUN yarn install --production
    umbrel-dev:  ---> Using cache
    umbrel-dev:  ---> 2d982fe7cae4
    umbrel-dev: Step 5/10 : COPY . .
    umbrel-dev:  ---> Using cache
    umbrel-dev:  ---> f306525e8580
    umbrel-dev: Step 6/10 : FROM node:12-buster-slim AS umbrel-middleware
    umbrel-dev:  ---> 44f66a685237
    umbrel-dev: Step 7/10 : COPY --from=umbrel-middleware-builder /app /app
    umbrel-dev:  ---> Using cache
    umbrel-dev:  ---> c30b305d45bc
    umbrel-dev: Step 8/10 : WORKDIR /app
    umbrel-dev:  ---> Using cache
    umbrel-dev:  ---> 3933312cc2cc
    umbrel-dev: Step 9/10 : EXPOSE 3006
    umbrel-dev:  ---> Using cache
    umbrel-dev:  ---> 90bd4425409d
    umbrel-dev: Step 10/10 : CMD [ "yarn", "start" ]
    umbrel-dev:  ---> Using cache
    umbrel-dev:  ---> d2fd50b9843c
    umbrel-dev: Successfully built d2fd50b9843c
    umbrel-dev: Successfully tagged getumbrel/middleware:latest
    umbrel-dev: Creating umbrel_tor_server_1 ...
    umbrel-dev: Creating electrs             ...
    umbrel-dev: Creating tor                 ...
    umbrel-dev: Creating dashboard           ...
    umbrel-dev: Creating dashboard           ... done
    umbrel-dev: Creating electrs             ... done
    umbrel-dev: Creating umbrel_tor_server_1 ... done
    umbrel-dev: Creating tor                 ... done
    umbrel-dev: Creating manager             ...
    umbrel-dev: Creating manager             ... done
    umbrel-dev: Creating lnd                 ...
    umbrel-dev: Creating nginx               ...
    umbrel-dev: Creating lnd                 ... done
    umbrel-dev: Creating nginx               ... done
    umbrel-dev: Creating bitcoin             ...
    umbrel-dev: Creating bitcoin             ... done
    umbrel-dev: Creating neutrino-switcher   ...
    umbrel-dev: Creating middleware          ...
    umbrel-dev: Creating neutrino-switcher   ... done
    umbrel-dev: Creating middleware          ... done
    umbrel-dev:
    umbrel-dev: Removing status server iptables entry...
    umbrel-dev: Exiting iptables setup when not on Umbrel OS
    umbrel-dev:
    umbrel-dev: Starting installed apps...
    umbrel-dev:
    umbrel-dev:
    umbrel-dev: Umbrel is now accessible at
    umbrel-dev:   http://umbrel-dev.local
    umbrel-dev:   http://10.0.2.15
    umbrel-dev:   http://b7zljreor54i3fyaekxvuwdoetsruk4bvjdrirfgfj43gd4xtpa5g2yd.onion
    umbrel-dev: Skipping status update when not on Umbrel OS

==> umbrel-dev: Machine 'umbrel-dev' has a post `vagrant up` message. This is a message
==> umbrel-dev: from the creator of the Vagrantfile, and not from Vagrant itself:
==> umbrel-dev:
==> umbrel-dev:               ,;###GGGGGGGGGGl#Sp
==> umbrel-dev:            ,##GGGlW""^'  '`""%GGGG#S,
==> umbrel-dev:          ,#GGG"                  "lGG#o
==> umbrel-dev:         #GGl^                      '$GG#
==> umbrel-dev:       ,#GGb                          GGG,
==> umbrel-dev:       lGG"                            "GGG
==> umbrel-dev:      #GGGlGGGl##p,,p##lGGl##p,,p###ll##GGGG
==> umbrel-dev:     !GGGlW"""*GGGGGGG#""""WlGGGGG#W""*WGGGGS
==> umbrel-dev:      ""          "^          '"          ""
==> umbrel-dev:
==> umbrel-dev:
==> umbrel-dev:                 @GGS         lG#
==> umbrel-dev:                 !GGG        !GGG
==> umbrel-dev:                 !GGG        !GGG
==> umbrel-dev:                 !GGG        !GGG
==> umbrel-dev:                 !GGG        !GGG
==> umbrel-dev:                 !GGG        !GGG
==> umbrel-dev:                 'GGG        $GGl
==> umbrel-dev:                  "GGG#psqp##GG#
==> umbrel-dev:                    "%GGGGGG#"
==> umbrel-dev:
==> umbrel-dev: Umbrel development environment ready: http://umbrel-dev.local

[nevets963]

Hmm, maybe the interface wlp3s0 is connectd to a network that is similar to a 10.x.x.x network. and it's confused how to get to the VM. Can you see if you can access the dev VM at: http://192.168.56.56 ?

[Christewart]

http://192.168.56.56

This does work

[j-5-s]

I'm also seeing this issue. however i dont get the same response from umbrel-dev run "cat tor/data/web/hostname":

➜  umbrel-dev umbrel-dev run "cat tor/data/web/hostname"
cat: tor/data/web/hostname: No such file or directory
Connection to 127.0.0.1 closed.

I do get a successful response from umbrel-dev run "curl http://localhost":

➜  umbrel-dev umbrel-dev run "curl http://localhost"
<!DOCTYPE html>
<html lang="en">

<head>
  <title>Umbrel</title>
  <meta charset="utf-8">
  <meta http-equiv="X-UA-Compatible" content="IE=edge">
  <meta name="viewport" content="width=device-width,initial-scale=1.0">
  <meta name="robots" content="noindex, nofollow" />
  <meta name="referrer" content="no-referrer" />
  <link rel="icon" href="/favicon.png">
  <meta name="description" content="Welcome back">
<link href="/js/app.js" rel="preload" as="script"><link href="/js/chunk-vendors.js" rel="preload" as="script"></head>

<body>
  <noscript>
    <strong>We're sorry but Umbrel
      doesn't work properly without JavaScript enabled. Please enable it to
      continue.</strong>
  </noscript>
  <div id="app"></div>
  <!-- built files will be auto injected -->
<script type="text/javascript" src="/js/chunk-vendors.js"></script><script type="text/javascript" src="/js/app.js"></script></body>

</html>Connection to 127.0.0.1 closed.

http://umbre-dev.local returns a 502 from nginx

And http://192.168.56.56/ does work (although really slow - about a minute of waiting) however after interacting with it it eventually throws a different error that I created a new issue for:

Failed to compile.

./node_modules/css-loader/dist/runtime/api.js
Module build failed: Error: ENOENT: no such file or directory, open '/app/node_modules/css-loader/dist/runtime/api.js'

[j-5-s]

Also, although access directly through the IP works, is it on the roadmap to fix http://umbrel-dev.local? I'd like to have a working dev environment as close to prod as possible to tinker around with things.