Hi,
Thank you for letting us know the details. What you have described is logical and expected behaviour.
We will forward your feedback to our dev teams and will try to get their input as soon as possible. But as they prepare for the new release, reviewing this matter may take some time and getting back to us.
I hope you would understand.
But thanks again.
Have a good day.
Regards,
Sharif
Hello guys,
Greetings
I'm still struggling with this issue without any success.
some details
I've a multi-server scenario over proxmox with public IP and iptables with nat rules.
After upgrading to versionΒ Version 23.9. I can't edit any documents from Files.
the frontend message is justΒ
no healthy upstream
checking mesh logs withΒ
journalctl -u service-discover
I get
Oct 06 07:49:10 storage.yobi365.com service-discoverd[647]: 2023-10-06T07:49:10.808Z [WARN] agent: Check socket connection failed: check=service:carbonio-docs-editor error="dial tcp 127.0.0.1:10000: i/o timeou>
storage syslog I haveΒ
Sep 30 14:35:56 storage service-discoverd[647]: 2023-09-30T14:35:56.411Z [WARN] agent: Check socket connection failed: check=service:carbonio-docs-editor error="dial tcp 127.0.0.1:10000: connect: connection refused"
checking all services with
systemctl list-unit-files "carbonio*"
all seems to be running in all servers.
no firewall was set on local network and all ports are open by default
---
What I suspect:
- some service is not accessible due to missing port setup (not like) or bad configuration (more like because everything was working before upgrade)
- which service? which server? which port?
Β
Appreciate and thank you guys for any help to debug and solve this issue.
Regards
Β
Β
I'm glad that fixed your issue with Docs... I'm still having problems after upgrade with documents and spreadsheets doesn't showing up.
I mean, Docs loads and I ca see all menus and option but no content, just this blank screen, like this:
And that's preventing me to upgrade from 23.7.0 to 23.9.0
I would love to have a quick fix for that issue =(
Grate news, @arman ! But in version 23.9 not fixed this problems:
1. "Undefined" in common name in From: or To: for edit or create a new message.
2. Problem with Russian keyboard layout
https://community.zextras.com/forum/carbonio-general-thread/problem-with-russian-keyboard-layout/
Β
These problems have existed for more than a year, and while the second is still somehow acceptable, the first is a very critical problem.
@sharif With the help of a good friend web developer we found the issue behind the 'blank screen" in Docs: locale.
As my environment is set to use default language as PT-BR then Docs fails to set locale correctly and I get the "blank screen".
If I set my account default language to English, then it works perfectly.
So, on 23.9.0 is Docs trying to change locale somehow? Because in 23.7.0 it was all in English even if your default language was PT-BR, but it was working.
Ok.... now comes the 1M question: how to fix it?
I'm looking forward for that answer so I can finally upgrade my server =)
Complementing my message above. If you remove the "&lang=PT_BR" at the end of the document URL it works.
So something need to be fixed on the code to prevent it from sending that variable OR fix Docs to understand that =)
And.... found the issue: when I set it up to PB-BR URL is generated as "&lang=PT_BR"... underline instead of minus... when I change it to &lang=PT-BR, it works even translating it all... cute!
May you please fix it and release a patch?
Β
the error message
no healthy upstream
means that the carbonio-docs-editor-sidecar service is stopped or not enabled. You can check its status using standardΒ
systemctl status carbonio-docs-editor-sidecar
and restart and/or enable it if needed.
Β
HTH
@stefanodavid Thank you Stefano,
Β
The problem is now solved but the service was up and running but with errors.
I solved it with this info from @anahuac
https://community.zextras.com/forum/postid/5175/
As it was running before the upgrade I didn't check this but now I think that this capabilities were lost with the upgrade.
Perhaps we could have a "postupgradescript" per node to check these issues.
Have a nice day
@antonio that's an amazing idea that already crossed my mind a couple of times. I'll call it "carbfixperms" =)