@savity normally i just look for the answers to my questions in the forums. Also i won't bump into discussions, but this time i just want to say i totally agree with Savity

Thank you dear Cloudron team for the great support and hard work

What are Canarytokens?

You'll be familiar with web bugs, the transparent images which track when someone opens an email. They work by embedding a unique URL in a page's image tag, and monitoring incoming GET requests.

Imagine doing that, but for file reads, database queries, process executions or patterns in log files. Canarytokens does all this and more, letting you implant traps in your production systems rather than setting up separate honeypots.

and a nice YouTube Video with some explanation...
Youtube Video

https://github.com/thinkst/canarytokens-docker
Not sure if it's something for Cloudron, but at least interesting enough i guess

ps
I didn't use CanaryTokens for this post, no worries

Hi everyone,

It has been a while since this topic was active. But today i payd for a one year license and I am curious if there's any info about Pinry coming to Cloudron?

Greets a big Cloudron fan

Any progress with this, or is it just not something for Cloudron?

I have it installed locally at the moment and must say i'm impressed, it's pretty nice and smooth running

Only thing is i can't invite anyone from outside my local network....

@nebulon thanks for the reply
I'm gonna try out location/domain first..

Will report back if this works for me...

Problem for me after updating to v6.3.4 running on Ubuntu 18.04.4 LTS.
Matrix (Synapse server) seems to be running, but sending messages on Android and Windows not working anymore...

edit:
i moved this topic to https://forum.cloudron.io/topic/5291/problem-with-sending-and-receiving-message-s-android-windows

@girish Thanks a lot for this great support and that you want to take a look at it

It's not a must have, but it come's very handy for monitoring my Cloudron instance and get warnings if something goes weird or reaches high loads.

Netdata is also something i did not think about earlier, so maybe that will workout for me as well.

I must say (apart from this topic), i am really 100% satisfied till so far about Cloudron and the active community that's behind it. Many answers to my questions i did already find here in the forums

Also a big thanks to the Staff of Cloudron, that picks up problems really quick and solve's them as much as they can.

I hope Cloudron will live for a long time in the upcoming future, because it's the solution i was looking for a long time
Really glad i came accros all this and thanks to everybody

Mine was really noticable faster too. Running Ubuntu 18.04 OS here.
Reboot and apps up and running in less than a minute. Like 40 to 45 seconds in total.

Keep up the good work Cloudron staff

@ultraviolet
That would be really really great

@marcusquinn said in ElasticEmail dns record problem... i guess?:

"

Thanks for helping me out and sharing your config..

I did tried it the first time, wrapping the DKIM TXT with quotes .. but that doesn't seem to change it also...
I just rolled it back now just to be sure, so it's wrapped with double quotes again at this point.

I did another test at appmaildev.com to see what they are saying about my records...
funny
Because now the output of every record passed the test with a full green text "Passed" and no Fails at all...

this is the output of that test:
_dmarc.example.com: v=DMARC1;p=none;rua=mailto:webmaster@domain.com;pct=100;ruf=mailto:webmaster@domain.com;fo=0:d:s;aspf=r;adkim=r;
Received-SPF: pass (appmaildev.com: domain of my-name=example.com@bounces.example.com designates 54.36.22.222 as permitted sender) client-ip=54.36.22.222
Authentication-Results: appmaildev.com;
dkim=pass header.d=example.com;
spf=pass (appmaildev.com: domain of my-name=example.com@bounces.example.com designates 54.36.22.222 as permitted sender) client-ip=54.36.22.222;
dmarc=pass (adkim=r aspf=r p=none) header.from=example.com;

Where "example.com" is my actual domain redacted for privacy

SPF: Pass
DKIM: pass
DMARC: pass
DomainKey-Result: none (no signature)
If DKIM result is passed, you can ignore DomainKey result: none
Notice: DomainKey is obsoleted standard, the new standard is DKIM.

PTR: ExistsRecord
RBL: NotListed

Any progress with this, or is it just not something for Cloudron?

I have it installed locally at the moment and must say i'm impressed, it's pretty nice and smooth running

Only thing is i can't invite anyone from outside my local network....

What are Canarytokens?

You'll be familiar with web bugs, the transparent images which track when someone opens an email. They work by embedding a unique URL in a page's image tag, and monitoring incoming GET requests.

Imagine doing that, but for file reads, database queries, process executions or patterns in log files. Canarytokens does all this and more, letting you implant traps in your production systems rather than setting up separate honeypots.

and a nice YouTube Video with some explanation...
Youtube Video

https://github.com/thinkst/canarytokens-docker
Not sure if it's something for Cloudron, but at least interesting enough i guess

ps
I didn't use CanaryTokens for this post, no worries

@girish
Thanks for the info and all the work (support) you have done for me Girish

@girish
Definitely, i will send a message to support@cloudron.io asap.

Thanks for checking up into this

@timconsidine
Now that i'm thinking about that also.
I remember reading something about that in the forums.

That's one problem I can skip off my list

@girish

I have done migrating Cloudron to Ubuntu 20.04 and this is what happend.....

As i spinned up the new VM, i setup cloudron to install version 6.2.8. at the command line.
I downloaded the backup config before i turned off the old vm, so i could use the backup config while restoring.

This turned out REALLY nice, since my bucket is at DO i could restore from there, after filling in my Id and secret.
After restoring, the Cloudron dashboard quickly showed up online and all the apps were restoring.

(edited)
SOLVED!! BECAUSE IT TAKES TIME TO REFRESH THE STATS-->
Ok, so i went for some (basic) checks and discovered that after the restore, the "system info" tab still showed the old values from the old VM. As in disk space was showing the old values.
Strange because i started with a new fresh VM and more disk space assigned to it.
I tried rebooting Cloudron, but that didn't help either. <-- SOLVED!! BECAUSE IT TAKES TIME TO REFRESH THE STATS

Also if i try to update "Collabora Office" (for example), it loses connection (integration) with Nextcloud.
Same is also for "OnlyOffice" that loses connection after updating.
If i restore them to the version before the update, everything is working ok again.

Ok so not really smooth running at this point, but this also happend before i did the migration, when it was running on Ubuntu 18.04.
So i thought let's try updating Cloudron to 6.3.4. since i was already on Ubuntu 20.04 now and maybe it could solve my problems from there....

Well that also didn't catch the problems i already had, it even became worse.
After the update, Elements was working for like 10/20 minutes and again i could't send message's from the Android app.

It seems like everytime i try to update an app or the whole Cloudron environment (version), things are breaking.

I went back to the old Ubuntu 18.04. VM with Cloudron 6.2.8.
That's my only stable Cloudron at the moment.

I'm out of idea's at this point and can't detect were it's failing....

Help?

@girish
Thanks for the support.
My weekend is started now, so i can finally dig into the problems i had.

I'm going to first spin up a new Ubuntu 20.04. VM.
Then install Cloudron version 6.2.8 on that.

Restore backup from the old Ubuntu 18.04. version 6.2.8 to the newly created Ubuntu 20.04 VM.

If that's running smooth I'll give it a shot to upgrade to 6.3.4. and see how that goes. I'll report back on that.

If Nextcloud sync is still bugging me after updating, i shall open a separate thread for that one

@girish
Sorry for the late reply, work is killing me at the moment...

All sort of things happened actually after updating on Ubuntu 18.04 from version 6.2.8 to 6.3.4.

A lot of things are covered already in the forums, like the "reboot button" didn't work and so on.

But he main problem i had, was Element's throwing out errors and was offline, on Windows and Android clients. I made a post about it recently.
https://forum.cloudron.io/topic/5291/problem-with-sending-and-receiving-message-s-android-windows/3?_=1626202967742

Also i discovered that Nextcloud doesn't sync no more, even not after trying to re-enable sync on the client side, like Nebulon suggested.

Now i'm still running on Ubuntu 18.04 and Cloudron version 6.2.8. and everything seems to be running ok. Except Nextcloud that doesn't sync from the mobile app...

@nebulon
Thanks i really appreciate your explanation.
Give me a couple of days to sort some things out and i report back asap of this works for me.

i guess i better keep an eye on it and look if it runs smoothly on the newly created Ubuntu 20.04 VM, before updating to 6.3.4.?

@timconsidine
Thanks for the answer.
I tried it like a year ago and that worked out really good.
Only thing then that al versions, like the running Cloudron version and Ubuntu version stayed the same when i did that a year ago.

I'm not sure if it wil work this time...