Cloudron Forum

None, ever, except whatever iCloud, gmail, yahoo, outlook, or more recently, MXRoute uses. I'm curious about the replies.

Check DNS setting at Registrar. Also, what error messages are given?

@JohnBee said in email server broken after update...:

snapshots to fall back-on

You restored the entire server to a previous working state?

Just like MXRoute!!

@jdaviescoates said in Forward Email with SES, Got "554 Message rejected: Email address is not verified":

Cloudron ought to

This is why I manage my DNS by hand using Wildcard. It's easier figuring out what I did wrong.

@avatar1024 said in Forward Email with SES, Got "554 Message rejected: Email address is not verified":

IPv6 address

Here is an OOLLDD post which says "yes" https://serverfault.com/questions/529121/mail-marked-as-spam-with-spf-record-allowing-servers-ipv4-but-not-ipv6

Something a little more "recent" https://stackoverflow.com/questions/19142369/create-both-ipv4-and-ipv6-spf-record

And from last year: https://dmarcly.com/blog/what-is-an-spf-record-and-how-does-it-work-spf-record-explained

Somewhere in this forum there were questions about what servers with IPv6 with hosting or dns or email, and I believe the usual final response is that if the server has active IPv6, then whatever the tech in question is also has to have that active. If not, then deactivate IPV6 on the server. So, I suspect, now, that your Cloudron is using IPv6 to send email and it is that missing SPF record, ip6: which is causing the issue. Try to fix that and tell us what happens. Remember, DNS can take longer than expected to resolve, so be patient.

@avatar1024 Is 421 4.7.23 your VPS IP?

okokokokok 什么？If you are using the Cloudron email server and set it up to use SES, then the error messages most certainly look like SES error messages, and not Cloudron. Read this: https://docs.aws.amazon.com/ses/latest/dg/mail-from.html Suffice to say, setting up SES well and proper is, in my experience, quite a challenge. It is Amazon who won't deliver your email, not Cloudron.

Have you considered just using the built-in SMTP server? That's what I use, and have not had any problems (i'm fortunate that my server IP is still clean, and I monitor my email sending, too).

Read also http://www.open-spf.org/SRS/. There is a small green box in the upper right corner advising you to "whitelist forwarder IP addresses" in the SPF field. Have you done that in your DNS? It would like something like: v=spf1 a:mydomain.com ip4:xx.xxx.xxx.xxx ~all

Do you have complete control over b@mydomain.com? You can set the various DNS entries?

And maybe you are too focused on a@gmail.com since that's just a test. It seems the main problem is that b@mydomain.com is not forwarding email. If any email is not set up correctly, like a@gmail.com, you can't control. But be sure you can manage b@mydomain.com. Can you? And b@mydomain.com is ON your Cloudron, right? So you are using Cloudron's email server?

Can you verify a@gmail.com? I thought you can verify both an email, or/as well as a domain.

Good luck! Wash regularly, but keep the beard hydrated. The itch for me comes from dry beard hair. Post some progress pics!

It was DNS. Man. So, trying different browsers helped me. First, the errors had a 200 return, meaning the site wasn't reachable. I should have figured it out then. Then using Incognito mode in Chrome came back with a cryptic message, the gist of which was that the "received data could not be verified". So, it was "working", as the Dashboard said, but not working. The Firefox also said something similar. So, I checked the DNS... and discovered I had changed the A records for @ and * to another IP. That was for a similarly named domain!

I fixed this DNS error, and I'm back in business.

A little while ago someone poasted about their Peertube instance not federating. I checked mine. Then I checked my Pixelfed and discovered it isn't even working! Here are the logs:

Feb 08 19:10:20 172.18.0.1 - - [08/Feb/2025:12:10:20 +0000] "GET / HTTP/1.1" 200 1834 "-" "Mozilla (CloudronHealth)"
Feb 08 19:10:23 ==> Running schduler
Feb 08 19:10:24 2025-02-08 12:10:23 Running ['artisan' horizon:snapshot] ..... 459.67ms DONE
Feb 08 19:10:24 2025-02-08 12:10:24 Running ['artisan' story:gc] ............. 424.85ms DONE
Feb 08 19:10:24 ⇂ '/usr/bin/php8.3' 'artisan' horizon:snapshot > '/dev/null' 2>&1
Feb 08 19:10:24 ⇂ '/usr/bin/php8.3' 'artisan' story:gc > '/dev/null' 2>&1
Feb 08 19:10:25 2025-02-08 12:10:24 Running ['artisan' app:transform-imports] 407.80ms DONE
Feb 08 19:10:25 ⇂ '/usr/bin/php8.3' 'artisan' app:transform-imports > '/dev/null' 2>&1
Feb 08 19:10:30 172.18.0.1 - - [08/Feb/2025:12:10:30 +0000] "GET / HTTP/1.1" 200 1837 "-" "Mozilla (CloudronHealth)"
Feb 08 19:10:40 172.18.0.1 - - [08/Feb/2025:12:10:40 +0000] "GET / HTTP/1.1" 200 1832 "-" "Mozilla (CloudronHealth)"

Any suggestions?

@humptydumpty said in Picking Teams for a Tournament:

@scooke said in Picking Teams for a Tournament:

Vikunja's are rather tall for the info inside - you can see after 7 names the bottoms ones aren't visible.

In Wekan, you simply have to scroll to see the rest.

Same with Vikunja, I was just pointing out that at-a-glance is limited if the list is long.

Here is how it might look for Games:

Or don't use the title "Captain" just color code it.

Wekan and KanBoard might have tighter boxes. Vikunja's are rather tall for the info inside - you can see after 7 names the bottoms ones aren't visible. As people change you can then move their Task/name back into the Player list, you can color code who is the new captain for Teams going into Bloodsport Monkey Bars, you can set a Start date on the Task/name to keep track of when someone joined, and if you give everyone their own account they can edit the info in their own task/name!

I used the following image: Photo by <a href="https://unsplash.com/@schmig?utm_content=creditCopyText&utm_medium=referral&utm_source=unsplash">Anderson Schmig</a> on <a href="https://unsplash.com/photos/a-group-of-people-playing-a-game-of-tennis-ViQZi7AZ9aU?utm_content=creditCopyText&utm_medium=referral&utm_source=unsplash">Unsplash</a>

Well, Kanban is just a visual way to track progress or process, but I thought why not make my own Buckets, I don't have to make each bucket a step foward. I'm visually oriented as it is. Here are some screenshots.

@web31978 I don't understand this. You manage the Cloudron, or someone else? Active notifications have that small strip of color to the left. If there is no strip, it's been viewed and presumably acted upon. So, you look at Notifications... and don't act on them? I suppose I might forget, but in that case we have the Event Log, which can show you up to ONE HUNDRED events, to check if something needing action happened or not.

I wouldn't call this misleading, especially since you, the manager, aren't acting on the Notifications, or otherwise making note of what needs to happen. I mean, now you can even get an email notification about these things... will it be Cloudron's fault if your email client flags it as spam and you never see it?

All that said, I suppose having yet MORE options in the Notifications Dashboard would be useful. What will they do next though? The colours give an idea as to what's new, and it's seriousness. Once you've read them the colours disappear but you want something to remain visually that you didn't actually act on it?

@LoudLemur But the point of choosing teams (by one or two ppl only) is to aim for balance. Letting those getting picked the option to decide negates the supposed balance.

Anyway, you could try using something like Vikunja, or anything else that uses Kanban. I already do this with my domains. I make a Project called WEB, and in Kanban view, I make buckets. The buckets are the various VPSes I have. Then I make a new task in any given bucket. The Task is my domain name. I add tags such as Registrar, App, and Server, and use Notes to include info about the current app. I move my domains around often, so it's a visual cinch to just drag the Task/Domain from Bucket1(VPS1) to Bucket2(VPS2) or Bucket3(VPS3). Each bucket has an extra task containing details about that specific server. EVERY Task also has a Due Date which corresponds to the expiry date of the domain or server. Easy reminders!

How this can transfer to you is that you make a project called GAMES or TEAMS, and under it two Buckets, each for one person who will be choosing (Or just Captain 1 or Captain 2 if these people need their names in the Pool). Then, make a bunch of Tasks, maybe start in a neutral 3rd Bucket called Pool, and then as people are chosen you simply move their Task with their name from Pool to the appropriate Bucket1 or Bucket2. Everyone can also see who has moved where.

Good luck!

@nebulon said in How to set-up Firewall and/or Proxy to protect my Cloudron instance?:

if sysadmins know the side-effects depending on the apps used on Cloudron, which a WAF introduces.

Cloudron does SOOOO much for many of it's users already, and meets our needs. This is an important point. It can't necessarily do everything, nor should that be seen as a weakness or deficiency.

@MiddleEndian, what realistic, current, or recently exploited security breaches are you referring to? If you are talking generalities, well, sure, who knows what the next 0-day is going to be. But what likely exploits is Cloudron ripe for?