Search results

I tried this on a different server through the shell only and I used the password version. I initially had the same problem. Connection refused. I tried again without the password, and same connection refused. I tried a third time with a different port and no password and now it's working...

So I tried it through the shell instead of through the web interface, and it seems it's working now, sort of. I can connect, I just can't authenticate. I always get authentication failed in all the clients I've tried. Setting the password again doesn't seem to make a difference. I figure I'll...

I used 0.0.0.0:100 and I also tried :20 and :77 instead of :100. They all gave the same response. I used the IP of the proxmox server and the port to connect. So proxmoxip:5600 or :5920, or :5977. I tried the IP:port combinations on the built in vnc client on my Mac as well as VNC Viewer and...

I followed the instructions on this page, https://pve.proxmox.com/wiki/VNC_Client_Access, but whenever I try and connect from an external client I get connection refused. This happens multiple clients. I haven't enabled any sort of firewall features and I am connecting from the local subnet. Is...

I still have this issue from time to time. So far I have no idea what triggers it. It doesn't always happen on the same VM either. I have 4 VMs on my server and as far as I can tell, it never happens on the first vm or the last vm in the backups. It's always either the second or the third. One...

I'm also seeing the same type of error and it's happen on multiple of my VMs, but only one at a time. 102 ucs FAILED 00:00:07 no such volume 'local-lvm:vm-102-disk-1' So far I've just run the backup manually after the scheduled backup fails for one of the VMs and it's worked fine. I've...

Well, I figured out what the issue was. I made sure to be near the server with terminals open to all my VMs and Proxmox watching top and logs. Thought the updates had fixed it once 9am rolled around, but about 6 minutes later everything stopped and I heard a beep, but it didn't sound like the...

I am on the latest kernel now. I also updated to the latest bios on the motherboard just in case something in the newer kernel was interacting oddly with the previous bios. This is on a Ryzen CPU so there's been some growing pains with those so maybe that will help as well. If not maybe I'll try...

Yes, I checked the system log(s) and looked for kernel dumps, but I couldn't find anything. Also started to setup kdump-tools, but I couldn't figure out after googling around for a bit how it's supposed to interact with systemd. I'm going to try hunting down more info on getting a kernel dump...

I'm trying to figure out why my server reboots itself between 8am-9am every Monday. I've tried looking through all the cron jobs and backups to see if I could find anything scheduled around that time and so far I've come up empty. The logs I've looked at don't turn up anything that doesn't...

I have added a USB 3 Realtek 8153 adapter to my system to get a second ethernet port to test with on my home server. While the adapter works well with Proxmox/Debian 9 itself, performance in a container or VM is quite slow comparatively. I can SCP a file to the Proxmox OS at about 115MB/s...

I have two servers, both with 2 drives, 1 SSD and 1 Spinning disk. Right now I have them setup with VMs and containers running on the SSDs and the HDDs used for backups. This works fine for our needs as it's mostly stuff for our office running on them and a hour or so of downtime during...

I've modified the systemd config file so the watchdog timeout is 10 seconds. That seems to limit the delay to about 10 seconds, so I'm going to use that as a work around for now.

I'm also having this issue on my new v5 installs. Is there any solution/workaround for this yet? It really adds a significant delay to reboots.

I'm not sure why you think I'm calling the netboot functionality and the pulling of the IP on boot the glitch. I think what I wrote is pretty clear that I now think that part is normal. The glitch was after the first install I could not get an IP change to work. I tried changing the interfaces...

So it turns out that this server supports net booting with no os installed and the EFI is by default pulling an IP. I loaded the latest EFI update and it still does that so I think it's normal. Now why the IP set for Proxmox/Debian would not work after the machine booted I don't know. I think...

Interesting. This server had ESXi on it previously. Maybe it tweaked something in the EFI that is pulling an IP. I'll have to play around with it some more and see what happens. For now I have it set to static and also have a static lease for the same IP setup for it in the router. Seems to boot...

So I reloaded and setup the work IP during the install. I added that subnet to my home router and it does work on that IP now. The weird thing is I still see the lease created in the router at the grub screen even though I did not setup dhcp anywhere. Once the server is up I cannot ping the...

So after a little more playing around, it seems that the server is pulling it's IP at the grub boot screen. I looked through the grub config file but there's not much there. At this point I think I may just reinstall from scratch to see what happens if I set up a static during the initial install.

I setup a new Proxmox 5 install on my home network with DHCP. After verifying I could log in to the web interface and ran updates I set the IP to static shutdown the server and took it to work. At work I logged into the ip that was on the home network updated it to match the work network and...