Page no longer load after creating first Instance

Hi, i am new with lxd and created a ubuntu server install on a dedicated server from ovh and followed this as per terminal. i tried with my ovh ubutnu@ with sudo su but as it was throwing same issue. i tried with enabling root login. same issue. the root/ssh login also stop working.

The issue appears after creating first instance, i was creating 24.04 instance, it shows created but then page stop loading. Setting Page is accessible.

as shared page no longer load after creating first Instance · Issue #1027 · canonical/lxd-ui · GitHub

ip is changed in this code. i don’t know what i am doing is wrong here and can give root access of fresh install to check. Thanks.

root@ns551443:~# snap version
snap    2.66.1+24.04
snapd   2.66.1+24.04
series  16
ubuntu  24.04
kernel  6.8.0-49-generic
root@ns551443:~# sudo snap install lxd
2024-12-13T04:51:12Z INFO Waiting for automatic snapd restart...
lxd (5.21/stable) 5.21.2-084c8c8 from Canonical✓ installed
root@ns551443:~# getent group lxd | grep "$USER"
root@ns551443:~# sudo usermod -aG lxd "$USER"
newgrp lxd
root@ns551443:~# getent group lxd | grep "$USER"
lxd:x:105:ubuntu,root
root@ns551443:~# lxd init
permanently dropping privs did not work: File exists
root@ns551443:~# sudo lxd init
Would you like to use LXD clustering? (yes/no) [default=no]: yes
What IP address or DNS name should be used to reach this server? [default=142.44.420.420]: 
Are you joining an existing cluster? (yes/no) [default=no]: 
What member name should be used to identify this server in the cluster? [default=ns551443]: 
Do you want to configure a new local storage pool? (yes/no) [default=yes]: 
Name of the storage backend to use (dir, lvm, zfs, btrfs) [default=zfs]: 
Create a new ZFS pool? (yes/no) [default=yes]: 
Would you like to use an existing empty block device (e.g. a disk or partition)? (yes/no) [default=no]: 
Size in GiB of the new loop device (1GiB minimum) [default=30GiB]: 64GiB
Do you want to configure a new remote storage pool? (yes/no) [default=no]: 
Would you like to connect to a MAAS server? (yes/no) [default=no]: 
Would you like to configure LXD to use an existing bridge or host interface? (yes/no) [default=no]: 
Would you like to create a new Fan overlay network? (yes/no) [default=yes]: 
What subnet should be used as the Fan underlay? [default=auto]: 
Would you like stale cached images to be updated automatically? (yes/no) [default=yes]: 
Would you like a YAML "lxd init" preseed to be printed? (yes/no) [default=no]: yes
config:
  core.https_address: 142.44.420.420:8443
networks:
- config:
    bridge.mode: fan
    fan.underlay_subnet: auto
  description: ""
  name: lxdfan0
  type: ""
  project: default
storage_pools:
- config:
    size: 64GiB
  description: ""
  name: local
  driver: zfs
storage_volumes: []
profiles:
- config: {}
  description: ""
  devices:
    eth0:
      name: eth0
      network: lxdfan0
      type: nic
    root:
      path: /
      pool: local
      type: disk
  name: default
projects: []
cluster:
  server_name: ns551443
  enabled: true
  member_config: []
  cluster_address: ""
  cluster_certificate: ""
  server_address: ""
  cluster_password: ""
  cluster_token: ""
  cluster_certificate_path: ""

root@ns551443:~# lxc config set core.https_address :8443
permanently dropping privs did not work: File exists
root@ns551443:~# sudo lxc config set core.https_address :8443
To start your first container, try: lxc launch ubuntu:24.04
Or for a virtual machine: lxc launch ubuntu:24.04 --vm

root@ns551443:~# sudo lxc config trust add lxd-ui-142.44.420.420.crt
root@ns551443:~# sudo lxc config trust list
+--------+---------------------------+---------------+--------------+------------------------------+------------------------------+
|  TYPE  |           NAME            |  COMMON NAME  | FINGERPRINT  |          ISSUE DATE          |         EXPIRY DATE          |
+--------+---------------------------+---------------+--------------+------------------------------+------------------------------+
| client | lxd-ui-142.44.420.420.crt |               | 1cb97e86f566 | Dec 13, 2024 at 2:40am (UTC) | Sep 9, 2027 at 2:40am (UTC)  |
+--------+---------------------------+---------------+--------------+------------------------------+------------------------------+
| server | ns551443                  | root@ns551443 | 25ee657d6d73 | Dec 13, 2024 at 4:52am (UTC) | Dec 11, 2034 at 4:52am (UTC) |
+--------+---------------------------+---------------+--------------+------------------------------+------------------------------+
root@ns551443:~# 

Hi! Are there any news on this topic?

If not and you are still facing this problem, could you please share the steps you took for your set up so we can try to reproduce it on our end?

During the holidays the activity here tends to slow down, we appreciate the patience :slight_smile:

1 Like

Hi Pedro, unfortunately, i failed to make it work.

I followed the steps mentioned above in the code in fresh dedicated metal server with ubuntu 24.04 install.

If you have time, i can share a dedicated server login that you can use to test it and record all the process? or can have a video call if relative options are available this way.

I would really appreciate all the help with this. I will make sure to not take a lot of time.

Thanks.

Hi! The forum has been quite unresponsive lately and I have been struggling to get this answer across, sorry about that :confused:

can have a video call if relative options are available this way

Sure, we can do one. But in the meantime I took some time to try and reproduce the problem on my end, but without success so far.

So I am now wondering:

  • Can you interact with LXD normally through the CLI?
  • I saw you were getting some 500 errors on the GitHub issue, could you show more information on those? You should be able to get some useful information using journalctl --quiet --no-hostname --no-pager --boot=0 --lines=200 --unit=snap.lxd.daemon.service just after getting said errors.
1 Like

hi @pedro-rib , i totally understand the late reply.

the server become unresponsive and then it just stop login with ssh root so can’t do anything after that.

let me know if you have time and how we can get on a zoom call.

Thanks.

we can schedule something for tomorrow after 5PM (GMT +0) if that works for you.

okay setting a reminder to message you between 5PM-5:30PM GMT +0 tomorrow.

send you a message so we can connect.

Hi, could you do now? If so just send a link and I will join

1 Like

check dm, i have sent the zoom link

seems like the issue was not exposing the port and i have not used this command

sudo lxc config set core.https_address :8443

strange the web ui was available by default without running this command.

it is working after exposing via above command.

1 Like