Posts by jackstone

    kess


    Thank you very much for the tip, it wasn't open_basedir, it was the shell_exec function which stopped the OnlyOffice from working, in case someone else runs into this problem, just disable all disable_functions and the connection between NextCloud and OnlyOffice will work.

    Hello guys,


    I've been trying to install an Office Server to run with Nextcloud for the past 2 days, every type of install or software I choose I run into the same problem. It just doesn't work on a Nextcloud instance which is setup on a i-MSCP server.


    I have the following config :


    1. Nextcloud installed on i-MSCP server as a client. (working ok, but complaining much due to php restrictions)

    2. Collabora and Onlyoffice installed with Docker and working on remote servers without i-MSCP


    Now the problem :


    Every time I try to open a document from the Nextcloud installation on i-MSCP i get either a "connection refused" from the onlyoffice server or "Failed to load Collabora Online" from the Collabora server.


    Luckily, I have other Nextcloud installations as well which are not on i-MSCP servers and from those Nextclouds both OnlyOffice and Collabora work perfectly and I can edit documents.


    I cannot seem to find one log file to find why in the name of God the i-MSCP Nextcloud install refuses to "talk" to office servers, i disabled the firewalls, i tried with curl, works both ways, I've edited HSTS settings thinking they could be a problem, I disabled all php restrictions thinking that maybe they could be a problem, NOTHING WORKS !


    From what I can tell so far, there is something in the i-MSCP php or vhost settings that blocks the exchange of information between the nextcloud server and the office server(s) but I have no idea what and I've spent hours browsing through logs end enabling debug tools.


    If anyone has a solution, please help !! If I can't make it work i have to give up hosting Nextclouds on i-MSCP servers and that is not something that I want.


    Thank you!

    Hello again guys,


    So, I managed to install corectly phpSwitcher 5.0.5, and installed php 7.2 using the following command :


    Code
    1. perl /var/www/imscp/gui/plugins/PhpSwitcher/PhpCompiler/php_compiler.pl --register 7.2

    Everything went well and php 7.2 got installed.


    Now the problem.


    In one of the domains, I switched from php5.6 (default on server) to php7.2

    Immediately the server gives an error when I try to access the webiste with the following error.log :


    Code
    1. [Fri Dec 20 22:42:07.421034 2019] [proxy:error] [pid 28306:tid 139852037216000] (2)No such file or directory: AH02454: FCGI: attempt to connect to Unix domain socket /run/php/php5.6-fpm-ishop24.com.sock (ishop24.com) failed
    2. [Fri Dec 20 22:42:07.421110 2019] [proxy_fcgi:error] [pid 28306:tid 139852037216000] [client x.x.x.x:7432] AH01079: failed to make connection to backend: httpd-UDS
    3. [Fri Dec 20 22:42:25.160050 2019] [proxy:error] [pid 28306:tid 139851609384704] (2)No such file or directory: AH02454: FCGI: attempt to connect to Unix domain socket /run/php/php5.6-fpm-ishop24.com.sock (ishop24.com) failed
    4. [Fri Dec 20 22:42:25.160116 2019] [proxy_fcgi:error] [pid 28306:tid 139851609384704] [client x.x.x.x:7505] AH01079: failed to make connection to backend: httpd-UDS


    So, for some reason, even after I switch to php 7.2, the website still tries to use php5.6-fpm.


    Any ideeas how to fix this ? The only reason I bought the plugin was because of this website requirements to use 7.2.


    Thank you.

    Hello,


    I've recently purchased the phpSwitcher plugin and i'm trying to install it in Ubuntu 18.04 server with i-MSCP 1.5.3.

    I've searched the forum for similar threads but couldn't find my exact scenario, most of them offer a fix for Debian sources.list.

    Anyway, here is the error :

    And the sources.list

    Can someone please tell me what's wrong with it ?

    I tried to install it on a different Ubuntu 18.04 server and it works there, so I copied the entire /etc/apt folder from that server to this one, but it still doesn't work, so I don't think it's an apt problem.


    Thanks!

    Back with an update :)


    I couldn't help myself and I finished the full upgrade to Debian 10. I thought well, if it's gonna break I'm just gonna reinstall it, maybe even switch to Ubuntu 18.04. So I've made all the backups and finished the upgrade and rebooted the server. Fortunately, besides a small bind problem which wouldn't start with "localhost" in the masters section of named.conf.local, which I had to switch to 127.0.0.1 in order to make bind start again, everything else seems to work fine, the panel is running, websites are ok, and the mail system is good. I'm now running i-MSCP 1.5.3-2018 on Debian 10 without any problems (at least not discovered yet)


    Just in case someone else accidentally starts an upgrade :)


    Cheers

    I am still wondering why did you use dist-upgrade? Simply update and upgrade should be fine enough. :-/


    I think I got used this way :)


    Anyway, thanks for your reply, I think I'll just leave it like this for a while, if something breaks I'll just re-install it, I wanted to switch tu Ubuntu 18 for some time now, this might be the perfect excuse :)

    Hello Everybody,


    One of my systems running on Debian 9 was setup for automatic updates and in sources list "stable" was defined instead of stretch, so when Debian 10 was launched it started to update the packages. Fortunately I managed to stop the upgrade mid-way and apparently only non-critical packages were upgraded in the process, although /etc/issue says Debian GNU/Linux 10 \n \l the system has quite a lot of packages that need to be upgraded.


    These are the packages that still need to be upgraded :


    My questions are :


    1. Is it safe to perform a full-upgrade to Debian 10 without breaking i-MSCP ?

    2. If not, any suggestions on what to do next besides a full reinstall of Debian 9 ?

    3. Should I leave the system in this state until support is added to i-MSCP for Debian 10 ?

    4. Any idea when support for Debian 10 will be included in i-MSCP ? - last question is for Nuxwin


    Thanks!