Cloudron Forum

Looks like there's a way to self-host with docker:
https://docs.standardnotes.org/self-hosting/self-hosting-with-docker

I've got a couple of mailing lists that started bouncing with a response like Error: Nowhere to deliver mail to for domain: undefined (full sample below). I couldn't find a related question after a quick search so posting here.

After some digging it seems like the issue is that I've got the mailing lists pointing to aliases instead of the original email addresses for the intended recipients. When I swap in the actual username-emails it works fine.

This just stopped working recently. I'd intended to use the aliases in order to prevent the cloudron login username from leaking, but the error message below actually says the issue is delivering to username@undefined versus alias@undefined, which kind of defeats that purpose.

To reproduce:

1. Identify two users to test with: user_a, user_b.
2. Create alias alias_a for user_a in a domain (e.g. example.com).
3. Create mailing list my_mailing_list in same domain.
4. Configure two recipients in mailing list: alias_a@example.com, user_b@example.com.
5. Send a test message to my_mailing_list@example.com.
6. Observe user_b receives the message, but alias_a / user_a does not, and sender receives an error referencing user_a instead of alias_a.

Expected behavior:

1. alias_a can receive the message.

The error message:

Hi. This is the Mailer program at my.example.com.

I'm afraid I wasn't able to deliver your message
    "{{email_subject}}"
to the following addresses.

This is a permanent error; I've given up. Sorry it didn't work out.

Intended Recipients: <{{user_a}}@undefined>
Failure Reason: Error: Nowhere to deliver mail to for domain: undefined

Just stumbled onto BookStack and it looks like it'd be a great wiki. I'd much prefer this over dealing with Dokuwiki.

@Hillside502 embarrassing, yeah I accidentally posted here thinking it was the wishlist. I’m on mobile and can’t see a way to move the topic over... @girish, can an admin do that?

I'm planning to colo a small server to host my cloudron, and want to make sure I've got it secure enough without getting in the way of Cloudron. I'm going to follow most of the advice in the Cloudron security guide. Beyond that, there are a few other things I can think of:

• Enable livepatch
• Run something like this Ansible hardening role. I need to know if any of these things would conflict with Cloudron:
  • Allowing only signed packages
  • Removing a few packages
  • Removing setuid bits from a few binaries

During setup, does Cloudron already do any of those steps anyways, and / or would they conflict with Cloudron (e.g. does it rely on any unsigned PPAs)? As much as possible, I'd love to rely on Cloudron to handle this so I don't have to think about it.

Don’t the log lines have time stamps that would make each unique? If not, cat log.txt | sort | uniq is another handy one-liner. If so, you could throw cut in to split the line.

Following up with a couple of links:

• BookStack supports ldap
• There's a community-built docker image

I’m running into this issue as well. Did you ever find a solution?

For what it’s worth, I’ve been happy with Joplin over the past year with plug-ins and a good theme. I’m sure other solutions are more polished, but at least you own your data, it’s open source, and Cloudron has the sync server in the app store. Hopefully those first two points remain true moving forward.

It seems like something's wrong with the latest round of updates. I'm on OnlyOffice 5.5.1 (Package v1.1.1) and Nextcloud 18.0.2 (Package v4.4.0). When I try to load a document or spreadsheet, I get a notice that the "editor version has been updated" and the page tries to reload but never does (see below).

I've tried restarting both NextCloud and OnlyOffice, tried reinstalling OnlyOffice, tried a different browser, and double-checked the configuration steps from the Cloudron docs -- none of these seems to have fixed it. Has anyone else noticed a similar issue?

.