NethServer Version: NS8
Module: Onlyoffice
Hi,
i installed onlyoffice like GitHub - mrmarkuz/ns8-onlyoffice · GitHub
But received thid error wen clik save in Onlyoffice App in nextcloud.
“Errore durante il tentativo di connessione (Stato di controllo integrità non valido)”, translate:
“Error trying to connect (Invalid health check state)”
My first question: is normal have two instance aftere install procedure?
I tryed config both istances, but ireceived the same error.
TK
Hi Roberto,
Yes, when you install an app, a new instance is installed and the old one remains.
It seems you installed an instance from command line using the latest tag. This should be avoided as latest may be not be ready for production and updates won’t work.
Onlyoffice should be installed from Software Center to install the right version tag.
I recommend to remove all onlyoffice instances and start over with a fresh installation via Software Center.
Hi,
Okay, I performed a fresh installation via the Software Center, and it installed version 1.1.7. I didn’t do anything else.
I ran the command to view the secret and then configured the app in Nextcloud.
I got the same error.
By the way, when I installed OnlyOffice, it was instance number 6, and the uninstallation probably wasn’t completely clean.
TK
Please remove the other onlyoffice instances, just one instance is needed. They can be removed from Software Center.
The instance number is raised to avoid issues, that’s ok.
Hi, Markuz
Partially solved…
The error message was caused by the firewall resolving office.xxxxx.it to a LAN IP (192.168.1.253) instead of the public IP.
I disabled the internal DNS record in the firewall, and now everything works, but when I go through the provider’s IP, I don’t know if this is convenient for the PCs on the LAN network…
Question: I saw that you can enable the option to make a LAN IP acceptable in Nextcloud. What do you recommend?
Ciao e grazie
In general an internal DNS record is a good practice to keep the traffic locally and avoid load on the router due to NAT reflection (or hairpin) but both methods are working and secure.
Hi, Markuz
Okay, but if I also wanted to enable the use of LAN IPs, there are some commands I need to run. Does this depend on the NextCloud app or the document server?
TK
I don’t know if it could be related to an update, but the same problem occurred on another server that’s been in production for a while now. It used the LAN’s internal IP as the DNS, and now it’s not working. I made the same change, confident everything would be fine, but now I’m getting the token error. I tried to find the JWR Secret, but when I run the “runaget” command, I get an invalid command response.
But this is another history…
It depends on the Nextcloud config.
To edit the Nextcloud config.php file enter the Nextcloud app environment, in this example the instance name is nextcloud1:
runagent -m nextcloud1
Edit config.php:
podman unshare nano $(podman volume inspect nextcloud-app-data --format={{.Mountpoint}})/config/config.php
At the bottom add 'allow_local_remote_servers' => true so it looks like this:
'instanceid' => 'oc42caiyw6ks',
'mail_smtpstreamoptions' => '',
'allow_local_remote_servers' => true,
);
I think it’s due to missing environment/path.
Does it work when you use the full path?
/usr/local/bin/runagent -m nextcloud1
To get root with right path, please use
su -
or
sudo su -
TK so much…