Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Randomly nodeJS - error downloadFile with Error response: statusCode:403 #329

Open
zubanst opened this issue Oct 15, 2020 · 1 comment
Open

Comments

@zubanst
Copy link

zubanst commented Oct 15, 2020

Randomly I have nodeJS - error downloadFile errors with Error response: statusCode:403 and documents cannot be opened. Here is my configuration: Server1 ubuntu server 18.04 with ownCloud 10.4.1.3 and onlyoffice connector 6.0.1 and Server2 ubuntu server 18.04 with onlyoffice document-server 5.6 installed from the repository described here https://helpcenter.onlyoffice.com/installation/docs-community-install-ubuntu.aspx . The document server uses https with selfsigned certificate. The document server works fine, a test in a browser on the local network with https://<server_address>/ is redirected https://<server_address>/welcome/ saying Document server is running.
At the first run, the onlyoffice connector on ownCloud was configured with the server address https://<server_address>/, Disable certificate verification checked and no secret key. Saving the configuration, I get the success message. Opening a document from the web interface went fine at the first run. Try open a document by another user from a different computer resulted in a error message saying the server is not accessible. After that I couldn't open the documents myself with the same error. Removing the configuration from the connector and punting it back, randomly allowed me to open documents again. You will see the randomness in the log file attached, at the bottom. I already checked the following things:

  • set a secret connector side and server side - same randomness
    -Time: both servers are ntp synchronized
    -Configure ownCloud with
    'onlyoffice' => array (
    'verify_peer_off' => true
    )
    None of these worked

onlyoffice-issue.zip

@Misokados
Copy link

Hello @zubanst.
According to provided logs, probably something is wrong with Owncloud SSL cerificate and\or your DNS settings.
We found this error in provided logs:
Error [ERR_TLS_CERT_ALTNAME_INVALID]: Hostname/IP does not match certificate's altnames: IP: 192.168.0.16 is not in the cert's list

Could you please check if  domain name is connected with the ip address of the server.
Also try to change default.json config file. Edit field "rejectUnauthorized": true to "rejectUnauthorized": false and restart Document Servers services using command supervisorctl restart all.

Also please provide us with some additional information:

  1. Check the accessibility of the Document Server and ownCloud to each other: execute wget https://documentserver_address/ from the server with your ownCloud and wget https://owncloud_address/ from the server with the Document Server.
  2. Do you use any proxy server between Document server and the storage?
  3. Please reproduce the issue scenario with open browser console:
  • Open browser console (for example, F12 in Chrome) -> choose ‘Network’ tab in browser console -> reproduce the issue -> check if there are any error entries in console and send us a screenshot;
  • Choose ‘Console’ tab in browser console -> reproduce the issue -> check if there are any error entries in console and send us a screenshot.
  1. Attach whole Document server logs folder to your reply or send the archive to support@onlyoffice.com with a note "For technical support/2LVL-issue number". We need to check all logs for diagnose.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants