Using nextcloud 17.0.2 and documentserver:5.4.2.46 docker images on same server. Both services are working but opening a file in browser displays "The document could not be saved" error message.
Error message points to this url https://api.onlyoffice.com/editors/troubleshooting explaining that the callback handler is not working. "The document editing service cannot connect to the document storage service at the editorConfig.callbackUrl address."
Unsure how to set the callbackUrl any help would be greatly appreciated.
==> /var/log/onlyoffice/documentserver/docservice/out.log <==
[2020-01-08T01:32:36.164] [ERROR] nodeJS - postData error: docId = 173335947;url = http://nc.example.com/apps/onlyoffice/track?doc=eyJ0eXAiO
iJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJ1c2VySWQiOiJtaWtlIiwiZmlsZUlkIjoxMTIsImZpbGVQYXRoIjoiXC9hYmMuZG9jeCIsInNoYXJlVG9rZW4iOm51bGwsImFjdGlvbiI6InRyYW
NrIn0.EWo6KBqF6-ZtcvfrVlvJR5UFLDjmxTt8XKsNgylBv8s;data = {"key":"173335947","status":1,"users":["ocxhbukekiw0_mike"],"actions":[{"type":1,"use
rid":"ocxhbukekiw0_mike"}]}
Error: Error response: statusCode:301 ;body:
<html>
<head><title>301 Moved Permanently</title></head>
<body>
<center><h1>301 Moved Permanently</h1></center>
<hr><center>nginx</center>
</body>
</html>
at Request._callback (/var/www/onlyoffice/documentserver/server/Common/sources/utils.js:301:23)
at Request.self.callback (/var/www/onlyoffice/documentserver/server/Common/node_modules/request/request.js:185:22)
at emitTwo (events.js:126:13)
at Request.emit (events.js:214:7)
at Request.<anonymous> (/var/www/onlyoffice/documentserver/server/Common/node_modules/request/request.js:1161:10)
at emitOne (events.js:116:13)
at Request.emit (events.js:211:7)
at IncomingMessage.<anonymous> (/var/www/onlyoffice/documentserver/server/Common/node_modules/request/request.js:1083:12)
at Object.onceWrapper (events.js:313:30)
at emitNone (events.js:111:20)
at IncomingMessage.emit (events.js:208:7)
at endReadableNT (_stream_readable.js:1064:12)
at _combinedTickCallback (internal/process/next_tick.js:139:11)
at process._tickCallback (internal/process/next_tick.js:181:9)
Server address for internal requests from the Document Editing" defaulted to http://nc.example.com which is wrong, https://nc.example.com is correct. Also must us FQDN not docker service name.
Related
Hi all I am learning Nodejs. I am uploading file to AZURE server, but getting the below error after every 3-4 minutes. Anyone have the solution for this?
The error is ->
Error: read ECONNRESET
at TCP.onStreamRead (internal/stream_base_commons.js:111:27)
Emitted 'error' event at:
at Connection._handleProtocolError
(/Data/core/node_modules/mysql/lib/Connection.js:425:8)
at Protocol.emit (events.js:198:13)
at Protocol.EventEmitter.emit (domain.js:448:20)
at Protocol._delegateError
(/Data/core/node_modules/mysql/lib/protocol/Protocol.js:390:10)
at Protocol.handleNetworkError
(/Data/core/node_modules/mysql/lib/protocol/Protocol.js:363:10)
at Connection._handleNetworkError
(/Data/core/node_modules/mysql/lib/Connection.js:420:18)
at Socket.emit (events.js:198:13)
at Socket.EventEmitter.emit (domain.js:448:20)
at emitErrorNT (internal/streams/destroy.js:91:8)
at emitErrorAndCloseNT (internal/streams/destroy.js:59:3)
"ECONNRESET" means the other side of the TCP conversation abruptly closed its end of the connection. This is most probably due to one or more application protocol errors. You could look at the API server logs to see if it complains about something.
Glad #RakeshSaini that you identified the error which was in the connection waiting limit in the MySQL and for fixing the issue.
In My project with Google calendar api getting error message when trying to authenticate using the code that given by the url
https://accounts.google.com/o/oauth2/auth?access_type=offline&scope=https%3A%2F%2Fwww.googleapis.com%2Fauth%2Fcalendar.readonly&response_type=code&client_id=353577961315-njban7i0ach9ditqeojomv18lmqlcglp.apps.googleusercontent.com&redirect_uri=http%3A%2F%2Flocalhost%3A4200
Error message
Error while trying to retrieve access token { Error: invalid_grant
at Request._callback (C:\Users\PC\Desktop\New folder\node_modules\google-auth-library\lib\transporters.js:81:15)
at Request.self.callback (C:\Users\PC\Desktop\New folder\node_modules\request\request.js:188:22)
at emitTwo (events.js:106:13)
at Request.emit (events.js:191:7)
at Request. (C:\Users\PC\Desktop\New folder\node_modules\request\request.js:1171:10)
at emitOne (events.js:96:13)
at Request.emit (events.js:188:7)
at IncomingMessage. (C:\Users\PC\Desktop\New folder\node_modules\request\request.js:1091:12)
at IncomingMessage.g (events.js:292:16)
at emitNone (events.js:91:20) code: 400 }
What the reason for getting the error message and how can i resolve this issue?
There are 2 common problems that cause invalid_grant errors:
Your server's clock is out of sync with NTP
You've exceeded the refresh token limit
I'd suggest investigating whether either of these issues could be the source of your problem.
I am getting the below error while trying to run Mocha JS test case which runs npm request-promise to call a REST service. I was able to connect to the REST URI endpoint through ARC client bur it failed with below error while running through organization's proxy-
RequestError: Error: connect ETIMEDOUT SERVER_IP:SERVER_PORT
at new RequestError (<Some_Path>\errors.js:14:15)
at Request.plumbing.callback (<Some_Path>\plumbing.js:87:29)
at Request.RP$callback [as _callback] (<Some_Path>\plumbing.js:46:31)
at self.callback (<Some_Path>\request.js:188:22)
at Request.onRequestError (<Some_Path>\request\request.js:884:8)
at TLSSocket.socketErrorListener (_http_client.js:309:9)
at emitErrorNT (net.js:1277:8)
at _combinedTickCallback (internal/process/next_tick.js:80:11)
at process._tickCallback (internal/process/next_tick.js:104:9)
I fixed this issue with adding the following in the request-promise options-
proxy:'http://PROXY_SERVER_IP:PORT#'
I hope this helps.
Cheers,
Kunal
This worked for me
var request = require('request-promise').defaults({
proxy:'http://username:password#host:port',
strictSSL :false
});
I am new to Autodesk-Forge API and I am trying to use the sample dmSample.js, included in the node.js SDK.
The example works well for very small files (up to 500 Kb)
However, when I try to upload larger files, (even just 1 Mb), the execution stops after few seconds with the following error message :
Error: { Error: ESOCKETTIMEDOUT
at ClientRequest.<anonymous> (C:\node.js dev\forge-api-nodejs-client node_mo dules\request\request.js:819:19)
at ClientRequest.g (events.js:292:16)
at emitNone (events.js:86:13)
at ClientRequest.emit (events.js:185:7)
at TLSSocket.emitTimeout (_http_client.js:629:10)
at TLSSocket.g (events.js:292:16)
at emitNone (events.js:86:13)
at TLSSocket.emit (events.js:185:7)
at TLSSocket.Socket._onTimeout (net.js:338:8)
at ontimeout (timers.js:386:14) code: 'ESOCKETTIMEDOUT', connect: false
}
The file I am trying to upload is 30 Mb and is on my local post.
Any idea ?
I was able to fix it by increasing the value of the timeout of the request module.
Forge uses a wrapper that it is located in
/src/ApiClient.js
Search for this.timeout and set it to something like.
this.timeout = 600000;
Sometimes my get request to an api fails with this error message, (btw im using the request module to trigger my requests)
Error: toString failed
buffer.js:378
throw new Error('toString failed');
^
Error: toString failed
at Buffer.toString (buffer.js:378:11)
at BufferList.toString (/home/vardha/www/abp/node_modules/bl/bl.js:155:33)
at Request.<anonymous> (/home/vardha/www/abp/node_modules/request/request.js:1013:32)
at emitOne (events.js:82:20)
at Request.emit (events.js:169:7)
at IncomingMessage.<anonymous> (/home/vardha/www/abp/node_modules/request/request.js:962:12)
at emitNone (events.js:72:20)
at IncomingMessage.emit (events.js:166:7)
at endReadableNT (_stream_readable.js:921:12)
at nextTickCallbackWith2Args (node.js:442:9)
This has been buggin me a lot since I have no idea as to whats causing this and was not able to find any clear solution in the github page. ANy help would be appreciated.
This error usually occurs when you request for file which is relatively bigger in size (or) the bufferlength exceeds / reaches 256 MB which the V8 engine will throw as an error.
This issue is still being addressed by the NodeJS community Read out this comprehensive post which has all the progress/answers that you are looking for.
https://github.com/nodejs/node/pull/4394
Hope this helps!