Posts by Mr.X

Salut Nuxwin,

Quote from Nuxwin

This issue has been fixed lately in our git repository...

I cloned from git today on the 1.5.3-maintenance branch and still see this error.

Br

Mr.X

Quote from Eyecu

Just testing out Debian 10 support and noticed when attempting to install any plugin i get the following error

Code

1. An unexpected error occurred
2. An exception has been thrown in file /var/www/imscp/gui/src/Plugin/Validate/PluginArchive.php at line 251:
4. Argument 1 passed to iMSCP\Plugin\Validate\PluginArchive::_getPluginInfoFromString() must be of the type string, null given, called in /var/www/imscp/gui/src/Plugin/Validate/PluginArchive.php on line 442

I know it's not production ready, just thought I would add this to this thread.

Hi,

any news on this issue? Looks like i-mscp is expecting a type of string instead of null. Something we can fix? This is blocking me from testing the plugins with the latest version.

Br

Mr.X

Hi FloRet88,

thanks for your quick reply. I know I am not on the latest version but will update in the next days.

Meanwhile I fixed the issue by executing

and renew in the GUI at the end.

BR

Mr.X

Hi,

since today we see this error message in the GUI. Anyone else with the same issue and a solution available?

Quote

Traceback (most recent call last):
File "/usr/local/sbin/certbot", line 7, in <module>
from certbot.main import main
File "/opt/eff.org/certbot/venv/local/lib/python2.7/site-packages/certbot/main.py", line 5, in <module>
import logging.handlers
File "/usr/lib/python2.7/logging/__init__.py", line 26, in <module> import sys, os, time, cStringIO, traceback, warnings, weakref, collections

File "/usr/lib/python2.7/weakref.py", line 14, in <module> from _weakref import ( ImportError: cannot import name _remove_dead_weakref at /var/www/imscp/gui/plugins/LetsEncrypt/backend/LetsEncrypt.pm line 834.

Running with version

Quote

i-MSCP 1.5.3

Build: 20180516

Codename: Ennio Morricone

Br

Mr.X

Quote from Nuxwin

In our wiki, we don't mention that Buster is supported, and if you look at the INSTALL.md file of the latest stable version, you can see that the list of supported Debian versions are Debian Jessie (7.x) and Debian Stretch (8.x). See https://github.com/i-MSCP/imsc…supported-debian-versions

So, basically put, you're using an i-MSCP version, and a PhpSwitcher plugin version that were not tested under Debian Buster. Current i-MSCP stable version is compatible with Debian Stretch, not with Debian Buster. Therefore, I'm primarly wondering why you did that update without more thinking about your current environment... Debian Buster has just been released.

Regarding the configuration failure when you try to re-compile your PHP versions, this can be due to many things... I cannot say more without investigating directly on your server.

Salut Nuxwin,

thanks for your reply. The update was not on purpose, apt was using stable .-/

Any change to get a beta of phpSwitch? Or a possible release date?

I could see in one of the git commits that apc makes some troubles ...

Br

Jan

Quote from Iceman

Next release date....

Its in the final steps, so I guess rather sooner than later.

I edited the post, because it seemed to me that the first part might sound rude. It wasnt meant that way, btw.^^

Hi Iceman,

no worries ! .-)

Shit hit the fan as I cannot roll back and the customer is getting upset as the webpage is not working anymore .-/

Br

Mr.X

Quote from Iceman

Debian 10 isn't supported officially (but another user reported its working). I think thats the issue here at the moment.

The needed phpswitcher version will re released with or close after / before the new i-MSCP version. Which got support for newer php versions.

Hi Iceman,

thanks for your reply. I've read the wiki and checked the forum before. But couldn't find something similar to this.

Do we know when the new version will be released... yeah, I know when it's done it's done .-) But will it be 2 months or 6 months?

I don't know why your text about wiki and forum is not shown here in the forum while it's in your email. Nevertheless ...

Hi all,

last night one of my servers updated to the lastest stable version. All looked good at first. This morning a customer called us that his webpage is not working anymore.

After some investigation I found out that the php version / PhpSwitcher is not working anymore .-(

System is running latest Debian Buster and imscp 1.5.3.

In the apache log I could see

Quote

[Mon Jul 15 10:14:04.694796 2019] [proxy:error] [pid 22367:tid 140344532383488] (2)No such file or directory: AH02454: FCGI: attempt to connect to Unix domain socket /run/phpswitcher/psw7.0-fpm-DOMAIN.sock (DOMAIN) failed

.5

I checked the admin gui and could see also error messages here like

Quote

Plugin::PhpSwitcher::_checkPhpVersionData: `/opt/phpswitcher/20180618/php7.0/bin/php-cgi' doesn't looks like a PHP FastCGI binary

so I tried to reinstall different php version via

Quote

perl /var/www/imscp/gui/plugins/PhpSwitcher/PhpCompiler/php_compiler.pl --auto-setup 5.6

but I received this error message

Quote

[ERROR] main: An unexpected error occurred: An error occurred while executing the install MAKE(1) target for php-5.6.32: aclocal: warning: autoconf input should be named 'configure.ac', not 'configure.in'

../configure: line 5408: test: too many arguments

configure: error: freetype-config not found.

make: *** [/var/www/imscp/gui/plugins/PhpSwitcher/PhpCompiler/Makefile:370: configure-5.6-stamp] Error 1

same error message for 7.1

Quote

[ERROR] main: An unexpected error occurred: An error occurred while executing the install MAKE(1) target for php-7.1.11: aclocal: warning: autoconf input should be named 'configure.ac', not 'configure.in'

../configure: line 5352: test: too many arguments

configure: error: freetype-config not found.

make: *** [/var/www/imscp/gui/plugins/PhpSwitcher/PhpCompiler/Makefile:370: configure-7.1-stamp] Error 1

but freetype fonts are installed

Quote

dpkg -l|grep freetype

ii libfreetype6:amd64 2.9.1-3 amd64 FreeType 2 font engine, shared library files

ii libfreetype6-dev:amd64 2.9.1-3 amd64 FreeType 2 font engine, development files

Right now I don't know how to solve this issue. Do you have a hint for me? Merci !

BR

Mr.X

Hi Nuxwin,

I did search the forum first but could find any details.

I also looked at the plugin page to get some details.

This link is very helpful, thx.

Mr.X

Quote from Nuxwin

Mr.X

The control panel is made available through dedicated ports and is run through dedicated httpd instance (nginx). If you try to access it through standard http ports (through Apache2) while there is no Apache2 vhost files for the control panel domain, Apache2 will serves the first site found (here example2.com) and therefore:

The SSL certificate will be marked as invalid by your browser because the name admin.example1.com doesn't match with the name example2.com.

Don't forget: The control panel is run through dedicated ports and through nginx Web server, not Apache2 Web server. Thus, by default, there are not Apache2 vhost files for the control panel by default, those last that would make you able to reach the control panel through standard http ports (80, 443). The PanelRedirect plugin was meant to provide access to the control panel through standard http ports by creating the Apache2 vhost files for the control panel using either simple http redirection or the proxy feature. However, the PanelRedirect plugin has been deprecrated in favor of the i-MSCP redirect (proxy) feature.

So what now?

• Either you always access the control panel through expected non standard ports (look at your /etc/imscp/imscp.conf file for the ports)
• Either you add the control panel domain as client domain or subdomain and you enable the proxy feature and Let's Encrypt for it.

Regarding the DefaultServerPage plugin

That plugin will prevent Apache2 to serve the default site found when there are no Apache2 vhost file for the domain you try to reach. Instead, a default server page will be served.

Display More

Salut Nuxin,

thanks for your long answer. Ok, understood.

But what do you mean with "i-MSCP redirect (proxy) feature"?

Br

Mr.X