Unable to access the GUI after changing the Ip address

[Brian Read]

I changed the Ip address and the hostname entry and re-booted.

Now I get a "refused to connect" when I try to get at the gui. ssh works to the new ip.

I switched the ip address back and it worked.

I presume there must be an extra step required...

 

[grmg2010]

Hello,

what steps did you took to change the IP and hostname?

 

[Brian Read]

Initially I used the gui to edit /etc/networks/interfaces:

auto vmbr0
iface vmbr0 inet static
    address 192.168.100.98/24
    gateway 192.168.100.4
    bridge-ports eno1
    bridge-stp off
    bridge-fd 0

and the /etc/hosts:

127.0.0.1 localhost.localdomain localhost
192.168.100.98 pve.bjsystems.co.uk pve

to switch back I just edited the files.

 

[oguz]

hi,

please take a look here [0].

I presume there must be an extra step required...

check your /etc/hosts file and the output of hostname --ip-address, you should be seeing the new IP address as a result of this command.

if your machine is clustered you'll also need to edit the corosync conf (see wiki link)

hope this helps

[0]: https://pve.proxmox.com/wiki/Renaming_a_PVE_node

 

[Brian Read]

root@pve:~# hostname --ip-address
192.168.100.98
root@pve:~#

Machine is not clustered.

 

[oguz]

okay.

are you connecting like https://192.168.100.98:8006 to the GUI?

do you see any error messages in journalctl -r?

is the pveproxy service running? ss -antlp | grep pveproxy

 

[Brian Read]

root@pve:~# ss -antlp | grep pveproxy
LISTEN 0      4096                *:8006             *:*    users:(("pveproxy worker",pid=5376,fd=6),("pveproxy worker",pid=5375,fd=6),("pveproxy worker",pid=5374,fd=6),("pveproxy",pid=5373,fd=6))
root@pve:~#

This what I get from Chromium:

This site can’t be reached
192.168.100.98 refused to connect

Can confirm the URL is correct.

Nothing that I can see in the journal.

 

[Brian Read]

Is there an issue with the self signed certificate?

Or perhaps with apparmour?

 

[oguz]

* do you have firewall activated for the node or the datacenter? if yes please check the firewall rules.

Is there an issue with the self signed certificate?

Or perhaps with apparmour?

normally should be fine, unless there are errors related to that?

This what I get from Chromium:

This site can’t be reached
192.168.100.98 refused to connect

Can confirm the URL is correct.

what if you run curl https://127.0.0.1:8006 -s -k | grep title on your PVE host? do you see the page title?

also try with the other IP address (192.168.100.98) as well.

Nothing that I can see in the journal.

you can still post it here. run:journalctl -b0 > journal.txt and paste/upload the journal.txt file

 

[Brian Read]

No firewall rules that I've put in.

root@pve:~# curl https://127.0.0.1:8006 -s -k | grep title
    <title>pve - Proxmox Virtual Environment</title>
root@pve:~# curl https://192.168.100.98:8006 -s -k | grep title
    <title>pve - Proxmox Virtual Environment</title>
root@pve:~#

and from my desktop:

[brianr@bjr-fedora ~]$ curl https://192.168.100.98:8006 -s -k | grep title
    <title>pve - Proxmox Virtual Environment</title>
[brianr@bjr-fedora ~]$

Which makes me think it might be a browser problem.

Firefox still refuses to connect, but Chromium now works (but gives me "Not Secure"). I had tried CHromium before a number of times (I have re-booted the desktop since then probably).

Am attaching the journal.

 

[Brian Read]

I am getting from CHromium that the Certificate is not valid. Will the (self signed) contents depend on the Ip address?

How do I re-generate it?

It is showing the old Ip address in the "Certificate Subject Alternative Name" field.

 

[oguz]

Chromium now works (but gives me "Not Secure").

the "not secure" is normal if you're using a self-signed certificate.

Will the (self signed) contents depend on the Ip address?

How do I re-generate it?

It is showing the old Ip address in the "Certificate Subject Alternative Name" field.

yes, try running pvecm updatecerts --force

Firefox still refuses to connect

are you putting https:// in front?

Am attaching the journal.

besides some kernel call traces related to iommu, i don't see anything that should be problematic (at least should not be relevant).

 

[Brian Read]

yes to the https.

Have re-generated the certificate, but Chromium still shows the old Ip address and the original certificate generated date. <update> now seeing new date in Chromium after CTRL-F5.

root@pve:~# pvecm updatecerts --force
(re)generate node files
generate new node certificate
merge authorized SSH keys and known hosts
root@pve:~#

Firefox still just gives me a blank page.

 

[oguz]

but Chromium still shows the old Ip address and the original certificate generated date

you can try to do systemctl restart pvedaemon pveproxy

 

[Brian Read]

See above - Chromium ok now, but Firefox still not showing anything, even after restarting pvedaemon and pveproxy.

Confirmed Firefox has new Certificate.

 

[oguz]

See above - Chromium ok now, but Firefox still not showing anything, even after restarting pvedaemon and pveproxy.

Confirmed Firefox has new Certificate.

if it's working then you can mark the thread as [SOLVED]

 

[Brian Read]

Well its still not working for Firefox.

Have tried Brave and Edge, and they also work (but they are based on Chrome).

 

[Brian Read]

I could probably pick up a cert from letsencrypt - do you think that might help?

 

[oguz]

Well its still not working for Firefox.

which version of firefox? and which OS?

are you receiving a certificate error?

I could probably pick up a cert from letsencrypt - do you think that might help?

if you have a domain name it's worth a shot, but i'm not so sure if it'll solve the underlying issue

still take a look here for certificate management [0]

[0]: https://pve.proxmox.com/pve-docs/pve-admin-guide.html#sysadmin_certs_get_trusted_acme_cert

 

[Brian Read]

firefox v100.0 Fedora 36 with Cinnamon.

No error from firefox, after going through the "insecure" dialog, it just gives me a blank screen.