We have within /etc/localtime UTC and within "System Settings “Berlin/Europe”.
What is also interesting, especially comparing the scopes within the tokens from @Jecintha and @avc is, that @avc you also don’t have the “offline_access” added there, only in the connected app scopes.
In case of containers set environment variable TZ to the timezone. e.g. TZ=Berlin/Europe.
For frappecloud you may need to contact frappecloud support.
Ideally I’d set the system time and frappe system settings to UTC and local time for every User. It means not set system time at all, most systems use UTC as default. Set “System Settings” to UTC instead of local timezone. (During setup wizard). User can then set their own timezones from their settings.
Or set all timezones ($TZ, “System Settings”, “User”) to same timezone if there is no need for multiple timezones.
Hi,
thanks @revant_one for an advice, we will contact the frappcloud support.
@Patrick.St, we have live version with v2 token URI where are these settings:
Scopes in connected app:
And I have devel frappe site where I have v1 token URI:
Both settings are working as well with server side script for token refresh.
Expiracy calculation is now fixed here:
