The user @tasism tried to post the following reply, but for whatever reason the forum software does not let me approve his post. Therefore posting manually:

As I stumbled upon this thread trying to get to get the kopano-docker setup to work behind my reverse TLS proxy (haproxy, not nginx), I just wanted to share the required configuration changes that allowed this to happen for me:

First of all, the configuration variable has changed its name in later versions and is now SECURE_COOKIES (not INSECURE_COOKIES). I chose to put the following in the kopano_webapp.env file:

In addition, I commented out the FQDNCLEANED variable in the .env file:

That’s it, very easy from this perspective…

Latest script verion is 3.0.1

can be found here : https://github.com/thctlo/Kopano

Idea’s, improvements let me know.

@marlemion said in BackendApplicationFlow or LegacyApplicationFlow with kopano-konnectd possible?:

However, the json reply never has a REQUEST_TOKEN.

If you don’t get a request token back, you most likely do not request one (in OpenID Connect this is controlled by requesting the offline_access scope (see https://openid.net/specs/openid-connect-core-1_0.html#OfflineAccess).

@demerzel999 said in kopano-docker build webapp-plugins missing:

I just looked through the sources on the kopano-docker repo, there is nothing about spellcheck in them.

Yes, I removed it in https://github.com/zokradonh/kopano-docker/pull/439

PYTHON3 was definitely the problem. I was able to successfully build! Having a weird issue with it not taking PYTHON_PATH/PYTHON_EXEC_PATH variables to send the python packages to somewhere other than site-packages (I’m looking for dist-packages), but I have a rather embearassing hack in place to move them manually after install. Thanks for your assistance.

I have merged a pr that will skip the download performed in the onbuild step (which was your above failure) in https://github.com/zokradonh/kopano-docker/pull/432. So when you pull the latest image again your build should succeed.

@longsleep said in Konnectd token expiration:

@fkroeger said in Konnectd token expiration:

kopano-meet wasn’t able to retrieve the contacts.

I just learned that the current nightly version of kopano-grapi does not start (because of a falsy permission check). Follow up at https://forum.kopano.io/topic/3243/kopano-grapi-won-t-start-since-10-2-0-4-a5080ed-0-28-2-10-3-0-14-16bdb73-0-31-1-update - it might be related since contacts come from grapi and if that is not running …

Yes, that was it.
I installed the nightly builds from today and ran into the same error you referenced. The workaround did not work. I simply installed an older nightly build of the grapi packages and it works for now.

Access token expiration is now 3540s.

You are the man :-)

Since you are located in Germany as myself perhaps we see each other at an event (if my company is willing to pay for me to visit :-)) and I’ll buy you a beer.
Cheers
Frank Kroeger

Hi @hecke,

thanks for your tutorial! The remote development extensions in Vs code are indeed quite powerful. Been using this for quite a while myself already.

Thanks, @jengelh, that’s what I gathered from reading the GetSetting() code itself. In that case, why are there so many non-NULL-checks in LDAPUserPlugin.cpp for configuration variables? I’d gather they make no sense, because all options have defaults (the empty string); that’s where my initial confusion came from.