Search results

OK, I can access the gui now. It must have been an outdated rule imported on to the firewall, I cleaned up the rule feeds and it is working against. Sorry for wasting your time yet again.

Yes, they are both responding as running. If it is the pfsense then it's only blocking the host, guests are fine.

tcp 0 0 0.0.0.0:sunrpc 0.0.0.0:* listen tcp 0 0 localhost.localdomain:85 0.0.0.0:* listen tcp 0 0 0.0.0.0:ssh 0.0.0.0:* listen tcp 0 0 0.0.0.0:3128...

That was a typo. I CANNOT copy and paste. Anyway, you have the data now. What firewall are you referring to? On the Proxmox? I'm not running a firewall on the proxmox as yet, there is a pfsense in front of this node. netstat data to follow.

proxmox-ve: 5.0-19 running kernla 4:10.17-2-pve pve-manager 5.0-30 running version 5.0-30/5ab26bc pve-kernal-4.10.17-2-pve: 4.10.17-19 pve-kernal-4.10.15-1-pve: 4.10.15-15 libpve-http-server-perl: 2.0-5 lvm2: 2.02.168-pve3 corosync: 2.4.2-pve3 libqb0: 1.0.1-1 pve-cluster: 5.0-12 qemu-server...

By hand? OK, this will take a while.

I'm on the host so I can copy and paste 6 tcp and 3 tcp6 lines, all with 0 for Rev-Q, all 0 for Sen-Q, all foreign addresses listed as 0.0.0.0, 4 local listed as 0.0.0.0 two as localhost.localdomain. state is listen for all. proxmox-ve 5.0-19

We've tried rebooting (twice). Makes no difference.

Our host was working perfectly, we made no changes to it and now for some reason it is reporting all ports closed when we run nmap. Cannot access the GUI or SSH in. Any thoughts?

I have tried a variety of images and I can't get them to come up properly listening on 80. Has any one else encountered this?

This was caused by a router DNS issue. Not Proxmox, apologies for wasting your time.

This is a fresh proxmox 5 install, I made the IPv6 change I mentioned above but that's it. I'll do a clean install again it's in a DMZ behind a pfsense on a 192.168.3.x subnet Can I confirm that on install the gateway and DNS are 3.1?

I tried an ubuntu 16.04 desktop install. It installed, servers can see the internet but it hung after reboot

apologies, that seemed to fix it in dev on our no-sub box but the problem remains on the Prod sub machine including the script failing and the flashing screen. Very odd, I've been running no-sub boxes for a good while now and never seen this.

We found the cause. https://forum.proxmox.com/threads/disable-ipv6.36319/ We have reverted this change and debian installs. We still have the issue of failing to connect to security.debian to deal with though. Any advice on best practise on IPv6 on proxmox

Linux 4.10.17-2-pve #1 SMP PVE 4.10.17-19 KVM debian-9.1.0-amd64-netinst.iso Bridged mode virtIO

It redscreens at detect network hardware, then goes into that script failing with the console flashing white.

Is deploying docker in VMs in production under Proxmox 5 advisable right now? Is there a guide to best practise?

This is happing on a local install.

I'm still seeing this issue after doing this. Not consistently though.