Thanks all. This issue was already fixed as well last month - https://git.cloudron.io/cloudron/box/-/commit/67cde5a62cf0394c8bf2d78ee3408e5995a220e7 . It's already in 7.3.5. Essentially, if you have CIFS/NFS/SSHFS, there is a crash.

@girish said in How to upload/import app backup in Cloudron: Can you make a feature request and link to this post? Filed it here: https://forum.cloudron.io/topic/8359/ability-to-import-backups-from-computer-disk-rather-than-needing-to-scp-files/1

@imc67 yes, this one is only fixed in 7.3.5 . Still waiting for the fix for the graphs and mailbox listing issue to get that out.

okay, i'll try it running on ubuntu using virtual machine.. .

@girish It is working now! I've found a good doc from Namecheap themselves: Namecheap DOC about Sendgrid It's important to not add the domain part in the CNAME entries! Hopefully this helps someone else in the future Thank you for your commitment @girish

@girish said in Ways to free up space?: 28GB of data does seem off. Yeah, I've got 48 apps running and mine is only 4.11GB (if my.cloudron.coop/#/system is to be believed - have all sorts of issues with it so I don't really trust it at all, see https://forum.cloudron.io/post/58715 )

@nickbeswick Can you explain your setup a bit more. I assume Nginx Proxy Manager (NPM) has the public IP address and Cloudron is in some internal network? I think something like this https://forum.cloudron.io/topic/5898/nginx-in-front-of-cloudron-install/9 . Put the IP address as internal IP and also add the domain name.

Ah, I guess the error message could be more descriptive. Currently there is a hard-coded allowlist of paths on the filessystem to be used as volumes, to avoid accidents where someone might add system folders. The list is at https://git.cloudron.io/cloudron/box/-/blob/master/src/volumes.js#L57

@andreasdueren said in How can I block email addresses in catch all?: I thought these addresses are only checked for in the from fiel not the to? No, to the best of my knowledge it applies to any addresses in the mail. In any case this is how I prevent these kind mails from popping up in my mailbox. @subven said in How can I block email addresses in catch all?: via a mail sieve filter That could work as well, but another mailbox is not necessary. You can just filter on the recipient address.

Glad you managed to resolve this. Some ago we changed the REST api there which probably caused this issue when using an outdated cloudron cli tool.

@fbartels ! i got there just as you were hitting send i think i was cloudflare, and it wasn't working -yet- because i had an OR where I should have had an AND 🥴 but I GOT THERE. damn that feels good. thanks for your help

Cool. Thanks for the definitive answers all. Cheers.

OK, I have fixed the unbound issue with IPv6. It's an upstream bug but I have made a workaround for the moment. Fix will be part of 7.3.5 (released next week).

This is fixed in 7.3.5 (will be released next week).

@girish said in Restrict Dashboard Access - Cloudron v6.1.2: @potemkin_ai UFW and Docker are not compatible. I haven't looked into the repo you linked yet. I didn't test the solution yet, found it with people referring as a working one, so I have hopes. The idea is to modify /etc/ufw/after.rules to contain: # BEGIN UFW AND DOCKER *filter :ufw-user-forward - [0:0] :ufw-docker-logging-deny - [0:0] :DOCKER-USER - [0:0] -A DOCKER-USER -j ufw-user-forward -A DOCKER-USER -j RETURN -s 10.0.0.0/8 -A DOCKER-USER -j RETURN -s 172.16.0.0/12 -A DOCKER-USER -j RETURN -s 192.168.0.0/16 -A DOCKER-USER -p udp -m udp --sport 53 --dport 1024:65535 -j RETURN -A DOCKER-USER -j ufw-docker-logging-deny -p tcp -m tcp --tcp-flags FIN,SYN,RST,ACK SYN -d 192.168.0.0/16 -A DOCKER-USER -j ufw-docker-logging-deny -p tcp -m tcp --tcp-flags FIN,SYN,RST,ACK SYN -d 10.0.0.0/8 -A DOCKER-USER -j ufw-docker-logging-deny -p tcp -m tcp --tcp-flags FIN,SYN,RST,ACK SYN -d 172.16.0.0/12 -A DOCKER-USER -j ufw-docker-logging-deny -p udp -m udp --dport 0:32767 -d 192.168.0.0/16 -A DOCKER-USER -j ufw-docker-logging-deny -p udp -m udp --dport 0:32767 -d 10.0.0.0/8 -A DOCKER-USER -j ufw-docker-logging-deny -p udp -m udp --dport 0:32767 -d 172.16.0.0/12 -A DOCKER-USER -j RETURN -A ufw-docker-logging-deny -m limit --limit 3/min --limit-burst 10 -j LOG --log-prefix "[UFW DOCKER BLOCK] " -A ufw-docker-logging-deny -j DROP COMMIT # END UFW AND DOCKER Why not just enable 2FA on the dashboard? It's a different security layer. 2FA relies on the code, which is much more complicated, as opposed to network level filtering. What is more complicated could have more issues. So, whenever possible, I close any code from outside access - everything have bugs, some of them are in security space, even if you are OpenBSD Do you believe this could become part of the system? I would really like to deny from all with allow from xxx.xxx.xxx.xxx with periodic firewall disable for let's encrypt.

@Vladimir Sounds like a popular site with lots of traffic. Sounds like you found one reason to be the translation plugin. You should be able to view the apache logs and monitor for errors, similarly for long DB calls which might make things wait, but then you'd notice site slowness from that too.

@AgentM which dns provider are you using? If you go to Domains -> Renew all certs, can you check the logs as to why it is it not getting the certs?

@nebulon Thank you, I will investigate today and let you know.

@brandthedwarf I finally did it. I'm not a technical person and just followed the instructions running it locally