jonathanmmm
jonathanmmm
Is maybe related to https://github.com/nextcloud/desktop/issues/2593 ?
My guess when commenting them out, is that the container now internally also uses UTC (could you check that with `date` command inside the container)? And that way no shift...
> well this was what I was hoping for and it indeed does have that effect. It is important to do it on all containers though! > ``` > bash-5.0#...
Ok, problem in my case: I use mysql for a bunch of other services, so I won't put mysql into UTC. But your setup just tells that something is wrong,...
> Well since mysql in docker-compose is deployed as a dedicated microservice which only handles mailtrain data, in my case I don't see a huge problem in chaging system time...
In the UI I only can see something like "1 day ago", which is almost correct. I looked in the database and found the following: | status_change | created |...
Ok, the time shows correctly, after I commented these two lines out and put mysql time to +02:00 (for UTC+2) into /app/server/config/default.yaml instead of local (keeping the two lines not...
@bures What do you think could be the problem and how to fix it or is Mailtrain V2 not supported to run on anything else (and only UTC as the...
I tested it the following way: UTC+2 is my local time I set the timezone for the subscriber as Europe/Berlin (UTC+2) and in the schedule in the campaign I set...
> I don't recall exactly the issues any more, but I would guess the DB or the DB client is the culprit. the DB runs perfectly fine with UTC+2, I...