Can not connect to web interface

BobMann

New Member
Mar 31, 2014
4
0
1
I recently installed Proxmox to my test server (a Dell Poweredge 2950) to try it out and see if it would work as a replacement for Virtualbox. I was having issues burning it to a USB and a CD so I followed this tutorial
http://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Wheezy
I get an "unable to connect" error in Firefox when trying to access the web interface.
I have only ever used Ubuntu before so I am new to Debian.
Any help would be appreciated.
 
I recently installed Proxmox to my test server (a Dell Poweredge 2950) to try it out and see if it would work as a replacement for Virtualbox. I was having issues burning it to a USB and a CD so I followed this tutorial
http://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Wheezy
I get an "unable to connect" error in Firefox when trying to access the web interface.
I have only ever used Ubuntu before so I am new to Debian.
Any help would be appreciated.
Hi,
and you use to connect an URL like "https://ip.of.pve.server:8006" ?!
Can you ping your pvehost "ping ip.of.pve.server" ?

Udo
 
Bump? I really need help to get this working or I am going to have to go back to Virtualbox.
 
What I would do in such a case:


- try to connect to PROXMOX server via ssh

* if not ok, connect a terminal and log in directly on the server

- check with

netstat -l | grep 8006

whether webservice is running correctly

result shoud be

tcp 0 0 *:8006 *:* LISTEN

* if not ok: something wrong after PROXMOX installation

* if ok try

wget --no-check-certificate https://localhost:8006

result should be

--2014-04-xx xx:xx:xx-- https://localhost:8006/
Resolving localhost (localhost)... 127.0.0.1
Connecting to localhost (localhost)|127.0.0.1|:8006... connected.


etc.

- if ok: probably a problem with your client - but no idea what it can be, try another one.

- if not ok: something wrong after PROXMOX installation

In case of wrong PROXMOX installation: I would reapeat ist, simply. Be careful to fill out the forms
during installation proces for IP addresses etc. correctly. My experience is: if you do so
there are no problems to connect to web interface.

Best regards

Mr. Holmes
 
  • Like
Reactions: fodorj
The error was "failed: connection refused."

The port isn't open!
Verify with nmap (and netstat like Mr.Holmes wrote):
Code:
nmap -p 8006 ip.of.pve.server

Starting Nmap 6.40 ( http://nmap.org ) at 2014-04-09 18:13 CEST
Nmap scan report for proxmox.example.org (ip.of.pve.server)
Host is up (0.000076s latency).
PORT     STATE SERVICE
8006/tcp open  unknown

Nmap done: 1 IP address (1 host up) scanned in 0.11 seconds
Udo
 
Last edited:
having same issue, super green to this stuff.
mine says:
Failed to resolve "ip.of.pve.server"
WARNING: no targets were specified, so 0 hosts scanned.
Nmap done: 0 IP addresses (0 host up) scanned in 0.10 seconds..
 
What I would do in such a case:


- try to connect to PROXMOX server via ssh

* if not ok, connect a terminal and log in directly on the server

- check with

netstat -l | grep 8006

whether webservice is running correctly

result shoud be

tcp 0 0 *:8006 *:* LISTEN

* if not ok: something wrong after PROXMOX installation

* if ok try

wget --no-check-certificate https://localhost:8006

result should be

--2014-04-xx xx:xx:xx-- https://localhost:8006/
Resolving localhost (localhost)... 127.0.0.1
Connecting to localhost (localhost)|127.0.0.1|:8006... connected.


etc.

- if ok: probably a problem with your client - but no idea what it can be, try another one.

- if not ok: something wrong after PROXMOX installation

In case of wrong PROXMOX installation: I would reapeat ist, simply. Be careful to fill out the forms
during installation proces for IP addresses etc. correctly. My experience is: if you do so
there are no problems to connect to web interface.

Best regards

Mr. Holmes
I know the thread is old, but I am having the same issue. Everytime I try to connect to my web interface for Proxmox it comes up with

502 Bad Gateway​


nginx/1.18.0

I have tried to run all the commands Mr. Holmes suggested and they all checked out. The only thing that I am not sure about is the certificate message I received below......if that's normal or not?
wget --no-check-certificate https://localhost:8006
--2021-07-24 16:44:51-- https://localhost:8006/
Resolving localhost (localhost)... 127.0.0.1
Connecting to localhost (localhost)|127.0.0.1|:8006... connected.
WARNING: The certificate of ‘localhost’ is not trusted.
WARNING: The certificate of ‘localhost’ doesn't have a known issuer.
HTTP request sent, awaiting response... 200 OK
Length: 2308 (2.3K) [text/html]
Saving to: ‘index.html.1’

index.html.1 100%[===================>] 2.25K --.-KB/s in 0s


So I am not sure what to do next?? I really don't want to reinstall Prox if I don't have to as I have a few VMs that I need to keep running. Any help would be greatly appreciated.

Thanks,
Truckin
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!