Closed ant0nwax closed 10 months ago
Hello @ant0nwax, we have a bug 61138 in our private issue tracker.
Hi @igwyd thank you for confirming that you have a private issue tracker for an open source software ;-) i like this world
Hello @ant0nwax, we have a bug 61138 in our private issue tracker.
And it is planned to fix it in a next release quite soon? Because the last release is quite old
For me this "secret bug" does not allow to use Nextcloud with OnlyOffice newer than 7.1
For me this "secret bug" does not allow to use Nextcloud with OnlyOffice newer than 7.1
Same here
@igwyd could you maybe be so kind and please share the status, the estimated release date and the planned fix version for the bug? Background, My nextcloud / Onlyoffice is unusable for 1 week now because I am fed up with restoring, I would like to see if I should restore in order to use only office 7.1 or just wait... but without any OPEN information on your planned release dates, this task is problematic to see, I am not asking you to disclose more private information, but those are information that in my opinion are not a problem to see a bug fixes implementations planned release date for public... correct me if I did not think about some aspects. Thank you very much and I wish you a very nice ongoing weekend and start of the week,
Good to know: at the moment this bug fix is blocking me from leaving my google workspace and starting to use only nextcloud and onlyoffice...
As the Nextcloud OnlyOffice Integration seems to be not important to OnlyOffice, nor Nextcloud, I think I will change the scope to Collabora. I give the two App Developer Teams one more week for Integrating a bugfix, basically there was no work done on the bugfix which is visible, even no release date was shared... Thank you for keeping us posted and not hiding in your private bug tracker...
Restored OnlyOffice 7.1 - works like a charm
Our Developers answered in the bug that this message is for debugging, it does not affect the performance of the application in any way. Problems with your integration in something else. I recommend installing the docker version for the test and connecting it to your cloud.
If on your webpage you write that some of the packaged versions are unsupported after version 7.1 then i will do that, but i did not see that yet on your official releases, so I am waiting for the official version of your comment... actually CentOS / RedHat OnlyOffice Packaged RPM is ONLY SUPPORTED UNTIL 7.1, i do not see any effort of any developers to work on that task, or the priority on that tasks is minimal, it was asked about a planned release, there was no answer from your side for that... just a please install docker.... i bet on CentOS docker version will ALSO NOT WORK, or did you test that with Nextcloud on CENTOS and OnlyOffice Docker on CentOS?
ONLYOFFICE-Docs 7.3.2 works in Centos 7, 8 and 9, we tested it, you can verify this by installing on a clean server, on a virtual machine, for example. I recommended you to test with docker to make sure the warn message in dev-tools and error message in nginx.error.log about missing socket.io.min.js.map doesn't affect the documentserver.
Your problem is something else. And the simplest solution in my opinion is to reinstall the document server.
yes, indeed, my problem is that you have a private bug tracker, that is the main reason why i will not reinstall but consider an OPEN SOURCE software
Our Developers answered in the bug that this message is for debugging, it does not affect the performance of the application in any way. Problems with your integration in something else. I recommend installing the docker version for the test and connecting it to your cloud.
Hi, Thank you for providing answers. I was also on packages, but when the update broke everything, I switched to docker and it doesn't work any better. I have tested all versions post 7.1.
But it is possible that something has changed in the configuration and I am not aware of it. Maybe you should check the documentation too?
@Gspohu lets stick to 7.1 and consider migrating to Collabora i heard it shall be Open Source more than OnlyOffice
@Gspohu i will check. Can you provide links to the documentation you used and provide the documentserver log with errors? @ant0nwax i can't discuss having a private tracker, but I can try to help with the document server issue. As soon as I have more time, I will take a closer look at your issue https://github.com/ONLYOFFICE/DocumentServer/issues/2115. How do you change http to https?
@ant0nwax I checked your case and everythings works fine on my centos 8 steam server, include enabled SELinux and disabled ipv6. Follow this scenario and see it yourself.
/etc/nginx/conf.d/ds.conf
comment out ipv6 string listen [::]:80 default_server;
and restart nginx server and run sudo service supervisord start
sudo systemctl enable supervisord
welcome page
follow instruction to enable the integrated test exaple. Create a document in integrated test exaple. Make sure the document is created and can be edited./etc/nginx/conf.d/ds.conf
comment out ipv6 strings listen [::]:80 default_server;
listen [::1]:80;
and listen [::]:443 ssl default_server;
. Restart nginx service nginx restart
welcome page
follow instruction to enable the integrated test exaple. Create a document in integrated test exaple. Make sure the document is created and can be edited.yum update -y
welcome page
follow instruction to enable the integrated test exaple. Create a document in integrated test exaple. Make sure the document is created and can be edited.PS We test our installations on default clean updated servers because we can't know all of the user's custom settings. Ports https://helpcenter.onlyoffice.com/installation/docs-community-open-ports.aspx. I guess that where on previous installations was somehow lost local.json, its important because default.json must be update from version to new version - I want to change some Document Server parameters from the default.json configuration file. How can I do that so that my changes were not lost after update?
@ant0nwax try this way:
documentserver-configure.sh
@igwyd I shared my tries in the referenced issue https://github.com/ONLYOFFICE/DocumentServer/issues/2115 everything worked fine, but as said there is one problem OPEN and this is the OnlyOffice app add on on CentOS for Nextcloud
please take a look at this:
the app still has a reference for a file called socket.io.min.js.map, which was renamed to socket.io.min.js according to this post:
PLEASE READ IT!
https://github.com/socketio/socket.io/issues/3768
please could you find a method to integrate this change into the code in the Integration App
@ant0nwax i seen it https://github.com/socketio/socket.io/issues/3768 and already answer to you https://github.com/ONLYOFFICE/onlyoffice-nextcloud/issues/763#issuecomment-1445739334, the opinion of our developers has not changed since that moment - this does NOT affect the operation of the application ONLYOFFICE-Docs or connector onlyoffice in nexcloud, we did a lot of tests to make sure. This bug is not a priority now.
I state:
the reference to this renamed file is in the files of the onlyoffice add-on, at least that is what i remember , could you please show a proof that the reference to this file is inside nextcloud and not in the add on?
I need something to open an issue at nextcloud then.
but i remember that i checked and i found the reference inside the mentioned files in the beginning of the issue.
for my understanding nextcloud on centos 8 stream will never work with only office if you update everything to latest with yum update -y
Kind Regards From Phoneland
On Thu, Mar 16, 2023, 08:53 Igor Demin @.***> wrote:
@ant0nwax https://github.com/ant0nwax i seen it socketio/socket.io#3768 https://github.com/socketio/socket.io/issues/3768 and already answer to you #763 (comment) https://github.com/ONLYOFFICE/onlyoffice-nextcloud/issues/763#issuecomment-1445739334, the opinion of our developers has not changed since that moment - this does NOT affect the operation of the application ONLYOFFICE-Docs or connector onlyoffice in nexcloud, we did a lot of tests to make sure. This bug is not a priority now.
— Reply to this email directly, view it on GitHub https://github.com/ONLYOFFICE/onlyoffice-nextcloud/issues/763#issuecomment-1471471162, or unsubscribe https://github.com/notifications/unsubscribe-auth/AH7N7TGID7FKWK7TYM23YGDW4LBINANCNFSM6AAAAAAVA5MXBM . You are receiving this because you were mentioned.Message ID: @.***>
This bug in ONLYOFFICE-Docs, not in nextcloud. As far as I know, because socket.io doesn't provide distribution without socket.io.js.map. Don't know about installation Nextcloud on centos 8. I will try to check it later.
I will stay on 7.1.23 until i hear your result, it is not urgent, but please do not ask me to install docker ;) i am running rpm based and it shall stay like that
FYKI. On Easter weekend I am willing to retry the update, I will continue with our snapshot setup from 26th of February 2023.
solved by something like 5 hours which can be reduced to:
cp /etc/onlyoffice/documentserver/nginx/ds.conf /etc/onlyoffice/documentserver/nginx/ds.conf-backup42
sudo yum reinstall onlyoffice-documentserver
cp /etc/onlyoffice/documentserver/nginx/ds.conf-backup42 /etc/onlyoffice/documentserver/nginx/ds.conf
/usr/bin/documentserver-configure.sh
documentserver-jwt-status.sh # with this you get a secret that is needed for the nextcloud olyoffice integration
systemctl restart ds-docservice.service
systemctl restart nginx
add the JWT secret to nextcloud only office integration and VOILA
I'm glad you did it, thanks for the report.
I think the socket thing is still in the console, but it was never an Error but one of the million Warnings ;)
Hello @ant0nwax, it's solved, can you close this issue?
getting the same error in 7.5.1 debian 12 fresh install
I confirm its still broken with nextcoud on my setup. I just was lazy to login, I tried an upgrade and needed to fall back again, restore the backup before the upgrade I will stop writing and really consider Collabora instead, sorry I wanted really to support OnlyOffice, but it seems there is something not used enough by many so I must let it go
ad SOLVED in that case, was just my fall back / restore the backup :) that was difficult enough, or reinstall, but upgrading is not possible since a certain time... details are in post: https://github.com/ONLYOFFICE/onlyoffice-nextcloud/issues/763#issuecomment-1469954202
I am sure we could setup an online meeting with on of your software quality assurance tessters, but I am not sure if you would like to help me as a non paying customer... I am really just a private user and I am in my second year without microsoft and google :)
Hi developers
please take a look at this: https://github.com/ONLYOFFICE/DocumentServer/issues/2115
it seems to be a link generated by Nextcloud
it is missing a file called
socket.io.min.js.map
, which was renamed tosocket.io.min.js
according to this post:https://github.com/socketio/socket.io/issues/3768
please could you find a method to integrate this change into the code in the Integration App if it is somewhere there the file does not exist on the onlyoffice server and if i copy the
socket.io.min.js
tosocket.io.min.js.map
it does not solve it?at /var/www/onlyoffice i searched for expression
socket.io.min.js.map