avoid using HTTP_PROXY environment variable
People run into problems on upgrades, for example: export http_proxy=http://172.xxx.xxx.xxx:8888/ aptitude update && aptitude full-upgrade This restarts pveproxy, and after that login was no longer possible. Another way to reproduce the bug is: http_proxy=http://1.2.3.4:8888/ pveproxy --debug
Showing
Please register or sign in to comment