Changes 09.05.2019
– Add links to webdeasy.de-Guides „Install Nextcloud with Beta-Extension „Nextcloud“
———————————————–
Changes 25.03.2019
– Add screenshot for finding out Plesk-User
– Add link to Redis to clarify
– Add link to Nextcloud-Background-Job-Manual
– Add instructions to adjust nginxClientMaxBodySize
———————————————–
Changes 23.03.2019
– Add Screenshot for memcache-block in config.php to clarify
– Adjust entry for crontab
In this Howto I will show you to install Nextcloud 15 on a Plesk VPS with nginx only
If you want to install Nextcloud via the Extension „Nextcloud“ (Beta-State) then follow this guides:
webdeasy English-Version
or
webdeasy German Version
Then come back and switch to nginx-only.
Nextcloud recommends the use of a MemoryCache. If we have ssh-access to our server, we install redis for this. Redis is an in-memory database with a simple key-value data structure and belongs to the family of NoSQL databases.
If you want to know more, follow this link.
The following command installs the appropriate package:
sudo apt-get install redis-server
please check the status of redis:
sudo systemctl status redis
Output:
Prepare vHost:
In Plesk we create the subdomain under domains:
and secure it with LetsEncrypt:
Within the subdomain we use the file manager:
and remove all files and directories:
Now we have to download the Nextcloud-Webinstaller from the following URL to our workstation:
Afterwards we upload it to our Webspace in Plesk:
In Apache/NGINX settings
of the subdomain, we set the following values for Additional nginx directives
(Customize Domain / Subdomain):
rewrite ^/.well-known/host-meta /public.php?service=host-meta last; rewrite ^/.well-known/host-meta.json /public.php?service=host-meta-json last; rewrite ^/.well-known/webfinger /public.php?service=webfinger last; add_header Strict-Transport-Security "max-age=15768000; includeSubDomains; preload;"; location = /.well-known/carddav { return 301 $scheme://$host/remote.php/dav; } location = /.well-known/caldav { return 301 $scheme://$host/remote.php/dav; } location = /robots.txt { allow all; log_not_found off; access_log off; } # Enable gzip but do not remove ETag headers gzip on; gzip_vary on; gzip_comp_level 4; gzip_min_length 256; gzip_proxied expired no-cache no-store private no_last_modified no_etag auth; gzip_types application/atom+xml application/javascript application/json application/ld+json application/manifest+json application/rss+xml application/vnd.geo+json application/vnd.ms-fontobject application/x-font-ttf application/x-web-app-manifest+json application/xhtml+xml application/xml font/opentype image/bmp image/svg+xml image/x-icon text/cache-manifest text/css text/plain text/vcard text/vnd.rim.location.xloc text/vtt text/x-component text/x-cross-domain-policy; location ~ ^\/(?:build|tests|config|lib|3rdparty|templates|data)\/ { deny all; } location ~ ^\/(?:\.|autotest|occ|issue|indie|db_|console) { deny all; } location ~ ^\/(?:updater|ocs-provider)(?:$|\/) { try_files $uri/ =404; index index.php; } # Adding the cache control header for js and css files location ~ \.(?:css|js|woff2?|svg|gif)$ { try_files $uri /index.php$request_uri; add_header Cache-Control "public, max-age=15778463"; add_header X-Content-Type-Options nosniff; add_header X-XSS-Protection "1; mode=block"; add_header X-Robots-Tag none; add_header X-Download-Options noopen; add_header X-Permitted-Cross-Domain-Policies none; add_header Referrer-Policy no-referrer; } location ~ \.(?:png|html|ttf|ico|jpg|jpeg)$ { try_files $uri /index.php$request_uri; }
NGINX-Settings:
In PHP settings
we set the version to 7.2.x or 7.3.x and enter the following value under OPEN-Base-Dir
:
{WEBSPACEROOT}{/}{:}{TMP}{/}:/dev/urandom:/proc/meminfo
in section disable_functions
you have to delete opcache_get_status
and insert none
.
Don’t forget to adjust the upload_max_filesize
and post_max_size
values.
as example we can use the following values if you want to upload files not greater than 2 GB:
Then set pm
to dynamic
and adjust, as example:
At the bottom of the page under Additional configuration instructions
, we set following parameters:
opcache.enable_cli=1 opcache.interned_strings_buffer=8 opcache.max_accelerated_files=10000 opcache.memory_consumption=128 opcache.save_comments=1 opcache.revalidate_freq=1 [php-fpm-pool-settings] env[PATH] = /usr/local/bin:/usr/bin:/bin
To allow uploading large files, we have to adjust the nginxClientMaxBodySize in panel.ini of Plesk:
We can do this in two ways, the easiest way is to edit the file with nano:
sudo nano /opt/psa/admin/conf/panel.ini
and we add the following content:
[webserver] nginxClientMaxBodySize = 2048M
or you can install the „Panel.ini Editor“-Extension of Plesk and edit the file in Plesk:
Do not to forget to save this file.
Among the hosting settings
, we have to set the 301 redirect
(http to https) and run php
set to FPM Application served by nginx
:
Prepare Database
Add a database within the subdomain:
and accept or adjust the following settings and write them down for later use:
Finish the installation
Via the web browser, we call our Nextcloud-Webinstaller and complete the Installation now:
https://nextcloud.your-domain.tld/setup-nextcloud.php
In the next step, we enter a single „.“ into the field:
And after another click on „Next“, we should see the success of the installation:
The next step is to adjust the settings:
If we are logged in, we have to edit the config.php
in config directory in Plesk via File Manager and insert the following block for the cache behind the „Trusted Domains-Array“ (if redis is installed):
'memcache.distributed' => '\\OC\\Memcache\\Redis', 'memcache.local' => '\OC\Memcache\\Redis', 'memcache.locking' => '\\OC\\Memcache\\Redis', 'redis' => array( 'host' => 'localhost', 'port' => 6379, ),
it should look like this:
If we have ssh-access (as root or Plesk-User), then we can create a CRON
job (adjust user) for Nextcloud-Background-Jobs:
you can find the user in the domain view of plesk:
as example with my User as root:
sudo crontab -u nextclouding.de -e
if you have ssh-Access as Plesk-User „nextclouding.de“ than:
crontab -e
and enter the following lines (customize domain and subdomain):
for php7.2:
SHELL="/bin/sh" */15 * * * * /opt/plesk/php/7.2/bin/php -f 'nextcloud.your-domain.tld/cron.php' > /dev/null
for php7.3:
SHELL="/bin/sh" */15 * * * * /opt/plesk/php/7.3/bin/php -f 'nextcloud.your-domain.tld/cron.php' > /dev/null
Sometimes it is also possible to add a task via the GUI:
Otherwise, we use an external WebCron service, for example EasyCron.
The URL that needs to be called is:
https://nextcloud.domain.tld/nextcloud/cron.php
Among the basic settings, we check Nextcloud for errors and subsequently also in Plesk in the subdomain under logs.
you should see a warning for bigint indentifiers
because of this you have to execute the following command in your shell:
sudo -u admin php /var/www/vhosts/your-domain.tld/nextcloud.your-domain.tld/occ db:convert-filecache-bigint
After this errors or warnings should no longer be displayed.
If you have problems or questions, suggestions, don’t hesitate to contact me.
See you and happy Nextclouding 🙂
52 Gedanken zu „How to install Nextcloud 15 within Plesk with nginx only“
Wouldn’t it be cool(er) to use the docker-extension for providing the redis ?
Yes, but please be aware. The Docker-Extension exposes ports to the world wide web:
https://talk.plesk.com/threads/exposing-docker-container-ports-for-localhost-only.348260/
Vielen Dank für die tolle Anleitung! Wie gehe ich bei einem Update meiner NC vor? Installiere ich die neue Version „einfach drüber“ oder muss ich hier anders vorgehen?
Gerne. Ganz normal über den webbasierten Updater in den Einstellungen.
Hallo Markus, nach einem Serverwechsel (jetzt Ubuntu 18.04.2 LTS+Plesk habe ich die Nextcloud 16 nach Deiner Anleitung installiert, was gut geklappt hat. Danke für Deinen Beitrag! Jetzt bleiben 2 Punkte.
1. Im Nextcloud-Dasboard erhalte ich folgende Meldung:
„MySQL wird als Datenbank verwendet, unterstützt jedoch keine 4-Byte-Zeichen. Um beispielsweise 4-Byte-Zeichen (wie Emojis) ohne Probleme mit Dateinamen oder Kommentaren verarbeiten zu können, wird empfohlen, die 4-Byte-Unterstützung in MySQL zu aktivieren. Für weitere Details lesen Sie bitte die Dokumentationsseite (https://docs.nextcloud.com/server/16/admin_manual/configuration_database/mysql_4byte_support.html) hierzu.“
Ich habe die Dokumentation gelesen und versucht, mit hilfe von php-admin diesen notwendigen Befehl umzusetzen: „ALTER DATABASE nextcloud CHARACTER SET utf8mb4 COLLATE utf8mb4_general_ci;“ Das endet bei mir leider mit einer Fehlermeldung. Hast Du dies schon gemacht/versucht?
2. Die Synchronisation zwischen meinem Windows-Desktop-Client 2.5.2 (auch 2.5.0) scheitert immer mit der Fehlermeldung „HTTP/2-Protokoll-Fehler“ nachdem einige Dateien von meinem Rechner in die Cloud hochgeladen wurden. Es geht jetzt zwar problemlos nach einem Downgrade auf Nextcloud-Client Version 2.3 – ist aber etwas unbefriedigend. Weißt Du, was die Ursache sein könnte?
Beste Grüße
Jürgen
Hallo Jürgen,
zu 1.
für mysql legst Du einfach eine neue cnf-Datei an:
nano /etc/mysql/mysql.conf.d/anpassung.cnf
Inhalt:
dann:
systemctl restart mysql
dann die Schritte 3-5 wie in der Anleitung.
Schritt 5 wechselt automatisch in den Maintenance-Mode und dauert eine Weile.
Zu 2.
Geh mal hier durch, wenn Du es noch nicht getan hast:
Troubleshooting Nextcloud Client
Viele Grüße
Markus
Danke Markus, wenn ich in Schritt 3
„ALTER DATABASE (meine Nextcloud-DB) CHARACTER SET utf8mb4 COLLATE utf8mb4_general_ci;“ bei sql-Befehle in php-Admin eingebe, dann erhalte ich als Ergebnis: „MySQL lieferte ein leeres Resultat zurück (d.h. null Datensätze). (Die Abfrage dauerte 0.0012 Sekunden.)“
Mache ich da etwas falsch?
Mein MySQL-Server gibt unter Plesk als Versionsinformation folgendes heraus:
Server: Localhost via UNIX socket
Server-Typ: MariaDB
Server-Verbindung: SSL wird nicht verwendet Dokumentation
Server-Version: 10.1.40-MariaDB-0ubuntu0.18.04.1 – Ubuntu 18.04
Protokoll-Version: 10
Benutzer: 3_SVx7@localhost
Server-Zeichensatz: UTF-8 Unicode (utf8)
Muss ich dann eher:
[mysqld]
innodb_file_per_table=1
statt
[mysqld]
innodb_large_prefix=true
innodb_file_format=barracuda
innodb_file_per_table=1
eintragen, da Version höher als 8.0 ist?
Beste Grüße
Jürgen
Hallo Markus, jetzt hat es doch noch mit der DB-Umstellung geklappt – statt mit PHPadmin habe ich den Befehl jetzt direkt über die Bash im MySQL-Server eingegeben – und das hat auf Anhieb geklappt! Danke nochmals für Deine Hilfe!
Hallo Jürgen,
Wie immer gerne ?
Super Anleitung, allerdings habe ich die Pretty URLs so nicht zum Laufen gebracht. Gibt es hier schon Neuigkeiten? Außerdem gibt es bei mir die Datei /opt/psa/admin/conf/panel.ini zum Erhöhen des Upload-Limits nicht. Momentan brauche ich auch keine so großen Dateien, wäre aber trotzdem interessant zu wissen, ob man diese Datei, falls sie nicht exisitert und auch der Pfad nach psa nicht vorhanden ist, trotzdem dafür angelegt werden sollte. Zur Info: Ich nutze Plesk Onyx auf einem CentOS 7.
Als Workaround für Pretty-URLs habe ich deshalb doch wieder Apache mit dazu genommen und die Konfiguration von dieser Anleitung übernommen: https://markus-blog.de/index.php/2018/10/10/how-to-install-nextcloud-14-within-plesk-via-web-installer/
Die Pretty URL-Thematik ist noch auf der todo-Liste, aktuell ist etwas Overhead 😉
Die panel.ini kannst Du anlegen und bearbeiten oder Du installiert die entsprechende Erweiterung, siehe auch hier: https://docs.plesk.com/de-DE/onyx/administrator-guide/78509/
Vielen dank für deine Super Anleitung.
leider habe nwir aber imemr noch ein problem mit WebDav
Sabre\DAV\Exception\NotAuthenticated: No public access to this resource., No ‚Authorization: Basic‘ header found. Either the client didn’t send one, or the server is misconfigured, No ‚Authorization: Bearer‘ header found. Either the client didn’t send one, or the server is mis-configured, No ‚Authorization: Basic‘ header found. Either the client didn’t send one, or the server is misconfigured
<>
Sabre\DAV\Auth\Plugin->beforeMethod(Sabre\HTTP\R … „}, Sabre\HTTP\Response {})
/var/www/vhosts/docs…../httpdocs/nextcloud/3rdparty/sabre/event/lib/EventEmitterTrait.php – line 105:
call_user_func_array([ Sabre\DAV\ … „], [ Sabre\HTTP … }])
/var/www/vhosts/docs./httpdocs/nextcloud/3rdparty/sabre/dav/lib/DAV/Server.php – line 466:
Sabre\Event\EventEmitter->emit(„beforeMethod“, [ Sabre\HTTP … }])
/var/www/vhosts/docs./httpdocs/nextcloud/3rdparty/sabre/dav/lib/DAV/Server.php – line 254:
Sabre\DAV\Server->invokeMethod(Sabre\HTTP\R … „}, Sabre\HTTP\Response {})
/var/www/vhosts/docs./httpdocs/nextcloud/apps/dav/lib/Server.php – line 316:
Sabre\DAV\Server->exec()
/var/www/vhosts/docs.httpdocs/nextcloud/apps/dav/appinfo/v2/remote.php – line 35:
OCA\DAV\Server->exec()
/var/www/vhosts/docs……/httpdocs/nextcloud/remote.php – line 163:
require_once(„/var/www/vh … p“)
Hallo Bastian,
Funktioniert webdav-Aufruf über den Browser? Mit welchem Client funktioniert es nicht?
Gruß Markus
Also der nextcloud client geht nicht bekomme keine Anmeldung hin. Der Kalender für Mac os leider auch nicht. Webdav als Laufwerk geht.
Welche Fehlermeldungen sind denn auf der Client-Seite?
Hi Markus,
Ich habe seid dem letzten Nextcloud-Update (15.0.7) diesen Fehler
„MySQL wird als Datenbank verwendet, unterstützt jedoch keine 4-Byte-Zeichen. Um beispielsweise 4-Byte-Zeichen (wie Emojis) ohne Probleme mit Dateinamen oder Kommentaren verarbeiten zu können, wird empfohlen, die 4-Byte-Unterstützung in MySQL zu aktivieren.“
Leider finde ich keine Lösung die bisher funktioniert hat.
System:
Plesk Onyx 17.8.11
Debian 9.8
MariaDB 10.1.37
Kannst du mir hier evtl. weiter helfen?
Hallo Mark,
Was hast Du denn für Lösungen ausprobiert?
Grüße aus Dresden
Markus
Moin, wie in der Doku von Nextcloud beschrieben:
MariaDB 10.2 or earlier
Make sure the following InnoDB settings are set on your MySQL server:
[mysqld]
innodb_large_prefix=true
innodb_file_format=barracuda
innodb_file_per_table=1
Restart the MariaDB server in case you changed the configuration in step 1.
Figure out whether the file format was changed to Barracuda:
MariaDB> SELECT NAME, SPACE, FILE_FORMAT FROM INFORMATION_SCHEMA.INNODB_SYS_TABLES WHERE NAME like „nextcloud%“;
If the file format is “Barracuda” for every single table, nothing special is left to do. Continue with the MySQL instructions at step 3. While testing, all tables’ file format was “Antelope”.
The tables needs to be migrated to “Barracuda” manually, one by one. SQL commands can be created easily, however:
MariaDB> USE INFORMATION_SCHEMA;
MariaDB> SELECT CONCAT(„ALTER TABLE `“, TABLE_SCHEMA,“`.`“, TABLE_NAME, „` ROW_FORMAT=DYNAMIC;“) AS MySQLCMD FROM TABLES WHERE TABLE_SCHEMA = „nextcloud“;
This will return an SQL command for each table in the nextcloud database. The rows can be quickly copied into a text editor, the “|”s replaced and the SQL commands copied back to the MariaDB shell. If no error appeared (in doubt check step 2) all is done and nothing is left to do here. It can be proceded with the MySQL steps.
It is possible, however, that some tables cannot be altered. The operations fails with: “ERROR 1478 (HY000): Table storage engine ‘InnoDB’ does not support the create option ‘ROW_FORMAT’”. In that case the failing tables have a SPACE value of 0 in step 2. It basically means that the table does not have an index file of its own, which is required for the Barracuda format. This can be solved with a slightly different SQL command:
MariaDB> ALTER TABLE `nextcloud`.`oc_tablename` ROW_FORMAT=DYNAMIC, ALGORITHM=COPY;
Replace oc_tablename with the failing table. If there are too many (did not happen here), SQL commands can be generated in a batch (task for the reader).
Now everything should be fine and the MySQL instructions can be followed from step 3 onwards
Leider ohne erfolg … 🙁
Wenn es dabei keine Fehler gab und der Hinweis immer noch angezeigt wird, kannst Du folgendes mal versuchen:
und im Anschluß:
Es kam folgende Fehlermeldung:
In AbstractMySQLDriver.php line 115:
An exception occurred while executing ‚ALTER TABLE `oc_addressbooks` CONVERT TO CHARACT
ER SET utf8mb4 COLLATE utf8mb4_bin;‘:
SQLSTATE[42000]: Syntax error or access violation: 1071 Specified key was too long; max
key length is 767 bytes
In PDOStatement.php line 107:
SQLSTATE[42000]: Syntax error or access violation: 1071 Specified key was too long; max
key length is 767 bytes
In PDOStatement.php line 105:
SQLSTATE[42000]: Syntax error or access violation: 1071 Specified key was too long; max
key length is 767 bytes
Dennoch klappte es in Nextcloud … hmm.
Im Nextcloud log steht jetzt auch:
[no app in context] Error: Doctrine\DBAL\Exception\DriverException: An exception occurred while executing ‚ALTER TABLE `oc_addressbooks` CONVERT TO CHARACTER SET utf8mb4 COLLATE utf8mb4_bin;‘:
SQLSTATE[42000]: Syntax error or access violation: 1071 Specified key was too long; max key length is 767 bytes at
0. /var/www/vhosts/domain.tld/cl.domain.tld/3rdparty/doctrine/dbal/lib/Doctrine/DBAL/DBALException.php line 128
convertException(„An exception oc … s“, Doctrine\DBAL\Dr … ]})
1. /var/www/vhosts/domain.tld/cl.domain.tld/3rdparty/doctrine/dbal/lib/Doctrine/DBAL/Statement.php line 177
driverExceptionDuringQuery(Doctrine\DBAL\Driver\PDOMySql\Driver {}, Doctrine\DBAL\Dr … ]}, „ALTER TABLE `oc … ;“, [])
2. /var/www/vhosts/domain.tld/cl.domain.tld/lib/private/Repair/Collation.php line 100
execute()
3. /var/www/vhosts/domain.tld/cl.domain.tld/lib/private/Repair.php line 96
run(OC\Repair {})
4. /var/www/vhosts/domain.tld/cl.domain.tld/core/Command/Maintenance/Repair.php line 119
run()
5. /var/www/vhosts/domain.tld/cl.domain.tld/3rdparty/symfony/console/Command/Command.php line 255
execute(Symfony\Componen … {}, Symfony\Componen … {})
6. /var/www/vhosts/domain.tld/cl.domain.tld/3rdparty/symfony/console/Application.php line 946
run(Symfony\Componen … {}, Symfony\Componen … {})
7. /var/www/vhosts/domain.tld/cl.domain.tld/3rdparty/symfony/console/Application.php line 248
doRunCommand(OC\Core\Command\Maintenance\Repair {}, Symfony\Componen … {}, Symfony\Componen … {})
8. /var/www/vhosts/domain.tld/cl.domain.tld/3rdparty/symfony/console/Application.php line 148
doRun(Symfony\Componen … {}, Symfony\Componen … {})
9. /var/www/vhosts/domain.tld/cl.domain.tld/lib/private/Console/Application.php line 213
run(Symfony\Componen … {}, Symfony\Componen … {})
10. /var/www/vhosts/domain.tld/cl.domain.tld/console.php line 96
run()
11. /var/www/vhosts/domain.tld/cl.domain.tld/occ line 11
require_once(„/var/www/vhosts … p“)
at 2019-04-24T18:17:13+00:00
Heißt jetzt ok oder noch Fehler?
Nextcloud schreibt:
Alle Überprüfungen bestanden.
Log gibt oben den folgenden Fehler wieder. Ich werde prüfen welche Auswirkungen es hat und melde mich ggf. wieder.
Danke dir erstmal
Dann ist noch nicht gut:
plesk db
use nextcloud_db;
set global innodb_large_prefix=on;
set global innodb_file_format=Barracuda;
exit
Und dann nochmal occ maintenance:repair
Gerne
Moin Markus,
sind deine Befehle für die CLI?
Grüße
Moin Mark,
Sorry, ja, sind sie. Mit plesk db kommst Du als root in die MySQL-shell, dann natürlich DB-Namen anpassen.
Markus
Danke für den Link ?
Des Rätsels Lösung:
innodb_large_prefix=1 statt innodb_large_prefix=on
? Super
Moin,
leider bleibt der Fehler. Hier ein Auszug:
Doctrine\DBAL\Exception\DriverException: An exception occurred while executing ‚SELECT `uid`, `displayname` FROM `oc_users` `u` LEFT JOIN `oc_preferences` `p` ON (`userid` = `uid`) AND (`appid` = ’settings‘) AND (`configkey` = ‚email‘) WHERE (`uid` COLLATE utf8mb4_general_ci LIKE ?) OR (`displayname` COLLATE utf8mb4_general_ci LIKE ?) OR (`configvalue` COLLATE utf8mb4_general_ci LIKE ?) ORDER BY `uid_lower` ASC LIMIT 500 OFFSET 500′ with params [„%%“, „%%“, „%%“]: SQLSTATE[42000]: Syntax error or access violation: 1253 COLLATION ‚utf8mb4_general_ci‘ is not valid for CHARACTER SET ‚utf8‘
Doctrine\DBAL\Exception\DriverException: An exception occurred while executing ‚ALTER TABLE `oc_addressbooks` CONVERT TO CHARACTER SET utf8mb4 COLLATE utf8mb4_bin;‘: SQLSTATE[42000]: Syntax error or access violation: 1071 Specified key was too long; max key length is 767 bytes.
_____________________________
Frage kann ich denn die Datenbank im vorhinein vorbereiten und Nextcloud dann neuinstallieren? Wenn ja wie bereite ich die vor dass utf8mb4 von vorhinein eingestellt ist.
Schau mal hier: https://github.com/nextcloud/news/issues/226
Hi Markus,
I would like to use the “ pretty urls“ function get rid of the „/index.php“ in my urls. I tried to integrate it here: „Additional nginx directives“. But I don’t found out how to do that correctly, so i switched back to your addidtional directives.
Do you know how to get the pretty urls working with nginx?
Thanks for your help,
Lukas
Hi Lukas,
Which config did you try?
Markus
I found something similar there:
https://help.nextcloud.com/t/pretty-urls-for-nextcloud-11-with-nginx-and-php5/11921
I tried some parts of this config, but then I’ve got som nginx socket errors.
The nextcloud user manual only describes how to use „pretty urls“ with apache.
It would be a nice to have feature, but if it won’t work it will be no problem.
Thanks for your fast reply. ?
OK. Give me some time and let me look at this. ? You’re welcome and thanks for reading my Guides.
Hi Markus
Did you already find a way to make pretty URLS work with only nginx?
Best wishes
Hi Lukas, sorry. Unfortunately not made in time, I hope next week.
Hi Markus
another question, is it safe to apply Nginx directions to an existent Nextcloud running on Apache? to become Nginx only
thanks again
Yes this is possible. Disable Proxy Mode of nginx, add directives and Switch php-handler to php-fpm served by nginx. Sometimes you have to Switch php-handler in php-settings and Hosting-Settings.
thanks man, now it works
you are awesome!
may I ask you to help me fixing these issues?
https://www.htbridge.com/ssl/?id=4LGCQYq7
thanks in advanced
Your welcome 🙂
Please run this Test again with your hostname and then look at the result.
dear Markus
thank you very much for your tutorials, they are really helpfull,
i have followed this tutorial from the first step, which is installing Redis Server
i have Plesk Onyx latest version on Ubuntu 16.04
but when I add these lines to config.php I get this error on the website:
Internal Server Error
The server encountered an internal error and was unable to complete your request.
Please contact the server administrator if this error reappears multiple times, please include the technical details below in your report.
More details can be found in the webserver log.
should I make some configurations for Redis?
I’m not a linux user but I can follow copy paste commands 🙂
thanks in advance
Hi Mansour,
Your welcome ?
let me know what is recorded in nextcloud.log in the data directory. You can also send it as a mail, then I’ll look at it and sign up again.
Best Regards.
Markus
You are using a fallback implementation of the intl extension. Installing the native one is highly recommended instead. at /var/www/vhosts/mns.ps/cloud.mns.ps/3rdparty/patchwork/utf8/src/Patchwork/Utf8/Bootup/intl.php#18
Every 15 min, after i’v choseen Cron
Dear Markus
the log file is empty :/
but when I remove the lines from the config.php I can enter the next cloud
but I notice now that there is a problem with Cron I think
Error PHP You are using a fallback implementation of the intl extension. Installing the native one is highly recommended instead. at /var/www/vhosts/mns.ps/cloud.mns.ps/3rdparty/patchwork/utf8/src/Patchwork/Utf8/Bootup/intl.php#18
Hi Mansour,
What is the output of:
systemctl status redis
Php-intl-error:
Try to change cronjob to use php instead of plesk-php, is the error then gone?
Markus
Dear Markus
the input is :
● redis-server.service – Advanced key-value store
Loaded: loaded (/lib/systemd/system/redis-server.service; enabled; vendor preset: enabled)
Active: active (running) since Thu 2019-03-21 16:47:21 CET; 1 day 17h ago
Docs: http://redis.io/documentation,
man:redis-server(1)
Main PID: 121568 (redis-server)
Tasks: 3
Memory: 1.4M
CPU: 2min 8.123s
CGroup: /system.slice/redis-server.service
└─121568 /usr/bin/redis-server 127.0.0.1:6379
Mar 21 16:47:21 mns.ps systemd[1]: Starting Advanced key-value store…
Mar 21 16:47:21 mns.ps run-parts[121559]: run-parts: executing /etc/redis/redis-server.pre-up.d/00_exampl
Mar 21 16:47:21 mns.ps run-parts[121569]: run-parts: executing /etc/redis/redis-server.post-up.d/00_examp
Mar 21 16:47:21 mns.ps systemd[1]: Started Advanced key-value store.
Mar 21 16:55:49 mns.ps systemd[1]: Started Advanced key-value store.
~
~
~
~
~
~
~
~
~
~
~
~
lines 1-17/17 (END)
it works.
i have found the nextcloud.log file,
here it is:
{„reqId“:“t5cEpoCwvMjSACJ8qKCM“,“level“:3,“time“:“2019-03-21T15:26:13+00:00″,“remoteAddr“:““,“user“:“–„,“app“:“PHP“,“method“:““,“url“:“–„,“message“:“You are using a fallback implementation of the intl extension. Installing the native one is highly recommended instead. at \/var\/www\/vhosts\/mns.ps\/cloud.mns.ps\/3rdparty\/patchwork\/utf8\/src\/Patchwork\/Utf8\/Bootup\/intl.php#18″,“userAgent“:“–„,“version“:“15.0.5.3″}
and when I add these configs to the conf file at the end:
……
‚installed‘ => true,
23
);
24
‚Memcache.distributed‘ => ‚\\ OC \\ \\ Memcache Redis‘
25
‚Memcache.local‘ => ‚\ OC \ Memcache \ Redis‘
26
‚Memcache.locking‘ => ‚\\ OC \\ \\ Memcache Redis‘
27
‚Redis‘ => array (
28
‚Host‘ => ‚localhost‘
29
‚Port‘ => 6379
30
)
I get this error:
Internal Server Error
The server encountered an internal error and was unable to complete your request.
Please contact the server administrator if this error reappears multiple times, please include the technical details below in your report.
More details can be found in the webserver log.
Sorry, you have to insert this behind Array Trusted Domains etc… behind ),
…
‚Memcache.distributed‘ => ‚\\ OC \\ \\ Memcache Redis‘
‚Memcache.local‘ => ‚\ OC \ Memcache \ Redis‘
‚Memcache.locking‘ => ‚\\ OC \\ \\ Memcache Redis‘
‚Redis‘ => array (
‚Host‘ => ‚localhost‘
‚Port‘ => 6379
),
I will add a Screenshot in this Guide to make it easier to understand.
If you have this line in your config.php file, try to uncomment it.
#’memcache.local‘ => ‚\\OC\\Memcache\\APCu‘,
For me it now works.
Hi Markus, thank you very much for this new blog post.
It really helped me getting strange problems solved. With the configuration I previously had (I think it came from your NC 13 Guide). After the NC15.0.5 update I had Problems to sync/create folders that ended like some file-extentions (such as tar in „Congstar“). I really don’t what exactly was going on there, but i got
“ 405 MKCOL /remote.php/webdav/Dokumente/Schriftverkehr/Congstar HTTP/2.0″ errors in my logs.
The updated Plesk-Config in this post solved my problems.
Thanks for sharing this!
Chris
Hi Chris,
Thank you very much. Your welcome ??
Regards
Markus