Search results

Once the hang occurs, if I reboot I get back into a hung state very quickly. Usually I cannot boot. If I clean power cycle (power off and then back on) I usually don't crash for a few weeks. Are you suggesting that once I get into this bad state, reboot into a live CD? I just ran a scrub and it...

Thank you so much for your help. I'm not sure what you mean. I don't think I'll be able to reproduce the problem in a live CD. My machine usually only hangs after ~2 weeks of real usage. Are you referring to nvme-cli? What specific command would you like me to run? Here's list and smart-log...

Hey Stoiko, I agree something sounds broken, but the only part that hasn't changed is the motherboard and I'm not sure how to diagnose that further. > try gathering the output of `dmesg` before the error is reached Any idea how I can do that if the drive itself is becoming not writable? Can I...

Hey All, I can't seem to get a stable Proxmox server. This was my last post on the subject. I got sick of fiddling with one or two variables and then waiting 2 weeks to see if it would hang, so I went ahead and changed almost everything in the system. I upgraded from Proxmox 5.4 to 6, I swapped...

WOW I just created a new container to check the answer to your question and it worked perfectly and I can login. The only change I've made to Proxmox is activating a subscription and reverting my apt sources back to stock. I haven't even rebooted. I'm not sure what to say. FWIW on this working...

Bumping just once (now that I've purchased a subscription). I hope that's okay :)

Bumping just once (now that I've purchased a subscription). I hope that's okay :)

Yeah which is definitely straightforwardly that it is connecting via ssh to the host (somehow). There's no accidental container escape or anything, heh.

That's an excellent question and I don't know the answer. I was just trying to help you get VSCode connected to your container. Since VSCode *did* connect to the host, though, something about your config isn't setup the way you think it is.

You're assuming I'm being loose in my instructions and not doing exactly what I said. If you want to fix your problem do EXACTLY this: Change your ssh config to have the "Host" value be "container" instead of "container.domain.it" Make sure the port is correct to connect to the container Make...

I honestly don’t understand your setup or question, but nothing should be connecting to the host. VSCode should ssh into the container, and if you can’t ssh directly into the container from the command line VSCode isn’t going to connect either. Get command line ssh to the *container* working...

Don’t use the domain/ip as the “Host” in your ssh config. Use an alias like “container”. Then make it so that `ssh container` works and connects to your container and NOT your host. This will require fixing the port forwarding or whatever is incorrect about your setup. Don’t touch VSCode until...

VSCode is connecting to your host and not the container. Your domain name or port forwarding isn't setup right. If VSCode were connecting to the container it wouldn't be able to touch the host and install the remote development server. What happens when you `ssh container.domain.it`? What...

If I open either a noVNC or xterm.js shell to the Proxmox host or container the shell will eventually, within a couple of minutes, time out. By time out I mean there is no visible error but the window stops accepting input and is hung. This ONLY occurs on Firefox. On Chrome I can leave the shell...

Since upgrading to Proxmox 6 I can no longer login to new containers I have just created (although older containers I created using Proxmox 5.4 continue to work). I am performing these steps: Create CT Input hostname "login-test" Provide a password "faceface1" and confirm the same Don't enter...

This is not the right forum to be asking VSCode specific questions unrelated to Proxmox, but I can probably guess what your issue is: make sure you use the Remote-SSH extension to connect over SSH to the container. Then everything will be installed on the container. You surely provided the...

In the Proxmox 6 release notes I noticed this line: This sounds really cool and I'd like to try it. I'm assuming this makes use of ZFS snapshots and should be really efficient at incrementally backing up? The only problem is that my ZFS pool isn't listed in the dialog: Here's my...

Interesting. Do you have the M11SDV-8C-LN4F? If so the bios was just released 6/13 so if you have 40 days of uptime you definitely don't have the update :) Either way it doesn't matter if your issue is fixed. I'm glad to hear it! I'll report back when I have more uptime (or don't).

PSA: SuperMicro released a bios update (R 1.0a) for this board and I've got 11 days of uptime without a crash, so I think the bios update may have fixed the problem. The update comes with no information so I have no clue if they even intended to address such an issue, but I'm hopeful this was an...

I went ~two weeks without this hang and it just happened again. Interestingly, my containers and VMs are running fine. I just can't access the Proxmox web GUI or ssh into the host. Local console is also hung. Anyone have any ideas how I might go about diagnosing this problem WHILE the machine is...