This is taken care of now via support ticket.

@girish Mailgun. It hasn't happened again (so far). BTW, the notification error listed only two out of ten domains (all using Mailgun).

@girish perfect! Thank you so much! I really highly appreciate the effort! Thanks! I see it now!

@nick We have deployed a (possible) fix now, can you please try again?

@perler We replied from support@ now, can you please check? For future reference, the approach is: Login to cloudron.io with your old account. Delete the cloudron instance there. This will disassociate your existing Cloudron from cloudron.io Then, go to your Cloudron dashboard. If you refresh the page and go to Appstore view, it will ask you to relogin. Just relogin with your new cloudron.io account. If your new account has a license, it will automatically get reassociated. If this doesn't, please send us a note on support@ and we can fix it up.

@girish thanks for the support. Now they are available in the app section .

@kk_cloudron that is correct, Cloudron requires IPv4 and does not work on IPv6 only servers (yet).

Not sure how related this is, but my SSHFS mounts are also not working, recently. Just saying.

@subven I not joe lol I just search this forums and found this and same as my server showing but it worked my side now:) Thank you and I do not know about his side yet

@girish I had something similar with navidrome too when an update broke a volume mount.

Just solved it by adding RUN ln -sf /app/data/env /app/code/.env to my Dockerfile, my env is linked in the code folder and works as intended. this topic may now be closed.

@girish that did the trick, thank you

@girish said in Domains and existing email configuration: It is possible to setup Cloudron to receive emails on a subdomain though (like email.example.com). For this, add email.example.com in Domains as well and then you can enable incoming mail for that domain. This is exactly what I was looking for. I didn't know I had to add that additional email.example.com to the list of domains configured in my Cloudron instance. Thanks a ton.

@dylightful Something definitely happened on Cloudron side and It's hurting me in full swing, I'm having a hard time to find the origin of this, it does not make any sense. current operations at osintukraine.com are fully impacted, each of our telegram archive are now disconnected from their volume, already tried to clean start, new mounts, clean start, same problem. Right now I'm trying to add a new sshfs volume, the target is empty, i'm still having this exact same error, I'm wondering if there isn't anything else going on here because nothing make sense.

@L3oN We don't support installing other software on Cloudron. It will interfere with future updates to the platform. Does IPB forum work in a LAMP stack? If so, you can deploy it inside the LAMP app on Cloudron.

@subven Sorry I wasn't clear on the domain thing. It's fixed now so no worries. I do have email working. I disabled mail in Cloudron (I don't see a use for it as it is just me), and redid the dmarc and other records that Google requires.

@RoboMod said in Restore backup doing nothing: "$scope.backupFolder https://forum.cloudron.io/topic/6388/scope-configurebackup-is-undefined/12 was the thread

The same error message was previously discussed in https://forum.cloudron.io/topic/6895/the-site-is-deceptive. Based on the current information it seems the real value behind idontwantdomaintobepublic.shop has triggered some potential scammer alarm at Google.