bad gateway after upgrade to licensed version #899
Comments
|
Hi, is there any errors in Seems DocumentServer trying to connect to some http://127.0.0.1:8000/solr/admin/info/system?wt=json url, which is not aviable. I think DocumentServer itselft may working fine |
|
Healthcheck doesnt oirk because of the 502, log contains |
|
But I dont understand the http://127.0.0.1:8000/solr/admin/info/system?wt=json ist this a new url? |
If healthcheck fails - something wrong, need more logs from Don't sure that you mean, |
|
I have no idea either where it comes from... The only thing I did was the update of the docserver through apt with the normal repo from https://download.onlyoffice.com/repo/debian squeeze main. More logs: Looks like an exception form a missing property? Something new which cam through the update? |
|
Yeah, this is error from DocumentServer, You can add missing option like in defaul.json: |
|
ok, the exception from the missing property is gone now, but healthcheck still says Cannot GET /welcome/healthcheck in the log: |
|
... and https://docs.netzwissen.de/welcome/ is ok now, no gateway error. |
This is not right, are your sure there is no other errors in many If everything ok - I think problem with nginx config, try to compare it with default config, maybe something missed in upgrade. You can look out this file in docker |
|
Good morning, root@docs:~# supervisorctl status all But we have a handshake issue left in the log (the "Connection refused" entries are from before adding the "pgPoolExtraOptions") : |
|
So seems there is only one current error (judging by date) - SSL_do_handshake I've googled |
|
Well, the whole server is auto-updated through unattended updates and its the current standard package for 18.04 lts:
|
|
Could you try to disable SSL/https and see if DocumentServer is working? |
|
ok, I can try that, but I don't understand how this happened: the server was running normal for months and the issue came up after the last upgrade and switch to the licensed version |
I think this is related to upgrade, but switchin to licensed version has nothing to do, it's just |
|
I made a reboot of the doc server and the ssl error is gone, the nginx log is clean now. root@docs:/var/log/onlyoffice/documentserver# tail -f docservice/out.log When using the docserver from out test machine. No change on the OC server concerning docserver settings (api key etc). The test machine has owncloud 10.5 beta, but that should no be important ... |
|
I think this error is not related to DocumentServer itself, since it's from connector. |
|
No, this has nothing to do with the connector, I think. We also have that exception when connecting the docserver directly at https://docs.netzwissen.de/welcome/healthcheck I see "Cannot GET /welcome/healthcheck" as the response And nothing in the nginx log. So, the problem originates in the app server, not in the web server. |
|
https://docs.netzwissen.de/welcome/healthcheck You should check not this url, but |
|
true |
|
ok, it seems like the secret key has been removed from the local.json during update |
This can be. See https://github.com/ONLYOFFICE/DocumentServer/issues/892 |
|
Hm, what was the correct syntax here? I still get "invalid token" when saving in the connector application |
|
Yeah, everything seems fine in syntax, is this placed in |
|
yes |
|
are there any characters which can not be used in the jwt secret? I've set a new key but get "invalid tooken" replies all the time on both OC 10.4 and 10.5 |
I'm not sure |
|
ok, II*ll try. Here is the local.json just to double check if all is OK: |
|
Yeah, I think it should be OK, if not - you'll see errors in logs
…On Tue, Jun 9, 2020, 17:26 psammechinus ***@***.***> wrote:
ok, II*ll try. Here is the local.json just to double check if all is OK:
{
"services": {
"CoAuthoring": {
"sql": {
"dbHost": "localhost",
"dbName": "onlyoffice",
"dbUser": "onlyoffice",
"dbPass": "onlyoffice",
"type": "postgres",
"dbPort": "5432"
},
"redis": {
"host": "localhost"
},
"token": {
"enable": {
"request": {
"inbox": true,
"outbox": true
},
"browser": true
},
"inbox": {
"header": "Authorization",
"inBody": false
},
"outbox": {
"header": "Authorization",
"inBody": false
}
},
"secret": {
"inbox": {
"string": "xxx"
},
"outbox": {
"string": "xxx"
},
"session": {
"string": "xxx"
}
}
}
},
"rabbitmq": {
"url": ***@***.***"
}
}
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#899 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAFDG3ATWNQ5RFWD5OEV4M3RVZBCVANCNFSM4NWMKUWA>
.
|
|
|
This is not right, it should be something like |
|
Hi Pavel, meanwhile I disabled the jwt token stuff for testing. https://docs.netzwissen.de/healthcheck replies with true. nginx log is clean and /docservice/out.log only has some warnings Even without the jwt token I see errors on the owncloud side for both oc 10.4 and 10.5 RC I think the problem lies inside the connector 4.2.1. We already had an issue in an earlier version where the connector did not work in combination with an encrypted oc storage. I think this re-appeared now and we have a regression, >> something for https://github.com/ONLYOFFICE/onlyoffice-owncloud/issues Bye, Thommie |
Yeah, those warning completely normal
Ok, I'll agree, in that case I'll close this issue, but feel free to comment if got some new info |
|
ok, I had some communication with @LinneyS then, created new issue now at ONLYOFFICE/onlyoffice-owncloud#310 |
I bought a license key for ONLYOFFICE Integration Edition Home Server. Added the license file to my already running free doc server and it is now in /var/www/onlyoffice/Data/. Now I see gateway 502 error from the nginx, the error message is:
2020/06/06 21:10:37 [error] 1528#1528: *9 connect() failed (111: Connection refused) while connecting to upstream, client: 195.54.160.135, server: , request: "GET /solr/admin/info/system?wt=json HTTP/1.1", upstream: "http://127.0.0.1:8000/solr/admin/info/system?wt=json", host: "136.243.85.153", referrer: "http://136.243.85.153:80/solr/admin/info/system?wt=json"
root@docs:~# cd /etc/
Did I miss something or do I need to reinstall the whole code before I can use the licensed version?
Thanks for help,
thommie
The text was updated successfully, but these errors were encountered: