Search results

  1. M

    GET /api2/json: 401 Unauthorized

    Hey Sterzy, I was looking through dev tools a bit. I have it happening sporadically in brave as well. One thing I noticed is that the first three attempts worked and the fourth and beyond hung. If I look in network tab, and filter by socket, I see an additional websocket connection each time...
  2. M

    Can you change smartctl parameters?

    I see these errors in the log for all my drives: (This is a really old hp dl360 g7 with a drive controller that's probably not ideal) Aug 28 18:34:24 pbs proxmox-backup-api[1420]: failed to gather smart data for /dev/sda – command "smartctl" "-H" "-A" "-j" "/dev/sda" failed - status code: 1 -...
  3. M

    GET /api2/json: 401 Unauthorized

    I tried it again from home tonight. Cleared cache. Brave browser works fine. Chrome fails. I'm ditching chrome so I'm okay with the results but I can't help but think there's something strange with this install. I may blow it away and start over anyway.
  4. M

    GET /api2/json: 401 Unauthorized

    Well this is interesting. I just tried accessing it from my laptop while on my work guest network through tailscale and it worked immediately. I'm further confused. I'll do some more testing.
  5. M

    GET /api2/json: 401 Unauthorized

    Yeah I cleared cookies and app cache. Definitely rebooted several times. Those logs above are from journal. Dev tools essentially showed the same error. I think I should probably just do a fresh pbs install. I thought about maybe trying to reinstall the pbs packages in place too. It's an odd...
  6. M

    GET /api2/json: 401 Unauthorized

    After the 4.x upgrade, I can't connect to the web interface from the browser. SSH is working fine. I see this in the logs for each attempt. Aug 25 21:40:24 pbs proxmox-backup-proxy[1465]: authentication failure; rhost=[::1]:36534 msg=no authentication credentials provided. Aug 25 21:40:27 pbs...
  7. M

    [Feature Request] Allow the configuration of the host shell background color.

    To make it easily distinguishable in putty I set a custom background color for the host but I can't do it through the web-ui. Just an extra layer of, "Hey dummy, you're on the host right now!" for those of us getting old enough to need that extra reminder.
  8. M

    Proxmox VE install fails

    Installing Debian and then PVE seems to be the quickest way to get past this issue. Are there any differences between the installs if you do it that way? I assume debian has a different default package list than what PVE installs? It's a bummer this is still going on after all this time.
  9. M

    Proxmox 3.4 "Out of Range" at install

    Same problem here. DL360 g7. Debian works fine. I tried the enter trick without any luck. Graphical and console have the same issue. Tried a 1024x768 monitor and a 1920x1080 monitor.
  10. M

    LXC Debian 10 to 11 => systemd failure

    Just tried it again with your 3 lines. Repeatable. I think these might be my problem but I don't understand what they are. Setting up systemd (247.3-6) ... Detected unsafe path transition /var/log -> /var/log/journal during canonicalization of /var/log/journal. Detected unsafe path transition...
  11. M

    LXC Debian 10 to 11 => systemd failure

    @Moayad I'm just going to setup a new container on debian 11 and migrate the configs.
  12. M

    Using Proxmox as NAS for different VMs + Windows Clients

    I have a couple of windows computers accessing it as well as sonos without issue. (Sonos did need a little extra config because they only support an older version of samba protocol) I haven't really tried accessing it from another linux container but I don't expect there would be any problem.
  13. M

    Using Proxmox as NAS for different VMs + Windows Clients

    I have one container with all my media on it that also runs samba and plex.
  14. M

    LXC Debian 10 to 11 => systemd failure

    Yes, I'm showing what they are before I started the upgrade. I changed them to bullseye prior to starting within the LXC. (If I hadn't it would have just upgraded buster to the latest packages)
  15. M

    LXC Debian 10 to 11 => systemd failure

    No, I had swapped them all to bullseye prior to the upgrade. deb http://deb.debian.org/debian bullseye main deb-src http://deb.debian.org/debian bullseye main deb https://deb.debian.org/debian-security bullseye-security main contrib deb-src https://deb.debian.org/debian-security...
  16. M

    LXC Debian 10 to 11 => systemd failure

    Thanks for taking a look. Here are the items you requested. root@pve:~# pveversion -v proxmox-ve: 7.1-1 (running kernel: 5.13.19-3-pve) pve-manager: 7.1-10 (running version: 7.1-10/6ddebafe) pve-kernel-helper: 7.1-10 pve-kernel-5.13: 7.1-7 pve-kernel-5.11: 7.0-10 pve-kernel-5.13.19-4-pve...
  17. M

    Newbie: Trying to setup Proxmox VE 7.1 on Ryzen system

    You should see PVE under datacenter I believe. Are you using an app or the web interface? If you're using an app, maybe try the web interface from the tablet or a PC. https://<proxmox ip>:8006/
  18. M

    Fresh Install Of 7.1 Disk Is Showing 100 percent utilization

    I think the 100% usage part is normal. Mine looks the same. Go under datacenter -> Summary and what does it show for storage?
  19. M

    LXC Debian 10 to 11 => systemd failure

    Switched apt/sources.list and apt/source.list.d from buster to bullseye and did apt update && apt full-upgrade and I end with a systemd failure. Only thing really installed is wireguard. Created symlink /etc/systemd/system/sysinit.target.wants/systemd-pstore.service ->...