-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Only Office Community version, file upload not synchronized #2730
Comments
Hello @Mr-XuanSu ! Please update the document server to the latest version. And check if the issue persists. Since we only support the current latest version, and your issue may already be fixed in it. |
You used wrong path. Do it that: After save chanes and restart nginx If you want us to assist with support, you can contact us at sales@onlyoffice.com. |
My problem has been solved, thank you very much |
This issue is unique.
Operating System of DocumentServer
Docker
Version information
6.3.1.56
Expected Behavior
The results obtained by accessing the only office using IP: 8.130.96.170 are consistent with those obtained by accessing the only office using IP 119.165.74.130
Actual Behavior
The results of accessing two IPs are inconsistent. I found that when I upload files on IP: 8.130.96.170, I cannot view them when accessing the only office using IP: 119.165.74.130. I found that the uploaded files were all saved to the server under/onlyoffice//var/lib/onlyoffice/documentserver example/files, and then the files were saved separately based on their IP addresses.
For example:
I uploaded the a.docx file using IP: 8.130.96.170, and the file was saved under/onlyoffice/var/lib/onlyoffice/documentserver-example/files/8.130.96.170. When I access using IP: 119.165.74.130, I can only see files in the/onlyoffice//var/lib/onlyoffice/documentserver example/files/119.165.74.130 directory
Can I put all the uploaded files in one place and see consistent data regardless of which IP address I use to access them.
Reproduction Steps
No response
Additional information
The text was updated successfully, but these errors were encountered: