Proxmox 3.2 ISO Post-installation no webinterface

[Paddy972]

Hi evrybody.

I have a hp elite 7500 core i7 with 8Go and 2 PCI/E Ethernet card with 2 DD ( 500go and 1To )
I would like to install the Proxmox VE 3.2 ISO 3.2-5a885216-5 on this machine.
So,
i make the installation with linux ext4.
i am behind a proxy.
configure the repo with No-Subscription Repository
enabled my http_proxy var.
$>aptitude update
$>aptitude full-upgrade
the update is performed without error
$>reboot

And i can't connect with my browser on it.
the ping work.
when i do a nmap i have "All 1000 scanned ports on 172.16.0.5 are closed"

Can you help me.
Regards
screenshot:
https://drive.google.com/file/d/0B-PiS3LAO_vXNHlscVQxaFlsZm8/edit?usp=sharing
https://drive.google.com/file/d/0B-PiS3LAO_vXUlVBcl9MVDB1bzQ/edit?usp=sharing

 

[Mr.Holmes]

Hello Paddy972

i make the installation with linux ext4.

Which installation option did you specify in detail?

i am behind a proxy.

But you can access directly to the console!?

configure the repo with No-Subscription Repository

enabled my http_proxy var.
$>aptitude update
$>aptitude full-upgrade
the update is performed without error
$>reboot

Dis you check after plain installation if web and ssh is working fine?

And i can't connect with my browser on it.
the ping work.
when i do a nmap i have "All 1000 scanned ports on 172.16.0.5 are closed"

Note that port for web is 8006 and not scanned if you don´t specify any option in nmap (only first 1000 ports scanned).

However, ssh port 22 should work - if not somewhere a firewall blocks access from your current client.
As seen in the pictures you have direct access to console, so check with

netstat -a | grep 8006

directly on the console if the respective port is open

- if yes, check where the access is blocked - but it should work if connect your client directly with proxmox host

- if no, I would install proxmox again and try it out before upgrade.

Kind regards

Mr.Holmes

 

[Paddy972]

Hello thanks for your answer.
Q: Which installation option did you specify in detail?
A: boot : linux ext4

Q: But you can access directly to the console!?
A:
Yes i can just access to the console
I just add in /etc/profil the varaible http_proxy and https_proxy
like http_proxy="http://proxy.sss.mq:8080/"
export http_proxy.
And i create a 40proxy file to my /etc/apt.conf.d/

Q: Dis you check after plain installation if web and ssh is working fine?
A: Yes i try before update . web and ssh don't work.

I do the netstat -a
it's empty..
no port open

I do all before update. nothing change.

 

[Mr.Holmes]

A: boot : linux ext4

.....

I just add in /etc/profil the varaible http_proxy and https_proxy
like http_proxy="http://proxy.sss.mq:8080/"
export http_proxy.
And i create a 40proxy file to my /etc/apt.conf.d/

And if you try to install without all these adaptions? I can hardly imagine that it will not work in that case - if really not you have probably a problem in your hardware (I have installed at least 50 times that version - never saw any problems like this).

 

[Paddy972]

Vmware Esxi work.
but i prefer the project of proxmox. :-(
I try as well with no adaptions, no success .
So ... i don't know why a linux distribution work and not proxmox.
Install debian and after upgrade to proxmox don't work too.

 

[Mr.Holmes]

Hello Paddy972

Vmware Esxi work.
but i prefer the project of proxmox. :-(

I agree - proxmox has a lot of advantages in daily usage as kvm and openvz available, basic OS is a real linux, nu huge client GUI necessary etc.

i don't know why a linux distribution work and not proxmox.
Install debian and after upgrade to proxmox don't work too.

I don´t either - and cannot imagine too.

It seems to me there is something in your HW which proxmox "doesn´t like" Did you try with a different HW?

Seems to be a problem with network interface ....

What I would try:

Connect the server to a local network and make some experiments with network connections, e.g. try if outgoing traffic works, then activate services listening to ports (typical is sshd, but you wrote it does not work), trying if an incoming connection to it is possible, if not: does it work with localhost? etc...


All the best

Mr.Holmes