Admin UI "broken"

mculibrk · 2023-10-18T10:30:22+00:00

Hi! I just noticed that the Admin UI is practically "broken/unusable" for me... i suppose after the last upgrades (a day-two ago). Well... it half works......

mculibrk

WalterH

I fixed that... when I saw that the crashing call was to a library that was not available.

So... at least as far as see/know sync is now working...

But it's the Admin UI that makes me mad.... (uwsgi failing in that python library/call/function/mapping... and I have no idea how to fix that? All packages seems there...)

Would you be so kind to check what's your version of python+libraries on a working Debian11 server? Thanks!

mculibrk

...or maybe install the admin parts from the supported repo (which should be older... hopefully old enough...)
Will check but if the repo was updated with the 1.11. versions then I'll have to go the "restore backup" route... (and then the obvious answer to "issues" will be "update to the last versions"...)

mculibrk

Hurray!!!

With the last grommunio-admin-common update (grommunio-admin-common 17.1694125-1+12.1) the Admin UI is "back" from the "brokenland"....

It still throws "Connection refused" like before (even if I checked/changed all the dns names/resolution so all should be resolving as required) but at least it loads and I can access it like before (with limited functionality but still)

weini

The Debian 12 specific issue described here https://community.grommunio.com/d/1157-debian-12-grommunio-admin-api-uwsg-cant-create-domain is still in place.

This can be worked around with a config file /etc/grommunio-admin-api/conf.d/05-openapi-dirty-fix.yaml

openapi:
  validateRequest: False
  validateResponse: False

Check file permissions and ownership, they need to be identical to the other yaml files in the same folder.

However, this just disables the OpenAPI validation which is there for a good reason. So a fix is still needed for this.

« Previous Page