This is because of IMDSv2 . Make it optional like below and it should work:
We will try to make it work with IMDSv2 in next release.
Translators
This is because of IMDSv2 . Make it optional like below and it should work:
We will try to make it work with IMDSv2 in next release.
If you really want totally separate mailboxes, then create separate mailboxes on Cloudron. Then , login to SOGo as john@mymainbox.com
. Then , Settings -> Mail -> Imap -> add account. You have to add otherdomain1.com , otherdomain2.com etc manually. SOGo has a limitation that it can store only one IMAP password from what I remember. It will always use the IMAP password of the initial mymainbox.com acount (SMTP has separate passwords). This means that on Cloudron side all the mailboxes must have the same owner...
Like:
It then appears in your main ui like so:
@JohnBee On Cloudron side, mailbox means a receiving endpoint/storage. alias is like a sticker label to this endpoint/storage. aliases can be from another domain. so, in your setup, john@mymainbox.com is the only mailbox. Rest john@otherdomain1.com, john@otherdomain2.com are aliases. When you edit mailbox -> Add Alias -> note the domain is a dropdown (I know it's a bit tricky to get this...)
SOGo on Cloudron has alias integration. So, you don't even need to add identities. The aliases are automatically picked up inside SOGo (you can choose in the From drop down).
I tried to look into mailcow docs as to what aliases mean but I didn't find any relevant docs. Do you have a link where we can read more?
Hello everyone,
PairDrop is now available as unstable app package.
File sharing on your local network that works on all platforms.
Code: https://git.cloudron.io/cloudron/pairdrop-app
Docs: https://docs.cloudron.io/apps/pairdrop/
Forum section: https://forum.cloudron.io/category/193/pairdrop
This is published in unstable . Please report any issues in the new app category.
We haven't added a way to add custom persistent iptables rules . For SSH though, just move it port 202 and disable root auth and password auth. This usually cuts down all bots to 0.
Just so we talk about the same thing... Cloudron has an internal network 172.18.0.0/16 . These IPs never leave the server. It's only a problem if your own internal network is also using these IPs. Is that the case? Generally, the docker stack uses 172.17 or 172.18 and the private networks use 192.168 (home) or 10.0 (enterprise). Very broad generalization yes.
I do know that the train network here (DB) uses 172 and it conflicts with Cloudron's network... It's kind of annoying when connecting to their wifi.
yes, the automated tests broke, so we are fixing that first
Discourse is more popular than NodeBB for sure. I think it's best to just try out various public forums and decide for yourself. NodeBB based forums are probably harder to find than Discourse ones (atleast for tech forums). The Qt Forum is nodebb though (https://forum.qt.io/)
https://krebsonsecurity.com/2024/07/phish-friendly-domain-registry-top-put-on-notice/
In case you use .top domain, now might be a good time to move out.
Also, freenom apparently went out of business after being sued by meta - https://krebsonsecurity.com/2023/05/phishing-domains-tanked-after-meta-sued-freenom/ .