I switched from Nextcloud office to ONLYOFFICE and I am struggeling to finish the setup:
Here’s what i did:
well…stopped all containers, added ONLYOFFICE container, started container again.
basically it works just fine, but: once I browse to https://cloud.<domain>.<tld>/onlyoffice I land on https://cloud.<domain>.<tld>/onlyoffice/welcome with instruction how to finsh the setup.
I have 2 questions:
while i can start the “test environment” with sudo docker exec nextcloud-aio-onlyoffice sudo supervisorctl start ds:example and connect to the test environment, editing a doc is not possible - just a blank page
when trying to access the admin panel, I am asked for a password. I learned on my testserver (onlyoffice doc server as docker deployment (sudo docker run -i -t -d -p 80:80 --restart=always -e JWT_SECRET=my_jwt_secret onlyoffice/documentserver) w/o nextcloud aio), that the initial login is done via the bootstrap token. This is not possible here… so, what is the actual password, where can i dinf it or how can i reset it?
the first one (the page within the nextcloud administration) is working just fine - as i mentioned in my original post.
Here’s a quick recap:
it seems to work fine, when working on documents within nextcloud
the welcome page and the admin panel are accessable, but i don’t know what to do with it:
Welcome page: cant edit documents in the testing section, can’t access the admin panel
the admin panel is asking for a password, which I don’t know (the bootstrap code, as mentioned in the description” is used to setup the password (i tried it on a testserver) - but during the in my AIO instance I was not asked to setup a passoword
I see. Honestly no clue where the admin password is set. Probably one gets generated automatically if no one is set. Probably best to ask this in an onlyoffice forum.
I don’t know exactly if its the case, but i guess, the issue exists because the AIO onlyoffice integration integrates the enterprise or dev release (there is no 9.1.0.1 community edition) . Thats why the behaviour is different compared to the community edition (which works, see original post).
Nevertheless, haven’t found a solution / answer to the missing admin panel password yet.