-
Dietmar Maurer authored
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
907c5316
| Name |
Last commit
|
Last update |
|---|---|---|
| PVE | ||
| aplinfo | ||
| bin | ||
| debian | ||
| po | ||
| www | ||
| .gitignore | ||
| Makefile | ||
| README | ||
| copyright | ||
| country.pl | ||
| defines.mk | ||
| repoid.pl | ||
| vzdump-hook-script.pl | ||
| vzdump.conf | ||
| vznet.conf |