@nebulon Possibly related... would it be possible to add a column maybe (or even if just a hover message on a user) that would show when the user was last used to login to Cloudron? May be helpful in narrowing down users which should be marked inactive that may have been missed earlier. Essentially good for doing an audit of users. I guess as a workaround we can look at the Event History, however it may not go far enough back.

@girish yes, cool

I second this request, however, is slightly different to the private interface your referencing @girish

x1 server, 5 public interfaces (eth0-5) all with public static IP's.

In my scenario, a client would be assigned a single static IP for all their applications. I'm doing this currently by spinning up an individual VPS on Runcloud for their apps. The main advantage for them is RDNS for their 'assigned' IP address.

Just my 2cents

Just if anyone wants to contribute them self 😉

https://git.cloudron.io/cloudron/box/-/tree/master/src/dns

As you probably have access to the IP of the server, you could simply display a link once the setup is complete in the CLI:

https://<IP>?<token>

So not even copy/paste needed for most.^^

This whole thread is an interesting read - https://dovecot.org/pipermail/dovecot/2020-May/118823.html

@nj said in Issues when using Cloudflare Proxy service for Cloudron:

Even if I'm using Cloudflare DNS Provider using API Token, Cloudron adds an A-Record but the certificate error still shows up because the A-Record is still in DNS-Only mode. If Cloudron gave an option to set the A-Record in Proxy Mode while installing the app, I didn't have to go to Cloudflare and change the record from DNS Only mode to Proxied Mode and wait for DNS to propagate.

This is the best way to do it.

Add the domain in Cloudron with Cloudflare DNS provider Cloudron will always add the A record in DNS Mode. Go to Cloudflare, and turn on proxying. For future DNS changes to this domain, Cloudron has code to "persist" the proxying flag. Just noting this down, since we have code explicitly for this use case.

I agree having a checkbox or something at app install time to enable proxying would be nice.

Sounds super useful indeed!
We could manage all our users centrally and create mailboxes for them too 👍🏻

I will move this to Feature request then.

@fbartels sure. One answer would be separation of concerns. Baserow isn't built to call multiple webhooks after a form submit, whereas n8n is built almost exactly for this reason (among others).

Additionally, as @Sam_uk said, this is a solution that could work right now, without having to wait for additional features being added to Baserow.

That being said, I do love the idea of being able to adjust a payload for webhooks - such flexibility!

@girish 3 if you count the original poster 😉

@nebulon Certainly, implementing OVH’s API would be ideal too. I’m definitely in favour of that. 🙂

It’d still be good to add in the zone feature though for other providers which may not have an API and allow for direct zone edits.

@girish yes

@girish I would say pick and choose what is applicable obviously you would know best it's also worth noting there are CIS benchmarks specifically for Docker Containers which might be a better fit. You could combine the two for better hardening.

https://www.cisecurity.org/benchmark/docker/

https://github.com/docker/docker-bench-security

Let me know what you think

@nebulon because the USER doesn't have a clue. It's the ADMIN that is guiding this process and has to send the info to the USER.

The Admin is the one who sets up the mailbox and has the responsibility to notify the user of how to use it.
Not the other way around 😆

So please make it EASY for Admins to let the users know how to set up Email.

Email the Cloudron user the info as soon as the mailbox is created Copy the details easily so it can be pasted to the user if requested.

@nebulon Many thanks, @nebulon and @girish . The concern wasn't so much that I could not figure out what the status of my certs were external to Cloudron, but more that it would be nice if the area of the dashboard regarding certs would, as a matter of course, just say "You have 47 days remaining, and Cloudron should automatically update your certs in 17 days."

And, if I do mash the button to manually run a cert update, it would be nice to get a response in the dash that says "Success! New certs will expire in 90 days!" (Or, whatever it would say.)

I was mostly surprised that I got a certbot email saying I only had one day left, making me wonder what was up. (I did do a domain registration move at some point, and possibly other things that could have somehow upset the automatic update process. So, this isn't a bug report.) Not having a simple UI response to the act of hitting "update certs" (and instead being dumped into the log) is all I'm poking at.

I don't know how long my personal instance has been running (a month or two now), but it has been a joy. Thank you.

Ok I will mark this as solved then since we already have the feature request for the other mentioned issue.

This would go well with a secondary backup facility for all things Cloudron doesn't currently back up, which is valuable, such as Volumes.

Add a few protocols for this such as FTPS, SFTP, RCLONE, RSYNC, etc..

@mastadamus thanks so much for investigating. I have removed it for next release (7.1) - https://git.cloudron.io/cloudron/box/-/commit/6492c9b71f80120413ff4ae7eefa2f03dc96ea0f

I like the idea of having a summary for all the things (apps, users, domains, mailboxes). Good idea.