@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.

@girish said in Backup size: Thanks, I deleted files in the Nextcloud recycle bin. Now, after a reboot, Cloudron System Info shows 4.3 GB for the Nextcloud instance. (I had to delete the nginx config of a stopped app to get the system to reboot.) Thanks, I'll keep both folders. I have no particular goal to remove Discourse or its backups. I measured /var/backups size by adding up the three separate folders that FileZilla showed me, but I now understand that some files are hardlinks. And the Backup data shows only 4.87 GB now, so my disk is small enough for me to move on. Thank you!

I created a new SMTP user and used that in the second Cloudron. Worked like a charm. Thanks!

@girish I just tried a free VPN service and the domain loaded but on the other computer without a VPN it did not load so I am thinking it is a problem with my ISP. I'll let you know how I make out with it.

@scooke I went to each individual app and pointed to the fileshare with the full path "/media/fileshare/2020-07-01-0500/app_backup.tar.gz.enc" and restored those backups. As for the second part, Azure adds the following "actimeo=30" switch to the cifs share that goes in your /etc/fstab file that causes the connection to time out if the backup takes too long. Once that is removed, reboot the server and the new backups will complete without issues.

@Mastadamus yes, reverse proxy is implemented in next release (7.3) - https://forum.cloudron.io/topic/6655/what-s-coming-in-7-3/21

@zylstra right, we removed the version in the default footer.