I use a container template for new customer VPS server w/ proxmox, I guess the server IP addresses are checked during a OS update via (imscp scripts) and so I have to change them before running an update or install a image from a container template:
Posts by fulltilt
-
-
Debian 9
imSCP 1.5.3
openssl libssl-dev already patched
I get an nginx installation error while upgrading 1.5.3 to latest imscp-1.5.3-2018120800
Display MoreCode- Processing triggers for systemd (232-25+deb9u6) ...
- Errors were encountered while processing:
- nginx-full
- E: Sub-process /usr/bin/dpkg returned an error code (1)
- invoke-rc.d: initscript nginx, action "start" failed.
- ● nginx.service - A high performance web server and a reverse proxy server
- Loaded: loaded (/lib/systemd/system/nginx.service; enabled; vendor preset: enabled)
- Active: failed (Result: exit-code) since Tue 2018-12-11 14:27:41 CET; 7ms ago
- Docs: man:nginx(8)
- Process: 25679 ExecStartPre=/usr/sbin/nginx -t -q -g daemon on; master_process on; (code=exited, status=1/FAILURE)
- Dec 11 14:27:41 host1 systemd[1]: Starting A high performance web server an…r...
- Dec 11 14:27:41 host1 nginx[25679]: nginx: [emerg] bind() to 138.201.187.21…ess)
- Dec 11 14:27:41 host1 nginx[25679]: nginx: configuration file /etc/nginx/ng…iled
- Dec 11 14:27:41 host1 systemd[1]: nginx.service: Control process exited, co…us=1
- Dec 11 14:27:41 host1 systemd[1]: Failed to start A high performance web se…ver.
- Dec 11 14:27:41 host1 systemd[1]: nginx.service: Unit entered failed state.
- Dec 11 14:27:41 host1 systemd[1]: nginx.service: Failed with result 'exit-code'.
- Hint: Some lines were ellipsized, use -l to show in full.
- dpkg: error processing package nginx-full (--configure):
- subprocess installed post-installation script returned error exit status 1
- Errors were encountered while processing:
- nginx-full
- E: Sub-process /usr/bin/dpkg returned an error code (1)
-
note: if libssl-dev was removed during a previous OS update you should re-install the package
Display MoreCode- nano /etc/apt/preferences.d/imscp
- remove:
- Package: openssl libssl-dev
- Pin: release o=Debian,n=stretch
- Pin-Priority: 1002
- nano /usr/local/src/imscp-1.5.3/autoinstaller/Packages/debian-stretch.xml
- <ssl
- pinning_package="openssl libssl-dev"
- pinning_pin="release o=Debian,n=stretch"
- pinning_pin_priority="1002"
- >
- <package>libssl-dev</package>
- <package>openssl</package>
- </ssl>
- change to:
- <ssl>
- <package>libssl-dev</package>
- <package>openssl</package>
- </ssl>
- apt-get update
- apt-get clean
- apt-get update
- apt-get upgrade
- apt-get install libssl-dev
- apt autoremove
-
Display MoreYes
In current i-MSCP version, there is an uwanted APT pinning on the libssl-dev package, as on the openssl package. You can fix the problem by editing the /etc/apt/preferences.d/imscp file, removing the following stanza:This APT pinning is added by the i-MSCP installer, through distribution packages file. For instance, the autoinstaller/Packages/debian-stretch.xml distribution packages file for Debian Stretch inside the i-MSCP distribution archive comes with the following definition:
If you want reconfigure or process a new i-MSCP installation (from distribution archive), you should first change the above statement by:
Ref: https://github.com/i-MSCP/imsc…s/debian-stretch.xml#L375
This issue will be fixed in next release.
Great, Thank you for the quick solution!
-
imSCP 1.5.3
Debian 9
PHP 7.1 fpm
LetsEncrypt Plugin 3.5.0
I can no longer install LetsEncrypt Plugin
after re-run imscp updater I get following:
I was able to install the package above, but the imscp installer/ updater does not accept the package
Display MoreCode- apt-cache policy libssl-dev
- libssl-dev:
- Installed: (none)
- Candidate: 1.1.0f-3+deb9u2
- Version table:
- 1.1.1-2+0~20181105132527.5+stretch~1.gbp90eb86 1001
- 1001 https://packages.sury.org/php stretch/main amd64 Packages
- 1.1.0f-3+deb9u2 1002
- 500 http://deb.debian.org/debian stretch/main amd64 Packages
- 500 http://security.debian.org stretch/updates/main amd64 Packages
- 500 http://mirror.hetzner.de/debian/packages stretch/main amd64 Packages
- 500 http://mirror.hetzner.de/debian/security stretch/updates/main amd64 Packages
- root@host1 /usr/local/src/imscp-1.5.3 # sudo apt-get install libssl-dev=1.1.0f-3+deb9u2
- apt-get install libssl-dev=1.1.1-2+0~20181105132527.5+stretch~1.gbp90eb86
when libssl1.1 was updated libssl-dev gets removed, seems to be a global imscp package sources problem ...
-
imSCP 1.5.3
Debian 9
SpamAssassin 2.0.1
ClamAV 1.3.0
What about the additional database settings for bayes and pyzor?
In the plugin config these are activated but in spamassassin database it looks like this:
use_bayes 0
use_pyzor 0
Do they have to be activated or removed from the database?
-
because of gmail and hotmail rate limits.
is there a way to integrate following throttle limits w/ postfix so that it remains compatible with imSCP?
https://wiki.deimos.fr/Postfix…_outgoing_mail_throttling
-
haha,
now it works ... removed the tables and after plugin installation re-imported the switcher plugin user settings ... so I will keep everything intact ... for the next time
-
-
I have not yet used vsftp ... which is faster and most reliable, vsftpd or proftpd?