@joseph Sorry but this was confusing for me.
So I understand that the mx should be removed. (done)
The questions was: I thought I need that MX for the DMAR/DKIM to work?
I did setup that ses MX following the DKIM/DMARC dokumentation....
@joseph Sorry but this was confusing for me.
So I understand that the mx should be removed. (done)
The questions was: I thought I need that MX for the DMAR/DKIM to work?
I did setup that ses MX following the DKIM/DMARC dokumentation....
OH OK so I had an MX record with the SES address in addition to the cloudron one: feedback-smtp.eu-west-1.amazonses.com
Deleted it and it's working again.
Do I not need this for the DMARC/DKIM of SES to work though?
Hey!
I 've set up sending via SES for a domain (sending works well)
However, I now have a problem receiving email:
550 Mailbox does not exist!
Final-Recipient: rfc822; my@email.com
Action: failed
Status: 4.4.2
Remote-MTA: dns; feedback-smtp.eu-west-1.amazonses.com. (IP.IP.IP.IP, the
server for the domain email.com.)
Diagnostic-Code: smtp; 550 Mailbox does not exist!
Pretty sure this used to work and stopped working after setting up DMARC/DKIM?!?
No idea where to start debugging though - any idea?
I'd love to see this in cloudron. Using the online version atm and love it. Finally something that could actually replace google analytics and be self-hosted. Amazing!
Posthog is a pretty mighty analytics platform, mainly for more complex applications like SaaS.
Would it be possible to add it to Cloudron?
Here are the docs for it:
https://posthog.com/docs/self-host
This update broke the chat detail views for me it seems... they are empty and the console is full of errors
@girish yes csvImport folder was there. 1.1 works after deleting it
Let me try ones more, with deleting
Yeah I just tried updating manually again after the rollback
Which seems to be exactly what you reported on github there @girish
Error log via terminal:
[06-Nov-2023 12:52:39 Europe/Berlin] PHP Fatal error: Uncaught Exception: Plugin csvimport conflicts with domain in /app/code/app/Core/Template.php:194
Stack trace:
#0 /app/code/vendor/illuminate/collections/Collection.php(819): Leantime\Core\Template->Leantime\Core{closure}()
#1 /app/code/app/Core/Template.php(197): Illuminate\Support\Collection->mapWithKeys()
#2 /app/code/vendor/illuminate/container/BoundMethod.php(36): Leantime\Core\Template->setupBlade()
#3 /app/code/vendor/illuminate/container/Util.php(41): Illuminate\Container\BoundMethod::Illuminate\Container{closure}()
#4 /app/code/vendor/illuminate/container/BoundMethod.php(93): Illuminate\Container\Util::unwrapIfClosure()
#5 /app/code/vendor/illuminate/container/BoundMethod.php(37): Illuminate\Container\BoundMethod::callBoundMethod()
#6 /app/code/vendor/illuminate/container/Container.php(661): Illuminate\Container\BoundMethod::call()
#7 /app/code/app/Core/Template.php(156): Illuminate\Container\Container->call()
#8 [internal function]: Leantime\Core\Template->__construct()
#9 /app/code/vendor/illuminate/container/Container.php(929): ReflectionClass->newInstanceArgs()
#10 /app/code/vendor/illuminate/container/Container.php(770): Illuminate\Container\Container->build()
#11 /app/code/vendor/illuminate/container/Container.php(706): Illuminate\Container\Container->resolve()
#12 /app/code/vendor/illuminate/container/Container.php(1043): Illuminate\Container\Container->make()
#13 /app/code/vendor/illuminate/container/Container.php(959): Illuminate\Container\Container->resolveClass()
#14 /app/code/vendor/illuminate/container/Container.php(920): Illuminate\Container\Container->resolveDependencies()
#15 /app/code/vendor/illuminate/container/Container.php(770): Illuminate\Container\Container->build()
#16 /app/code/vendor/illuminate/container/Container.php(706): Illuminate\Container\Container->resolve()
#17 /app/code/app/Core/Frontcontroller.php(120): Illuminate\Container\Container->make()
#18 /app/code/app/Core/Frontcontroller.php(74): Leantime\Core\Frontcontroller::executeAction()
#19 /app/code/app/Core/Bootloader.php(368): Leantime\Core\Frontcontroller::dispatch()
#20 /app/code/app/Core/Bootloader.php(165): Leantime\Core\Bootloader->handleRequest()
#21 /app/code/public/index.php(14): Leantime\Core\Bootloader->boot()
#22 {main}
thrown in /app/code/app/Core/Template.php on line 194
So I get a 500 on the login route:
Site was not reachable in browser. Checked the logs but no apparent errors ️
Backup works (Leantime v2.4.5)
@girish My App is broken since update from last night to 1.1. Trying to recover 1.0.3 now to see if this still works.
Great @nebulon that should do. Will check right away!
Not an expert, but the way I'm reading this(https://git.cloudron.io/cloudron/leantime-app/-/blob/main/start.sh) is:
You
Then yes: this explains the behavior.
However, the question remains: how would I update some of the env vars myself so that they are persisted?
I don't think editing your start.sh would be a good idea, would it?
I'm trying to change some vars in the ENV file via the app filemanager.
Unfortunately, when I restart the app (to see the changes) the ENV file gets reset to the default values.
Is this a bug or am I doing anything wrong?
@nebulon so this is fixed with the latest update I guess?
The process kinda comes and goes every second with verious high CPU usages.