Nextcloud 3 10 0

This app hasn’t been tested with the latest 3 major releases of Nextcloud. It may no longer be maintained or supported and may have compatibility issues when used with more recent versions of Nextcloud. Highest Nextcloud version Nextcloud 23 Show all releases Community rating Author Klaus Herberth Last updated 3 years, 1 month ago Categories Social & communication Resources Homepage User documentation Admin documentation Developer documentation Interact Report problem Request feature Ask questions or discuss Releases Nextcloud version Stable channel Nightly channel All releases 23 5.0.0 - 23 22 5.0.0 - 22 21 4.3.1 - 21 20 4.3.1 - 20 19 4.3.1 - 19 18 4.2.1 - 18 17 4.2.1 - 17 16 4.1.1 - 16 15 3.4.4 4.0.0-rc.1 (Unstable) 15 14 3.4.4 - 14 13 3.4.3 - 13 12 3.4.3 - 12 11 3.3.2 - 11 10 3.3.2 - 10 9 3.2.1 - 9 No comments found. Comments Switch language for the comments:

[docId] [userId] nodeJS - update cluster with 1 workers[2022-12-06T19:49:22.253] [WARN] [localhost] [docId] [userId] nodeJS - update cluster with 1 workersdocumentserver/metrics/out.log has a lot of entries (ever 5 minutes) like:Flushing stats at Wed Dec 07 2022 11:45:22 GMT+0000 (Coordinated Universal Time){ counters: { 'statsd.bad_lines_seen': 0, 'statsd.packets_received': 0, 'statsd.metrics_received': 0 }, timers: {}, gauges: { 'statsd.timestamp_lag': 0 }, timer_data: {}, counter_rates: { 'statsd.bad_lines_seen': 0, 'statsd.packets_received': 0, 'statsd.metrics_received': 0 }, sets: {}, pctThreshold: [ 90 ]}All values 0.All three err.log are empty. Also nginx.error.log has no entries of today (two errors from earlier trials with example). The Advanced server settings allows to set the ONLYOFFICE Docs address for internal requests from Nextcloud server and the returning Nextcloud address for the internal requests from ONLYOFFICE Docs, i.e. Advanced server settings are used when servers are not publicly available for each other. Which doesn’t seem to be your case.So I ask you to perform next actions:close Advanced server settings of the connector app;use your (Document Server address) in the ONLYOFFICE Docs address field and press ‘Save’;open any document from Nextcloud to reproduce the issue;open browser’s console (F12 in Chrome/Firefox/Edge);reload the page;make screenshots of network and console tabs of browser’s console to share with us.Also please check if your servers can reach each other with wget from Nextcloud server to Document Server and from inside the Document Server container to Nextcloud address and share outputs.After reproducing the issue that way please share the whole catalog with us. You can upload it to your Nextcloud portal and

Use your Nextcloud log to review system status, or to help debug problems. You may adjust logging levels, and choose how and where log data is stored. If additional event logging is required, you can optionally activate the admin_audit app.When file based logging is utilized, both the Nextcloud log and, optionally, the admit_audit app log can be viewed within the Nextcloud interface under Administration settings -> Logging (this functionality is provided by the logreader app).Further configuration and usage details for both the standard Nextcloud log and the optional admin_audit app log can be found below.Log levelLogging levels range from DEBUG, which logs all activity, to FATAL, which logs only fatal errors.0: DEBUG: All activity; the most detailed logging.1: INFO: Activity such as user logins and file activities, plus warnings, errors, and fatal errors.2: WARN: Operations succeed, but with warnings of potential problems, plus errors and fatal errors.3: ERROR: An operation fails, but other services and operations continue, plus fatal errors.4: FATAL: The server stops.By default the log level is set to 2 (WARN). Use DEBUG when you have a problem to diagnose, and then reset your log level to a less-verbose level as DEBUG outputs a lot of information, and can affect your server performance.Logging level parameters are set in the config/config.php file.Log typeerrorlogAll log information will be sent to PHP error_log()."log_type" => "errorlog",WarningUntil version Nextcloud 25 log entries were prefixed with [owncloud]. From 26 onwards messages start with [nextcloud].fileAll log information will be written to a separate log file which can beviewed using the log viewer on your Admin page. By default, a logfile named nextcloud.log will be created in the directory which hasbeen configured by the datadirectory parameter in config/config.php.The desired date format can optionally be defined using the logdateformat parameter in config/config.php.By default the PHP date function parameter c is used, and therefore thedate/time is written in the format 2013-01-10T15:20:25+02:00. By using thedate format in the example below, the date/time format will be written in the formatJanuary 10, 2013 15:20:25."log_type" => "file","logfile" => "nextcloud.log","loglevel" => 3,"logdateformat" => "F d, Y H:i:s",syslogAll log information will be sent to your default syslog daemon."log_type" => "syslog","syslog_tag" => "Nextcloud","logfile" => "","loglevel" => 3,systemdAll log information will be sent to Systemd journal. Requires php-systemd extension."log_type" => "systemd","syslog_tag" => "Nextcloud",Log fields explainedExample log entries{ "reqId":"TBsuA2uE86DiOD0S8f9j", "level":1, "time":"April 13, 2021 16:55:37", "remoteAddr":"192.168.56.1", "user":"admin", "app":"admin_audit", "method":"GET", "url":"/ocs/v1.php/cloud/users?disabled", "message":"Login successful: "admin"", "userAgent":"curl/7.68.0", "version":"21.0.1.1"}{ "reqId":"ByeDVLuwkXKMfLpBgvxC", "level":2, "time":"April 14, 2021 09:03:29", "remoteAddr":"192.168.56.1", "user":"--", "app":"no app in context", "method":"POST", "url":"/login", "message":"Login failed: asdf (Remote IP: 192.168.56.1)", "userAgent":"Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/89.0.4389.114 Safari/537.36", "version":"21.0.1.1"}Log field breakdownreqId (request id): any log lines related to a single request have the same valuelevel: logged incident’s level, always 1 in audit.logtime: date and time (format and timezone can be configured in config.php)remoteAddr: the IP address of the user (if applicable – empty for occ commands)user: acting user’s id (if applicable)app: affected app (always admin_audit in audit.log)method: HTTP method, for example GET, POST, PROPFIND, etc. – empty on occ callsurl: request