well, I wouldn't know, but 1.7G definitely doesn't sound like a lot. I am at the point where I am wondering if it wouldn't just be easier to back up all my VM's to a USB from within the shell (SDD1 is already a mounted USB) and reinstall proxmox fresh, no clue if that could work or would be easier than just finding the issue.
[SOLVED] can't access proxmox web GUI
- Thread starter StamPoints
- Start date
-
- Tags
- nowebgui
You should anyway always have full & restorable backups of all your VMs & LXCs. I very much hope you have these. External drive looks like a good choice especially considering a re-install.
As far as re-installing goes - I can't really advise you if this is necessary for your situation.
You need to examine your system & specifically what changes have you made to the system - that may have caused your issue. What changed from the last time you successfully accessed the WebGUI to this time? Etc. When/what updates have been committed?
Maybe provide output for
As far as re-installing goes - I can't really advise you if this is necessary for your situation.
You need to examine your system & specifically what changes have you made to the system - that may have caused your issue. What changed from the last time you successfully accessed the WebGUI to this time? Etc. When/what updates have been committed?
Maybe provide output for
pveversion -v (post the output in the code-editor, available on the formatting-bar in this reply box. Press the </> key & paste the output).well my main M.2 is mirrored to another M.2 so I was considering that as my backup, and i hadn't really done any changes the last time I was on proxmox, as most of what I was doing is working in the VM's on my AI , and I think I had set my widows VM to auto start on boot, that is all I had changed
also the result of pveversion -v
also the result of pveversion -v
If you're running any kind of production workloads, I would strongly suggest at least just basic (vzduump) backups of your VM's/containers, since as you are experiencing, issues on the main storage just mirror over to the other storage - creating a tough spot if things go sideways. - Re-install may be an option, but it's going to be much more work. Might check "journalctl -f" for any errors related to pveproxy to see why it won't respond to curl requests. Some more things to try to troubleshoot over in this thread you might try: https://forum.proxmox.com/threads/cannot-access-web-interface.103240/
FYI
That is NOT a backup - any data/incorrect data on one will be mirrored on the other.
Your version appears a mixed-bag? Assuming you are non-enterprise you do not appear to have the latest kernel, although some packages appear almost up to date? Have you ever fully updated/upgraded the whole system? Are your repos correctly configured?
Show output for:
Code:
cat /etc/apt/sources.list
# and this
cat /etc/apt/sources.list.d/ceph.list
# PLEASE POST OUTPUT IN CODE-EDITOR - LIKE THIS OUTPUT IS - AS SHOWN ABOVE!!!
okay will post it in the code editor .
I am not sure if everything is up to data, I only made this server in the last month and just a week ago this issue started, i haven't got everything set up the way I want it yet as I am still new to it all and learning.
this server is for my self and will be a shared storage with database for my dad's company once it is all done.
I will most likely have better backups in future like having the USB to back up things on it and off site backup to a micro system like a Lenovo ThinkCentre.
as for the result of what you asked for :
I am not sure if everything is up to data, I only made this server in the last month and just a week ago this issue started, i haven't got everything set up the way I want it yet as I am still new to it all and learning.
this server is for my self and will be a shared storage with database for my dad's company once it is all done.
I will most likely have better backups in future like having the USB to back up things on it and off site backup to a micro system like a Lenovo ThinkCentre.
as for the result of what you asked for :
Code:
root@StamPointsRecords:~# cat /etc/apt/sources.list
# and this
cat /etc/apt/sources.list.d/ceph.list
deb http://ftp.uk.debian.org/debian bookworm main contrib
deb http://ftp.uk.debian.org/debian bookworm-updates main contrib
# security updates
deb http://security.debian.org bookworm-security main contrib
deb https://enterprise.proxmox.com/debian/ceph-quincy bookworm enterprise
root@StamPointsRecords:~#i think i found the problem with journalctl -f, it just keeps going :
Code:
root@StamPointsRecords:~# journalctl -f
Feb 09 15:51:05 StamPointsRecords pveproxy[400574]: worker exit
Feb 09 15:51:05 StamPointsRecords pveproxy[2160]: worker 400574 finished
Feb 09 15:51:05 StamPointsRecords pveproxy[2160]: starting 1 worker(s)
Feb 09 15:51:05 StamPointsRecords pveproxy[2160]: worker 400596 started
Feb 09 15:51:05 StamPointsRecords pveproxy[400596]: unable to open log file '/var/log/pveproxy/access.log' - Permission denied
Feb 09 15:51:08 StamPointsRecords spiceproxy[400589]: worker exit
Feb 09 15:51:08 StamPointsRecords spiceproxy[2167]: worker 400589 finished
Feb 09 15:51:08 StamPointsRecords spiceproxy[2167]: starting 1 worker(s)
Feb 09 15:51:08 StamPointsRecords spiceproxy[2167]: worker 400613 started
Feb 09 15:51:08 StamPointsRecords spiceproxy[400613]: unable to open log file '/var/log/pveproxy/access.log' - Permission denied
Feb 09 15:51:10 StamPointsRecords pveproxy[400595]: worker exit
Feb 09 15:51:10 StamPointsRecords pveproxy[400594]: worker exit
Feb 09 15:51:10 StamPointsRecords pveproxy[2160]: worker 400595 finished
Feb 09 15:51:10 StamPointsRecords pveproxy[2160]: starting 1 worker(s)
Feb 09 15:51:10 StamPointsRecords pveproxy[2160]: worker 400594 finished
Feb 09 15:51:10 StamPointsRecords pveproxy[2160]: worker 400643 started
Feb 09 15:51:10 StamPointsRecords pveproxy[400643]: unable to open log file '/var/log/pveproxy/access.log' - Permission denied
Feb 09 15:51:10 StamPointsRecords pveproxy[400596]: worker exit
Feb 09 15:51:10 StamPointsRecords pveproxy[2160]: worker 400596 finished
Feb 09 15:51:10 StamPointsRecords pveproxy[2160]: starting 2 worker(s)
Feb 09 15:51:10 StamPointsRecords pveproxy[2160]: worker 400644 started
Feb 09 15:51:10 StamPointsRecords pveproxy[2160]: worker 400645 started
Feb 09 15:51:10 StamPointsRecords pveproxy[400645]: unable to open log file '/var/log/pveproxy/access.log' - Permission denied
Feb 09 15:51:10 StamPointsRecords pveproxy[400644]: unable to open log file '/var/log/pveproxy/access.log' - Permission denied
Feb 09 15:51:13 StamPointsRecords spiceproxy[400613]: worker exit
Feb 09 15:51:13 StamPointsRecords spiceproxy[2167]: worker 400613 finished
Feb 09 15:51:13 StamPointsRecords spiceproxy[2167]: starting 1 worker(s)
Feb 09 15:51:13 StamPointsRecords spiceproxy[2167]: worker 400670 started
Feb 09 15:51:13 StamPointsRecords spiceproxy[400670]: unable to open log file '/var/log/pveproxy/access.log' - Permission denied
Feb 09 15:51:15 StamPointsRecords pveproxy[400643]: worker exit
Feb 09 15:51:15 StamPointsRecords pveproxy[2160]: worker 400643 finished
Feb 09 15:51:15 StamPointsRecords pveproxy[2160]: starting 1 worker(s)
Feb 09 15:51:15 StamPointsRecords pveproxy[2160]: worker 400672 started
Feb 09 15:51:15 StamPointsRecords pveproxy[400672]: unable to open log file '/var/log/pveproxy/access.log' - Permission denied
Feb 09 15:51:15 StamPointsRecords pveproxy[400645]: worker exit
Feb 09 15:51:15 StamPointsRecords pveproxy[400644]: worker exit
Feb 09 15:51:15 StamPointsRecords pveproxy[2160]: worker 400645 finished
Feb 09 15:51:15 StamPointsRecords pveproxy[2160]: starting 1 worker(s)
Feb 09 15:51:15 StamPointsRecords pveproxy[2160]: worker 400673 started
Feb 09 15:51:15 StamPointsRecords pveproxy[2160]: worker 400644 finished
Feb 09 15:51:15 StamPointsRecords pveproxy[2160]: starting 1 worker(s)
Feb 09 15:51:15 StamPointsRecords pveproxy[2160]: worker 400674 started
Feb 09 15:51:15 StamPointsRecords pveproxy[400674]: unable to open log file '/var/log/pveproxy/access.log' - Permission denied
Feb 09 15:51:15 StamPointsRecords pveproxy[400673]: unable to open log file '/var/log/pveproxy/access.log' - Permission denied
Feb 09 15:51:18 StamPointsRecords spiceproxy[400670]: worker exit
Feb 09 15:51:18 StamPointsRecords spiceproxy[2167]: worker 400670 finished
Feb 09 15:51:18 StamPointsRecords spiceproxy[2167]: starting 1 worker(s)
Feb 09 15:51:18 StamPointsRecords spiceproxy[2167]: worker 400687 started
Feb 09 15:51:18 StamPointsRecords spiceproxy[400687]: unable to open log file '/var/log/pveproxy/access.log' - Permission denied
Feb 09 15:51:20 StamPointsRecords pveproxy[400672]: worker exit
Feb 09 15:51:20 StamPointsRecords pveproxy[2160]: worker 400672 finished
Feb 09 15:51:20 StamPointsRecords pveproxy[2160]: starting 1 worker(s)
Feb 09 15:51:20 StamPointsRecords pveproxy[2160]: worker 400716 started
Feb 09 15:51:20 StamPointsRecords pveproxy[400716]: unable to open log file '/var/log/pveproxy/access.log' - Permission denied
Feb 09 15:51:20 StamPointsRecords pveproxy[400674]: worker exit
Feb 09 15:51:20 StamPointsRecords pveproxy[400673]: worker exit
Feb 09 15:51:20 StamPointsRecords pveproxy[2160]: worker 400674 finished
Feb 09 15:51:20 StamPointsRecords pveproxy[2160]: starting 1 worker(s)
Feb 09 15:51:20 StamPointsRecords pveproxy[2160]: worker 400673 finished
Feb 09 15:51:20 StamPointsRecords pveproxy[2160]: worker 400717 started
Feb 09 15:51:20 StamPointsRecords pveproxy[400717]: unable to open log file '/var/log/pveproxy/access.log' - Permission denied
Feb 09 15:51:23 StamPointsRecords spiceproxy[400687]: worker exit
Feb 09 15:51:23 StamPointsRecords spiceproxy[2167]: worker 400687 finished
Feb 09 15:51:23 StamPointsRecords spiceproxy[2167]: starting 1 worker(s)
Feb 09 15:51:23 StamPointsRecords spiceproxy[2167]: worker 400729 started
Feb 09 15:51:23 StamPointsRecords spiceproxy[400729]: unable to open log file '/var/log/pveproxy/access.log' - Permission denied
Feb 09 15:51:25 StamPointsRecords pveproxy[400716]: worker exit
Feb 09 15:51:25 StamPointsRecords pveproxy[2160]: worker 400716 finished
Feb 09 15:51:25 StamPointsRecords pveproxy[2160]: starting 2 worker(s)
Feb 09 15:51:25 StamPointsRecords pveproxy[2160]: worker 400733 started
Feb 09 15:51:25 StamPointsRecords pveproxy[2160]: worker 400734 started
Feb 09 15:51:25 StamPointsRecords pveproxy[400733]: unable to open log file '/var/log/pveproxy/access.log' - Permission denied
Feb 09 15:51:25 StamPointsRecords pveproxy[400734]: unable to open log file '/var/log/pveproxy/access.log' - Permission denied
Feb 09 15:51:25 StamPointsRecords pveproxy[400717]: worker exit
Feb 09 15:51:25 StamPointsRecords pveproxy[2160]: worker 400717 finished
Feb 09 15:51:25 StamPointsRecords pveproxy[2160]: starting 1 worker(s)
Feb 09 15:51:25 StamPointsRecords pveproxy[2160]: worker 400735 started
Feb 09 15:51:25 StamPointsRecords pveproxy[400735]: unable to open log file '/var/log/pveproxy/access.log' - Permission denied
Feb 09 15:51:28 StamPointsRecords spiceproxy[400729]: worker exit
Feb 09 15:51:28 StamPointsRecords spiceproxy[2167]: worker 400729 finished
Feb 09 15:51:28 StamPointsRecords spiceproxy[2167]: starting 1 worker(s)
Feb 09 15:51:28 StamPointsRecords spiceproxy[2167]: worker 400755 started
Feb 09 15:51:28 StamPointsRecords spiceproxy[400755]: unable to open log file '/var/log/pveproxy/access.log' - Permission deniedyeah i rebooted the server a several times trying to get it to work, and last time was probably yesterday
the results are :
the results are :
Code:
root@StamPointsRecords:~# cat /etc/apt/sources.list.d/pve-enterprise.list
# and this one:
cat /etc/apt/sources.list.d/pve-install-repo.list
deb https://enterprise.proxmox.com/debian/pve bookworm pve-enterprise
cat: /etc/apt/sources.list.d/pve-install-repo.list: No such file or directory
root@StamPointsRecords:~#Do you have a subscription?
IF YOU HAVE A PROXMOX SUBSCRIPTION IGNORE ALL OF THE FOLLOWING!
If you do not you need to edit the following:
Then you should complete an upgrade with
After this you should probably reboot the server - as you will have a kernel update.
IF YOU HAVE A PROXMOX SUBSCRIPTION IGNORE ALL OF THE FOLLOWING!
If you do not you need to edit the following:
Code:
nano /etc/apt/sources.list.d/pve-install-repo.list
# Paste the following:
deb http://download.proxmox.com/debian/pve bookworm pve-no-subscription
# ctrl+x to save & then exitThen you should complete an upgrade with
apt-get update & when that completes, enter apt-get dist-upgrade .After this you should probably reboot the server - as you will have a kernel update.
okay that is done :
Code:
root@StamPointsRecords:~# apt-get update
Ign:1 http://ftp.uk.debian.org/debian bookworm InRelease
Ign:2 http://security.debian.org bookworm-security InRelease
Ign:3 https://enterprise.proxmox.com/debian/ceph-quincy bookworm InRelease
Ign:4 http://download.proxmox.com/debian/pve bookworm InRelease
Ign:5 http://ftp.uk.debian.org/debian bookworm-updates InRelease
Ign:6 https://enterprise.proxmox.com/debian/pve bookworm InRelease
Ign:1 http://ftp.uk.debian.org/debian bookworm InRelease
Ign:2 http://security.debian.org bookworm-security InRelease
Ign:3 https://enterprise.proxmox.com/debian/ceph-quincy bookworm InRelease
Ign:4 http://download.proxmox.com/debian/pve bookworm InRelease
Ign:5 http://ftp.uk.debian.org/debian bookworm-updates InRelease
Ign:6 https://enterprise.proxmox.com/debian/pve bookworm InRelease
Ign:1 http://ftp.uk.debian.org/debian bookworm InRelease
Ign:2 http://security.debian.org bookworm-security InRelease
Ign:4 http://download.proxmox.com/debian/pve bookworm InRelease
Ign:3 https://enterprise.proxmox.com/debian/ceph-quincy bookworm InRelease
Ign:5 http://ftp.uk.debian.org/debian bookworm-updates InRelease
Ign:6 https://enterprise.proxmox.com/debian/pve bookworm InRelease
Err:4 http://download.proxmox.com/debian/pve bookworm InRelease
Temporary failure resolving 'download.proxmox.com'
Err:1 http://ftp.uk.debian.org/debian bookworm InRelease
Temporary failure resolving 'ftp.uk.debian.org'
Err:2 http://security.debian.org bookworm-security InRelease
Temporary failure resolving 'security.debian.org'
Err:3 https://enterprise.proxmox.com/debian/ceph-quincy bookworm InRelease
Temporary failure resolving 'enterprise.proxmox.com'
Err:5 http://ftp.uk.debian.org/debian bookworm-updates InRelease
Temporary failure resolving 'ftp.uk.debian.org'
Err:6 https://enterprise.proxmox.com/debian/pve bookworm InRelease
Temporary failure resolving 'enterprise.proxmox.com'
Reading package lists... Done
W: Failed to fetch http://ftp.uk.debian.org/debian/dists/bookworm/InRelease Temporary failure resolving 'ftp.uk.debian.org'
W: Failed to fetch http://ftp.uk.debian.org/debian/dists/bookworm-updates/InRelease Temporary failure resolving 'ftp.uk.debian.org'
W: Failed to fetch http://security.debian.org/dists/bookworm-security/InRelease Temporary failure resolving 'security.debian.org'
W: Failed to fetch https://enterprise.proxmox.com/debian/ceph-quincy/dists/bookworm/InRelease Temporary failure resolving 'enterprise.proxmox.com'
W: Failed to fetch https://enterprise.proxmox.com/debian/pve/dists/bookworm/InRelease Temporary failure resolving 'enterprise.proxmox.com'
W: Failed to fetch http://download.proxmox.com/debian/pve/dists/bookworm/InRelease Temporary failure resolving 'download.proxmox.com'
W: Some index files failed to download. They have been ignored, or old ones used instead.
root@StamPointsRecords:~# apt-get dist-upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.seems you are correct i don't seem to have internet access :
Code:
root@StamPointsRecords:~# ping 1.1.1.1
ping: connect: Network is unreachable
root@StamPointsRecords:~# ping google.com
ping: google.com: Temporary failure in name resolution
root@StamPointsRecords:~#not that i can think of, i can access the sever's shell on my local network and it is plugged straight into the router, even tried changing what port on the router it is plugged into, plus i can still access all the VM and the VM's have internet access
You are going to have to go through the usual suspects.
Lets try some basic testing:
Post output for the following:
1.
2.
3.
4.
5.
Lets try some basic testing:
Post output for the following:
1.
ip a2.
cat /etc/network/interfaces3.
hostname4.
cat /etc/hosts5.
cat /etc/resolv.confWith only the same (single) cable connecting the host to the router?
here are the results for those :
Code:
root@StamPointsRecords:~# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host noprefixroute
valid_lft forever preferred_lft forever
2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master vmbr0 state UP group default qlen 1000
link/ether 08:bf:b8:38:5c:3e brd ff:ff:ff:ff:ff:ff
altname enp4s0
3: eno2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 08:bf:b8:38:5c:3d brd ff:ff:ff:ff:ff:ff
altname enp6s0
4: wlp5s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 00:93:37:a6:12:56 brd ff:ff:ff:ff:ff:ff
5: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 08:bf:b8:38:5c:3e brd ff:ff:ff:ff:ff:ff
inet 192.168.0.64/24 scope global vmbr0
valid_lft forever preferred_lft forever
inet6 fe80::abf:b8ff:fe38:5c3e/64 scope link
valid_lft forever preferred_lft forever
6: tap100i0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master fwbr100i0 state UNKNOWN group default qlen 1000
link/ether 7e:d7:22:d8:d1:98 brd ff:ff:ff:ff:ff:ff
7: fwbr100i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 0a:19:95:26:a7:cc brd ff:ff:ff:ff:ff:ff
8: fwpr100p0@fwln100i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr0 state UP group default qlen 1000
link/ether c2:6d:22:a4:c7:c9 brd ff:ff:ff:ff:ff:ff
9: fwln100i0@fwpr100p0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr100i0 state UP group default qlen 1000
link/ether 0a:19:95:26:a7:cc brd ff:ff:ff:ff:ff:ff
10: tap101i0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master fwbr101i0 state UNKNOWN group default qlen 1000
link/ether ce:89:b7:42:ca:5a brd ff:ff:ff:ff:ff:ff
11: fwbr101i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 06:04:6d:98:12:1e brd ff:ff:ff:ff:ff:ff
12: fwpr101p0@fwln101i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr0 state UP group default qlen 1000
link/ether 5e:89:3e:19:3c:ed brd ff:ff:ff:ff:ff:ff
13: fwln101i0@fwpr101p0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr101i0 state UP group default qlen 1000
link/ether 06:04:6d:98:12:1e brd ff:ff:ff:ff:ff:ff
14: tap102i0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master fwbr102i0 state UNKNOWN group default qlen 1000
link/ether 16:91:11:47:64:72 brd ff:ff:ff:ff:ff:ff
15: fwbr102i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 6a:56:64:14:c7:ba brd ff:ff:ff:ff:ff:ff
16: fwpr102p0@fwln102i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr0 state UP group default qlen 1000
link/ether 4e:6d:df:d0:d0:7a brd ff:ff:ff:ff:ff:ff
17: fwln102i0@fwpr102p0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr102i0 state UP group default qlen 1000
link/ether 6a:56:64:14:c7:ba brd ff:ff:ff:ff:ff:ff
18: tap103i0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master fwbr103i0 state UNKNOWN group default qlen 1000
link/ether 1e:6f:59:e8:1e:91 brd ff:ff:ff:ff:ff:ff
19: fwbr103i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 7a:10:3e:9f:d8:fa brd ff:ff:ff:ff:ff:ff
20: fwpr103p0@fwln103i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr0 state UP group default qlen 1000
link/ether 0e:aa:aa:fe:f6:bf brd ff:ff:ff:ff:ff:ff
21: fwln103i0@fwpr103p0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr103i0 state UP group default qlen 1000
link/ether 7a:10:3e:9f:d8:fa brd ff:ff:ff:ff:ff:ff
22: tap104i0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master fwbr104i0 state UNKNOWN group default qlen 1000
link/ether a6:76:e2:02:56:bf brd ff:ff:ff:ff:ff:ff
23: fwbr104i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether f2:11:ba:e2:bb:92 brd ff:ff:ff:ff:ff:ff
24: fwpr104p0@fwln104i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr0 state UP group default qlen 1000
link/ether 02:b3:a7:05:f8:7e brd ff:ff:ff:ff:ff:ff
25: fwln104i0@fwpr104p0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr104i0 state UP group default qlen 1000
link/ether f2:11:ba:e2:bb:92 brd ff:ff:ff:ff:ff:ff
26: tap111i0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master fwbr111i0 state UNKNOWN group default qlen 1000
link/ether 5a:d9:f7:06:6c:26 brd ff:ff:ff:ff:ff:ff
27: fwbr111i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 5e:ab:a9:04:e0:04 brd ff:ff:ff:ff:ff:ff
28: fwpr111p0@fwln111i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr0 state UP group default qlen 1000
link/ether 2e:3f:a0:05:1f:4a brd ff:ff:ff:ff:ff:ff
29: fwln111i0@fwpr111p0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr111i0 state UP group default qlen 1000
link/ether 5e:ab:a9:04:e0:04 brd ff:ff:ff:ff:ff:ff
root@StamPointsRecords:~# cat /etc/network/interfaces
auto lo
iface lo inet loopback
iface eno1 inet manual
auto vmbr0
iface vmbr0 inet static
address 192.168.0.64/24
gateway 192.168.0.64
bridge-ports eno1
bridge-stp off
bridge-fd 0
iface eno2 inet manual
iface wlp0s20f3 inet manual
source /etc/network/interfaces.d/*
root@StamPointsRecords:~# hostname
StamPointsRecords
root@StamPointsRecords:~# cat /etc/hosts
127.0.0.1 localhost.localdomain localhost
192.168.0.64 StamPointsRecords.server StamPointsRecords
# The following lines are desirable for IPv6 capable hosts
::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts
root@StamPointsRecords:~# cat /etc/resolv.conf
search .
nameserver 192.168.0.64
root@StamPointsRecords:~#Assuming that
192.168.0.64 is the correct gateway of your router, you need to choose a different address for the Proxmox host, so maybe check what is available & edit that line to the desired address so you will have:
Code:
address 192.168.0.xxx/24 #replacing 'xxx' with the desired address
gateway 192.168.0.64Here again replace that address (underlined) with the one above for the Host's address so
192.168.0.xxxChange that line (underlined) to
search localGood luck.