Search results

I'm very sorry. I remembered; Nextcloud was operating cron in systemd.

My Plesk does not have that menu. What if it does?

I'm running Nextcloud on PHP 8.0. But Cronjob is running on PHP 7.4. How can I get Cronjob to run on PHP 8.0?

Thank you. I changed it that way. However, I am not sure when I will receive that email, so I am going to wait for a while for it to arrive.

I don't use email on Plesk, so I haven't set anything up at all. The relevant section of main.cf is described as follows mydestination = localhost.$mydomain, localhost, localhost.localdomain #mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain #mydestination = $myhostname...

What "admin@localhost.localdomain"? I receive the above email irregularly to my registered email address. I can't find any entries registered as admin@localhost.localdomain when I log in with Admin and look at the profile and check the full hostname. hostname -f command is also fine. I'm the...

I've switched to PHP 7.4 and am able to use Nextcloud. I'm not sure if it's a problem with NC or PLESK-PHP7.3.

I updated to PHP 7.3.20 and faced an issue with Nextcloud not working and I did. The user can log in to Nextcloud, but immediately after that a 502 error occurs. I once uninstalled PHP7.3.20, and then reinstalled PHP7.3.20 I'm trying. I want to downgrade to PHP 7.3.19. Please tell me how to...

I'm having trouble opening a file with a Japanese file name in Collabora Online(CODE). I can change that file to English and open the file. I use Collabora Online on Nextcloud and Mattermost. Users cannot open files with Japanese file names in either application. Users will not be able to open...

I was able to resolve myself. I removed the CODE in Yum once. Next I removed the repo from /etc/yum.conf.d. Delete /etc/loolwsd as well. Install Collabora Online via PLESK again in this state. This time the installation was successful. I then deleted Collabora Online via Plesk. Here's the...

I used to install Collabora Online(CODE) using yum instead of Plesk. I found out that Collabora Online is also present in the PLESK extension and I enabled it from the Plesk extension. But I had a bad feeling about it, so I quickly deleted it. I have not been able to start loolwsd since then. ●...

This was caused by SELinux. I disabled SELinux, then reinstalled the "selinux-policy" association, then enabled SELinux. Then I was able to start fail2ban successfully.

The filters required by Nextcloud are as follows ``` [Definition] failregex = ^{“reqId”:".",“remoteAddr”:".",“app”:“core”,“message”:“Login failed: '.’ (Remote IP: ‘’)",“level”:2,“time”:".”}$ ^{“reqId”:".",“level”:2,“time”:".",“remoteAddr”:".",“app”:“core”.",“message”:"Login failed: '.’ (Remote...

I use fail2ban and even more so, I use Nextcloud. I've been failing to start fail2ban since NC became version 18. If I remove the Nextcloud item from fail2ban's jail on PLESK UI, fail2ban will start fine. I add Nextcloud to jail and it fails. I tried to set up jail.conf and filter.conf of people...

> daemonize yes I've been setting DAEMONIZE to YES. If I set "daemonize no" in redis.conf, I was able to service it in systemd and start it. When I set it to "daemonize yes", I couldn't start no matter which one I set to "supervised XX". XX: no, upstart ,systemd, auto. Did redis 6.0 change the...

I seem to be able to start Redis-server if I do it manually. sudo -u redis sh -c "/usr/bin/redis-server /etc/redis/6379.conf" In other words, I thought there was something wrong with Systemd's description. I remove the "Type" and the startup itself succeeds, but I can't use the redis. It's the...

I can't start redis when I update to Redis 6.0. I can't start redis when I update to Redis 6.0. I looked at the site that you presented to me. My current Redis is 5.0.9. wget and tcl components are up to date. I've already set up transparent_hugepage and vm.overcommit_memory as well...

Redis 6.0 has been released. I simply updated it with yum and Redis stopped working. Redis 6.0 adds new features such as TLC/SSL and ACL. It's probably a configuration issue with this. How should I install redis 6.0 in the environment where Plesk is used?

I have solved this problem by uninstalling redis once with pecl and installing redis again with pecl as one of the solutions.

> innodb_buffer_pool_size=1024M > query_cache_size=64M I was optimizing MariaDB with an app called mysqltuner.pl. Did I believe it too much? I'm adjusting the above two items, but this Warning does not stop even if I set the value of the above twice (2048M or 128M).