Problem: web interface not working when installing with options 'linux maxroot'

[ronpeled]

I'm installing the latest proxox (3.1) on a clean server. When I install it as-is there are no issues and the web interface is working once the install process is done and I reboot. However, when I set special parameters 'linux maxroot=20' it goes through the installation successfully but the web interface does not work. Pointing the browser to it will bring a Error code: ERR_EMPTY_RESPONSE message.

Login in via SSH and running the command:

pveproxy --debug
unable to create socket - IO::Socket::INET: Address already in use

How can this be resolved? or am I stuck with default root partition?

Thank you!

 

[tom]

a bit late, but did you manage it already?

if not, post the output of:

> cat /proc/mounts

and

> pveversion -v

 

[ronpeled]

This issue still exists. I was able to trace it better. It relates to SSL certificates and browsers caching it. So, I'm no expert on SSL and how browsers use it but whenever I reinstalled Proxmox - it essentially created new SSL certificates. So when I visit the site again <ip address>:8006 the browser shows a window with an error message:
No data received

if you click the 'More' button (in chrome) you see: Unable to load the webpage because the server sent no data.Error code: ERR_EMPTY_RESPONSE

Initially I thought it was only Chrome but it affects any browser. Clearing the cache and history does not fix the issue.

 

[chrism]

I know this is an old thread and was probably solved ages ago, but I had almost exactly the same problem and google brought me here. I've now fixed it and thought it might help others if I shared.

The problem I found is because of cookies, not SSL certificates. Proxmox uses a cookie called PVEAuthCookie, which is fundamental to the secure connection to Proxmox. I found that Chrome had an old version of this relating to my previous Proxmox installation. Deleting this cookie solved the problem.

For Chrome users there are two ways to find and delete this cookie:
1) Click on the padlock to the left of "https:" in the address bar, in the popup select the "Persmissions" tab, then click on "Show cookies and site data". In the new popup expand the arrow for your Proxmox server address (ie 192.168.1.11 for me) and then the Cookies folder. You should see a PVEAuthCookie cookie which you can select to show the date and then Remove if necessary.
2) Settings, Show Advanced Settings, Privacy/Content Settings..., in popup Cookies/All cookies and site data..., then select your Proxmox server address in the list on the left, or search for it. Click on the cross on the right to remove cookies.

 

[JustaGuy]

I know this is an old thread and was probably solved ages ago, but I had almost exactly the same problem and google brought me here. I've now fixed it and thought it might help others if I shared.

The problem I found is because of cookies, not SSL certificates. Proxmox uses a cookie called PVEAuthCookie, which is fundamental to the secure connection to Proxmox. I found that Chrome had an old version of this relating to my previous Proxmox installation. Deleting this cookie solved the problem.

For Chrome users there are two ways to find and delete this cookie:
1) Click on the padlock to the left of "https:" in the address bar, in the popup select the "Persmissions" tab, then click on "Show cookies and site data". In the new popup expand the arrow for your Proxmox server address (ie 192.168.1.11 for me) and then the Cookies folder. You should see a PVEAuthCookie cookie which you can select to show the date and then Remove if necessary.
2) Settings, Show Advanced Settings, Privacy/Content Settings..., in popup Cookies/All cookies and site data..., then select your Proxmox server address in the list on the left, or search for it. Click on the cross on the right to remove cookies.

Thank you _SO_ much for posting this. Apparently when I 'Clear browsing data', even selecting 'cookies', in Chrome, it didn't remove that cookie you mentioned. Manually deleting it solved my problem. Huge relief!

 

[daemonizer]

I know this is an old thread and was probably solved ages ago, but I had almost exactly the same problem and google brought me here. I've now fixed it and thought it might help others if I shared.

The problem I found is because of cookies, not SSL certificates. Proxmox uses a cookie called PVEAuthCookie, which is fundamental to the secure connection to Proxmox. I found that Chrome had an old version of this relating to my previous Proxmox installation. Deleting this cookie solved the problem.

For Chrome users there are two ways to find and delete this cookie:
1) Click on the padlock to the left of "https:" in the address bar, in the popup select the "Persmissions" tab, then click on "Show cookies and site data". In the new popup expand the arrow for your Proxmox server address (ie 192.168.1.11 for me) and then the Cookies folder. You should see a PVEAuthCookie cookie which you can select to show the date and then Remove if necessary.
2) Settings, Show Advanced Settings, Privacy/Content Settings..., in popup Cookies/All cookies and site data..., then select your Proxmox server address in the list on the left, or search for it. Click on the cross on the right to remove cookies.

Kudos ChrisM, such a stupid little thing ... you bailed me out.

 

[Logan_Rocks]

im getting the same issue:https://gyazo.com/a87009046cb798f575b6eb1a3ec84850

 

[dcsapak]

im getting the same issue:https://gyazo.com/a87009046cb798f575b6eb1a3ec84850

your screenshot shows you are not connecting with https

try:
https://xxxxx:8006/

and you might want to censor your domain on the image

 

[Logan_Rocks]

Its getting the same error when i do https. ill delete that screen sho tthanks for letting me know.

 

[dcsapak]

try another browser or delete the cache, and check if the time is correct

 

[Logan_Rocks]

I can connect via the https://ip:port but not the domain version

 

[Logan_Rocks]

nvm browser clearing worked. Thanks for your help dcsapak!!