ONLYOFFICE
Error when trying to connect (Error occurred in the document service: Error while downloading the document file to be converted.) (version 7.4.1.36)
This issue is unique.
- [X] I have used the search tool and did not find an issue describing my bug.
Operating System of DocumentServer
Linux (RPM package)
Version information
OnlyOffice 7.4.1
Expected Behavior
Setup SERVER SETTINGS for OwnCloud by Entering the OnlyOffice Docs Address and Key for the OnlyOffice Docs Server.
I expected OwnCloud to Connect to the OnlyOffice Docs Server with a Self Signed Certificate.
Actual Behavior
I have followed the Installation Documentation to Install OnlyOffice. In SERVER SETTINGS for OwnCloud the OnlyOffice Docs Address and Key will not Connect too the OnlyOffice Docs Server.
I receive the Error:
Error when trying to connect (Error occurred in the document service: Error while downloading the document file to be converted.) (version 7.4.1.36).
I am using a Self Signed Certificate created by MkCert.
I did try wget https://OwnCloud IP on the OnlyOffice Server and wget https://OnlyOffice IP on the OwnCloud Server
and receive for both:
Connecting to IP Address ... connected.
ERROR: The certificate of 'IP Address' is not trusted.
ERROR: The certificate of 'IP Address' does not have a known issuer.
Reproduction Steps
These are the Four Guides I used too Install OwnClound and OnlyOffice:
- https://helpcenter.onlyoffice.com/installation/docs-community-install-centos.aspx
- https://helpcenter.onlyoffice.com/installation/docs-community-https-linux.aspx
- https://computingforgeeks.com/how-to-install-rabbitmq-on-rhel-8/?expand_article=1
- https://github.com/FiloSottile/mkcert
Additional information
No response
Hello @kenrmayfield you need to allow Self Signed Certificate in the documentserver, add services.CoAuthoring.requestDefaults.rejectUnauthorized: false (default value is true) it in the /etc/onlyoffice/documentserver/local.json and restart services systemctl restart ds-*
@igwyd
Igor,
Can you show me the Correct way to have it Listed correctly in the JSON File. I already have a Services.CoAuthoring.
Just to let you know.......in the WEB UI for OwnCloud.......Disable certificate verification (insecure) is Checked.
{ "services": { "CoAuthoring": { "sql": { "dbHost": "localhost", "dbName": "", "dbUser": "", "dbPass": "", "type": "postgres", "dbPort": "5432" }, "token": { "enable": { "request": { "inbox": true, "outbox": true }, "browser": true }, "inbox": { "header": "Authorization" }, "outbox": { "header": "Authorization" } }, "secret": { "inbox": { "string": "" }, "outbox": { "string": "" }, "session": { "string": "" } } } }, "queue": { "type": "rabbitmq" }, "rabbitmq": { "url": "amqp://guest:guest@localhost" }, "storage": { "fs": { "secretString": "*****" } } }
I hope you posted a test environment, because you are showing secret config data. In your case:
{
"services": {
"CoAuthoring": {
"sql": {
"type": "postgres",
"dbHost": "localhost",
"dbPort": "5432",
"dbName": "***",
"dbUser": "***",
"dbPass": "***"
},
"redis": {
"host": "localhost"
},
"token": {
"enable": {
"request": {
"inbox": true,
"outbox": true
},
"browser": true
},
"inbox": {
"header": "Authorization"
},
"outbox": {
"header": "Authorization"
}
},
"secret": {
"inbox": {
"string": "***"
},
"outbox": {
"string": "***"
},
"session": {
"string": "***"
}
},
"requestDefaults": {
"rejectUnauthorized": false
}
}
},
"rabbitmq": {
"url": "amqp://guest:guest@localhost"
},
"storage": {
"fs": {
"secretString": "***"
}
}
}
Error attempting to establish connection (An error has occurred in the document service: Unknown error) (version 7.4.1.36)
I have the same problem, I had never experienced this in previous installations.
Nextcloud Hub 5 (27.0.1) onlyoffice-nextcloud v8.1.0
I also have this error when trying to connect Nextcloud 27.0.1 to ONLYOFFICE, the ONLYOFFFICE server is running Debian 12.1 Bookworm and the services appear to be running fine:
service ds-docservice status
* ds-docservice.service - Docs Docservice
Loaded: loaded (/lib/systemd/system/ds-docservice.service; enabled; preset: enabled)
Active: active (running) since Fri 2023-08-04 18:07:43 UTC; 39min ago
Main PID: 505 (docservice)
Tasks: 10 (limit: 3394)
Memory: 122.0M
CPU: 2.950s
CGroup: /system.slice/ds-docservice.service
`-505 /var/www/onlyoffice/documentserver/server/DocService/docservice
service ds-converter status
* ds-converter.service - Docs Converter
Loaded: loaded (/lib/systemd/system/ds-converter.service; enabled; preset: enabled)
Active: active (running) since Fri 2023-08-04 18:07:43 UTC; 39min ago
Main PID: 504 (converter)
Tasks: 20 (limit: 3394)
Memory: 142.5M
CPU: 2.885s
CGroup: /system.slice/ds-converter.service
|-504 /var/www/onlyoffice/documentserver/server/FileConverter/converter
`-618 /var/www/onlyoffice/documentserver/server/FileConverter/converter /snapshot/server/build/server/FileConverter/sources/convertermaster.js
Aug 04 18:07:43 onlyoffice systemd[1]: Started ds-converter.service - Docs Converter.
The healthcheck is true:
lynx -dump "http://127.0.0.1:8000/healthcheck"
true
However when I try to connect from Nextcloud I get:
Error when trying to connect (Error occurred in the document service: Unknown error) (version 7.4.1.36)
In the /var/log/onlyoffice/documentserver/docservice/out.log log I get:
[2023-08-04T18:21:36.118] [WARN] [localhost] [conv_check_1457373887_docx] [userId] nodeJS - sqlQuery error sqlCommand: INSERT INTO task_result (tenant, id, status, statu: error: permission denied for table task_result
at /snapshot/server/build/server/DocService/node_modules/pg-pool/index.js:45:11
at processTicksAndRejections (internal/process/task_queues.js:95:5)
[2023-08-04T18:21:36.118] [ERROR] [localhost] [conv_check_1457373887_docx] [userId] nodeJS - convertRequest error: error: permission denied for table task_result
at /snapshot/server/build/server/DocService/node_modules/pg-pool/index.js:45:11
at processTicksAndRejections (internal/process/task_queues.js:95:5)
Checking the task_result table and find that it is empty:
su - postgres
postgres@onlyoffice:~$ psql
psql (15.3 (Debian 15.3-0+deb12u1))
Type "help" for help.
postgres=# \c onlyoffice
You are now connected to database "onlyoffice" as user "postgres".
onlyoffice=# \dt
List of relations
Schema | Name | Type | Owner
--------+-------------+-------+----------
public | doc_changes | table | postgres
public | task_result | table | postgres
(2 rows)
onlyoffice=# SELECT * from task_result;
tenant | id | status | status_info | created_at | last_open_date | user_index | change_id | callback | baseurl | password | additional
--------+----+--------+-------------+------------+----------------+------------+-----------+----------+---------+----------+------------
(0 rows)
Check that the ds user can connect to PostgreSQL using the setting from /etc/onlyoffice/documentserver/local.json:
su - ds -s /bin/bash
psql -h localhost -U onlyoffice -W onlyoffice
Password:
psql (15.3 (Debian 15.3-0+deb12u1))
SSL connection (protocol: TLSv1.3, cipher: TLS_AES_256_GCM_SHA384, compression: off)
Type "help" for help.
onlyoffice=> \dt
List of relations
Schema | Name | Type | Owner
--------+-------------+-------+----------
public | doc_changes | table | postgres
public | task_result | table | postgres
(2 rows)
That is as far as I can debug it, I'm stuck.
@igwyd
This is a Test Environment so that is why I Posted the Config with the Database Names, Passwords and the Secret Key. However I went ahead and on this Post and took them out.
Thank You for the Help and Quick Response plus the Editing of the local.json File. I still am trying to understand why the Syntax is Different for the Entry you put in the File. The { } Brackets for this Entry is Different then the others?
Does "requestDefaults": { "rejectUnauthorized": false mean the same thing as Checking the Option Disable certificate verification (insecure) in OwnCloud Server Setting?
I did try to Connect the OwnCloud Server to the OnlyOffice Docs Server however there was a Error because the JSON FILE was missing a } Bracket at the End of the File: Error when trying to connect (Server error response [url] https://172.168.146/healthcheck [status code] 502 [reason phrase] Bad Gateway) however once Corrected the Original Error is back: Error when trying to connect (Error occurred in the document service: Error while downloading the document file to be converted.) (version 7.4.1.36)
I checked the Nginx Log File for Errors when the JSON File did not have a } Bracket at the End of the File which showed: 2023/08/04 12:51:06 [error] 4778#0: *13 connect() failed (111: Connection refused) while connecting to upstream, client: 172.168.1.111, server: 171.168.1.146, request: "GET /healthcheck HTTP/1.1", upstream: "http://[::1]:8000/healthcheck", host: "172.168.1.146" however once Corrected the Health Check now shows: TRUE
For the OnlyOffice Docs Server I am running this in a Linux Container CentOS and it is Unprivileged. However I can Ping the OnlyOffice Docs Server from the OwnCloud Server. Would the Nginx Log File Errors mentioned be a Issue with the Linux Container being Unprivileged? I am thinking not so because that has to do with not letting the Linux Container have Full Access to the Host(Proxmox).
@kenrmayfield "Disable certificate verification (not secure)" disables certificate verification in Nextcloud and "rejectUnauthorized": false disables certificate verification in ONLYOFFICE documentserver.
An unprivileged container might be a problem, we haven't tested this. Could you tell us more about your installation and show the container logs docker logs <container>?
@chriscroome i think you have other trouble, have you created a user with owner privileges as specified in the guide?
sudo -i -u postgres psql -c "CREATE USER onlyoffice WITH PASSWORD 'onlyoffice';"
sudo -i -u postgres psql -c "CREATE DATABASE onlyoffice OWNER onlyoffice;"
Try to improve privileges:
ALTER DATABASE onlyoffice OWNER TO onlyoffice;
@cubanitoalex describe in more detail your installation of the documentserver. Have you unprivileged container the same as @kenrmayfield?
@igwyd
It is just a Linux Container Template CentoOS 8 Stream running on Proxmox. There is No Docker. I did change the Linux Container too Privilege...........same Error when trying to Connect OnlyOffice to OwnCloud. OwnCloud version 10.7.0.4 and OnlyOffice Version 7.4.1.36
These are the Four Guides I used too Install OwnClound and OnlyOffice: ONLYOFFICE: https://helpcenter.onlyoffice.com/installation/docs-community-install-centos.aspx https://helpcenter.onlyoffice.com/installation/docs-community-https-linux.aspx RABBITMQ: https://computingforgeeks.com/how-to-install-rabbitmq-on-rhel-8/?expand_article=1 SELF SIGNED CERTIFICATE: https://github.com/FiloSottile/mkcert POSTGRES: https://phoenixnap.com/kb/postgres-create-user https://www.postgresql.org/download/linux/debian/ https://www.postgresql.org/download/linux/redhat/ Note: CentOS Rocky Linux https://towardsdatascience.com/setting-up-postgresql-in-debian-based-linux-e4985b0b766f https://www.geeksforgeeks.org/postgresql-psql-commands/# https://www.postgresqltutorial.com/postgresql-administration/postgresql-drop-database/
Why is there No Documentation about the differnece: "Disable certificate verification (not secure)" disables certificate verification in Nextcloud and "rejectUnauthorized": false disables certificate verification in ONLYOFFICE documentserver?
As you can see in the Screen Shot there is No Indication for the Difference:
Can you Explain why the Syntax { } Brackets are Different for the Entry rejectUnauthorized": false you put in the File. The { } Brackets for this Entry is Different then the others?
- Ok, I get it, I haven't used Proxmox and Linux containers before, it looks like the problem is here. We don't have guides on how to properly create such containers. I'll see what we can do.
- I don't know what documentation you used, but it has here for our connector for the Nexcloud, and here Default request section for ONLYOFFICE Docs
- I don't understand what you mean, there are curly brackets everywhere in my post
@igwyd
LOL.....I meant by the {}Brackets is that if you look at my Original local.json File and then the Editing you did to my local.json File.....where you placed rejectUnauthorized": false......this is what threw me off on how or when you use the {}Brackets correctly.
I showed you the Documentation I used in the My Previous Response to Setup OnlyOffice.
As you can see in the Screen Shot there is No Indication this is for NextCloud only:
Why do you say Proxmox and the Container is a problem?
Proxmox is just a HyperVisor. The Linux Container Template CentoOS 8 Stream I did not have to Create. Setup the Container Environment....Yes....but did not have to Create it.
Proxmox has PreBuilt Templates of Operating Systems you can Download within Proxmox.
Are there any errors in the documentserver logs /var/log/onlyoffice/documentserver/docservice/ and /var/log/onlyoffice/documentserver/converter/?
I mean the documentation for using self-signed certificates in the Nexcloud and the documentserver.
I'm guessing Proxmox with the Linux CentoS 8 Stream container template might be causing some issues, this needs to be checked. Can you check the connection of your OwnCloud with the our official ONLYOFFCICE docker container for a test?
PS Do you mean Code Blocks in markdown?
@igwyd
Docservice err.log Error:
Error: Cannot parse config file: '/etc/onlyoffice/documentserver/local.json': SyntaxError: Unexpected token } in JSON at position 528
at Config.
Converter err.log Error:
Error: Cannot parse config file: '/etc/onlyoffice/documentserver/local.json': SyntaxError: Unexpected end of JSON input
at Config.
SyntaxError in the /etc/onlyoffice/documentserver/local.json you forgot or type extra a comma or a bracket i think, or maybe wrong parameter. Show your local.json with Code Block please.
@igwyd
I am using the Local.JSON that you Edited for me from 4 Days Ago. Look at the the Previous Post were you Sent me the Edited Local.JSON File.
That is why I asked you about the {}Bracket Syntax in the Previous Posts because within the Code Block you Inserted rejectUnauthorized": false which looked different from the other {}Bracket Syntax within the Code Block.
I show you my test config in a previous post as an example) oh, ok, try to use this, edited your config:
{
"services": {
"CoAuthoring": {
"sql": {
"dbHost": "localhost",
"dbName": "",
"dbUser": "",
"dbPass": "",
"type": "postgres",
"dbPort": "5432"
},
"token": {
"enable": {
"request": {
"inbox": true,
"outbox": true
},
"browser": true
},
"inbox": {
"header": "Authorization"
},
"outbox": {
"header": "Authorization"
}
},
"secret": {
"inbox": {
"string": ""
},
"outbox": {
"string": ""
},
"session": {
"string": ""
}
},
"requestDefaults": {
"rejectUnauthorized": false
}
}
},
"queue": {
"type": "rabbitmq"
},
"rabbitmq": {
"url": "amqp://guest:guest@localhost"
},
"storage": {
"fs": {
"secretString": "*****"
}
}
}
@igwyd
That was not your Test Example from 5 Days Ago. Go back and Look. I Sent you My Local.JSON File 5 Days Ago and you made Edits too My JSON File.
On Your Last Post, I have that same Local.JSON File that you just Sent because I caught the Error in the File with a JSON Error Checker. It was missing the } Brackets at the very End.
What did you correct in the JSON File on your Last Post?
Now I saw what you mean and added }.
In the last post I added rejectUnauthorized: false to your local.json (your post).
This was my test server from where I copied local.json to show you how to add the desired string. If you are interested, you can compare the code in the posts and you will see the difference.
So you're still getting the error SyntaxError?
@igwyd
The Errors Persist. I used your Last Post on the Local.JSON File.
Docservice err.log Error:
Error: Cannot parse config file: '/etc/onlyoffice/documentserver/local.json': SyntaxError: Unexpected token } in JSON at position 528
at Config.
Docservice out.log: [2023-08-08T12:35:49.983] [WARN] [localhost] [docId] [userId] nodeJS - Express server listening on port 8000 in production-linux mode. Version: 7.4.1. Build: 36 [2023-08-08T12:36:54.645] [WARN] [localhost] [192.168.1.142new.docx1691516212100] [userId] nodeJS - checkJwt error: name = JsonWebTokenError message = invalid signature token = ************************************* [2023-08-09T07:56:08.458] [WARN] [localhost] [docId] [userId] nodeJS - Express server starting... [2023-08-09T07:56:08.471] [WARN] [localhost] [docId] [userId] nodeJS - Failed to subscribe to plugin folder updates. When changing the list of plugins, you must restart the server. https://nodejs.org/docs/latest/api/fs.html#fs_availability [2023-08-09T07:56:08.501] [ERROR] [localhost] [docId] [userId] nodeJS - [AMQP] Error: connect ECONNREFUSED 127.0.0.1:5672 at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1159:16)
Converter err.log Error:
Error: Cannot parse config file: '/etc/onlyoffice/documentserver/local.json': SyntaxError: Unexpected end of JSON input
at Config.
Converter out.log: [2023-08-09T08:16:39.503] [ERROR] [localhost] [conv_check_867109628_docx] [userId] nodeJS - error downloadFile:url=https://192.168.1.111/index.php/apps/onlyoffice/empty?doc=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJhY3Rpb24iOiJlbXB0eSJ9.Zbapkuy-qrO3PD3lfoz2-UHd4GSq9-t95xrI69x4MZ8;attempt=3;code:undefined;connect:undefined Error: Error response: statusCode:403; headers:{"date":"Wed, 09 Aug 2023 13:16:39 GMT","server":"Apache","strict-transport-security":"max-age=15552000; includeSubDomains","set-cookie":["ocgizt89djxd=tv16kjknmsqcbj9l4rumbnlrfn; path=/; secure; HttpOnly; SameSite=Strict","oc_sessionPassphrase=Vg1GRBkjPWxr0qL7S7YsherTnhwcHlLlaJMpdNw6Azs6tL8AHaFLaUnaBwKYUzUb6GCJoTolIAVTNRPXLQdKfHVH%2BIDPg96Ssyp%2BR5agP63nmbym7Nn0hKcu%2FHX5wXaW; path=/; secure; HttpOnly; SameSite=Strict"],"expires":"Thu, 19 Nov 1981 08:52:00 GMT","cache-control":"no-cache, no-store, must-revalidate","pragma":"no-cache","content-security-policy":"default-src 'none';manifest-src 'self';script-src 'self' 'unsafe-eval';style-src 'self' 'unsafe-inline';img-src 'self' data: blob:;font-src 'self';connect-src 'self';media-src 'self'","x-xss-protection":"0","x-content-type-options":"nosniff","x-frame-options":"SAMEORIGIN","x-robots-tag":"none","x-download-options":"noopen","x-permitted-cross-domain-policies":"none","content-length":"27","keep-alive":"timeout=5, max=100","connection":"Keep-Alive","content-type":"application/json; charset=utf-8"}; at Request.fResponse (/snapshot/server/build/server/Common/sources/utils.js) at Request.emit (events.js:400:28) at Request.onRequestResponse (/snapshot/server/build/server/Common/node_modules/request/request.js:1059:10) at ClientRequest.emit (events.js:400:28) at HTTPParser.parserOnIncomingClient (_http_client.js:647:27) at HTTPParser.parserOnHeadersComplete (_http_common.js:127:17) at TLSSocket.socketOnData (_http_client.js:515:22) at TLSSocket.emit (events.js:400:28) at addChunk (internal/streams/readable.js:293:12) at readableAddChunk (internal/streams/readable.js:267:9) at TLSSocket.Readable.push (internal/streams/readable.js:206:10) at TLSWrap.onStreamRead (internal/stream_base_commons.js:188:23)
You still need to look for the SyntaxError in local.json. For example, I reproduced your error on my server by deleting " in "outbox.header":"Authorization", check out it. Don't forget to restart services after each change systemctl restart ds-*
@igwyd
Maybe I am not explaining correctly. I took your JSON File from 2 Days Ago and filled in the Secret, DBName, DBUser, DBPassword with My Information.
I ran your JSON File that I Edited with My Information through a JSON Checker and it stated No Errors.
Yes, I always Restart or Reboot the DocServer on changes made.
ok, have you any errors in the docimentserver logs if you connect to the owncloud?
@igwyd
I Posted the Error Logs on Yesterday. Look at the Post from Yesterday.
First of all check http://127.0.0.1:8000/healthcheck shows true. If the SyntaxError no longer appears, then nodeJS - checkJwt error: name = JsonWebTokenError message = invalid signature token = ************************************* - you incorrectly specify the secret when connecting to owncloud, recheck it, enter correct secret and reconnect.
@igwyd
Look on the Post I Posted from last week. It shows the Health Check as being True.
I rechecked the Secret from Local.JSON File and it is Correct and also being Entered Correctly in OwnCloud.
Thanks @igwyd you were right regarding the database ownership:
Try to improve privileges:
ALTER DATABASE onlyoffice OWNER TO onlyoffice;
I had:
postgres=# \l
List of databases
Name | Owner | Encoding | Collate | Ctype | ICU Locale | Locale Provider | Access privileges
------------+----------+-----------+---------+-------+------------+-----------------+-----------------------
onlyoffice | postgres | SQL_ASCII | C | C | | libc |
postgres | postgres | SQL_ASCII | C | C | | libc |
template0 | postgres | SQL_ASCII | C | C | | libc | =c/postgres +
| | | | | | | postgres=CTc/postgres
template1 | postgres | SQL_ASCII | C | C | | libc | =c/postgres +
| | | | | | | postgres=CTc/postgres
(4 rows)
After updating the ownership:
postgres=# ALTER DATABASE onlyoffice OWNER TO onlyoffice;
ALTER DATABASE
postgres=# \l
List of databases
Name | Owner | Encoding | Collate | Ctype | ICU Locale | Locale Provider | Access privileges
------------+------------+-----------+---------+-------+------------+-----------------+-----------------------
onlyoffice | onlyoffice | SQL_ASCII | C | C | | libc |
postgres | postgres | SQL_ASCII | C | C | | libc |
template0 | postgres | SQL_ASCII | C | C | | libc | =c/postgres +
| | | | | | | postgres=CTc/postgres
template1 | postgres | SQL_ASCII | C | C | | libc | =c/postgres +
| | | | | | | postgres=CTc/postgres
(4 rows)
However I'm afraid to say that it didn't make a difference, in the past, as far as I'm aware, all that has been required is for the PostgreSQL onlyoffice user to have ALL database privileges for the onlyoffice database -- what extra permissions might be required that are granted when the onlyoffice user is the owner of the onlyoffice database rather than just haveing ALL database privileges?
I still had the issue when saving the ONLYOFFICE connection settings in Nextcloud, this error was produced:
Error when trying to connect (Error occurred in the document service: Unknown error) (version 7.4.1.36)
And in the /var/log/onlyoffice/documentserver/docservice/out.log file this was logged:
[2023-08-10T07:36:36.841] [ERROR] [localhost] [conv_check_777891505_docx] [userId] nodeJS - convertRequest error: error: permission denied for table task_result
at /snapshot/server/build/server/DocService/node_modules/pg-pool/index.js:45:11
at processTicksAndRejections (internal/process/task_queues.js:95:5)
The above issue was with the server running Debian Bookworm (the current stable version of Debian), I have since rebuilt the server with Debian Bullseye (the old stable version) and that has solved the issue -- perhaps the ONLYOFFICE Document server apt packages haven't yet been tested with the Bookworm version of PostgreSQL or something like that?
@igwyd
I did a Reinstall from Scratch and Installed a Clean Copy of Centos 8 Stream for OwnCloud and Onlyoffice.
I still get the same Error that this Post was created with.
@kenrmayfield There is just a JWT error in your log. Ok, I'll test this behavior on my stand.
@chriscroome we tested on debian 12, but maybe something broke, I'll double check thanks.
@igwyd
Igor.......this is not Directed at you however this is Ridiculous referring too Documentation. I Spent Relentless Hours(2 Weeks) of Investigation. Igor Thank You for your Help.
I Now Have Success. I can now Connect OwnCloud to OnlyOffice.
I have Setup and Tested on Centos 8 Stream(OwnCloud and OnlyOffice) and LXC Containers(OwnCloud and OnlyOffice).
I did more Investigation in which the Solution or more In Detail Instruction should have been in the Documentation for the Linux Version you are Installing OnlyOffice and OwnCloud on.
There were Two Issues causing the Connection Errors from OwnCloud to OnlyOffice: First Issue: Error: Error when trying to connect (Error occurred in the document service: Error while downloading the document file to be converted.) (version 7.4.1.36) Reason: Using a SSL Self Sign Certificate on the Document Server in which the Document Server cannot verify the SSL Certificate because of issues with the Trust Chain. Fix: Igor you were Correct on Adding ["requestDefaults": { "rejectUnauthorized": false] to the Local.Json File to eliminate the Error Message.
Second Issue:
Error:
Error when trying to connect (Client error: GET https://IP ADDRESS/cache/files/data/conv_check_718565083_docx/output.docx/check_718565083.docx?md5=29hz438X8NGq35NP7u6CQQ&expires=1691951456&filename=check_718565083.docx resulted in a 403 Forbidden response: 403 Forbidden (version 7.4.1.36)
Reason:
The [set $secure_link_secret "storage_secret";] in the DS.Conf File does not match the ["secretString": "storage_secret"] in the Local.Json File.
Fix:
You must have the [set $secure_link_secret "storage_secret";] in the DS.Conf File to match the ["secretString": "storage_secret"] in the Local.Json File.
@chriscroome you are right, previously it was not required to own the database, we had to change it due to PostgreSQL 15 also revokes the CREATE permission from all users except a database owner from the public (or default) schema. Rechecked the installation on Debian 12 guide - no errors.
@kenrmayfield about second reason, you probably forgot to run sudo bash /usr/bin/documentserver-update-securelink.sh in the guide Switching ONLYOFFICE Docs to HTTPS protocol. I'm glad you did it, can we close this issue?
@igwyd
Igor actually I did not forget to run that documentserver-update-securelink.sh. That Script is a problem. It has Wiped Out my DS.CONF several Times. I had to get the DS.CONF Restored from /etc/nginx/conf.d/ds.conf since it makes a Symbolic Link to /etc/onlyoffice/documentserver/nginx/ds.conf.
The Script documentserver-update-securelink.sh has Wiped Out /etc/onlyoffice/documentserver/nginx/ds.conf several times.