G
@humptydumpty thanks.
Just as an update: we found that for some reason, the docker containers (any of them) are unable to reach any port other than port 443/80 using the public IP. From the server itself, all ports of public IP are reachable... Have to debug this further tomorrow.
@humptydumpty the docs are a bit outdated since FS has changed the Encryption options. I will fix that once we resolve this... I am out of ideas now though. Can you send us an email to support@cloudron.io with the domain? It must be something very obvious because our FS works.
@humptydumpty the system email is configured by cloudron itself. You can ignore this (for this problem).
One thing in your screenshot: I noticed now that FS has changed it's TLS options (very nice). You have to choose STARTTLS for port 587. In yours it is none.
@humptydumpty are you using Cloudflare? I can't think of any other reason
@humptydumpty not sure how the firewall works but maybe when you enable one rule, it blocks all others . So , you have to open port 80 and port 443 as well.
@humptydumpty just incoming
For exec, you can do cloudron exec --tty sh . cloudron debug <cmd> . cmd needs to somehow "hang". If you have sleep in your Docker image, you can do cloudron debug sleep infinity.
There was some legacy commander parsing code in our CLI. Luckily, commander now supports variadic args and I have fixed our CLI and published a new version 5.12.0 . Can you check with that?
doc link - https://docs.cloudron.io/apps/#app-proxy
PocketBase is an open source Go backend that includes:
This was published a while ago and was then removed because it used SQLite and Cloudron's didn't have a sqlite backend to make proper backups. Sqlite addon is now in Cloudron 8.2 and thus the app is now re-published.
Thanks to @TheNils for the app package!
The forum section is at https://forum.cloudron.io/category/189/pocketbase
And the package repo at https://git.cloudron.io/packages/pocketbase-app
@humptydumpty said in Connection could not be established with host mail.domain.com [Connection timed out #110]:
Should I manually enable ports 587 and 993 in Hetzner's firewall regardless?
Oh, this could be it. Are you using the full name in freescout like mail.domain.com ? If so, external ports have to be opened. I guess you got the blocking of those ports from somewhere in the docs? We should probably add some caveats to it.
@humptydumpty just double checking, have you seen https://docs.cloudron.io/apps/freescout/#cloudron-mailbox already? Important thing here is TLS vs SSL distinction in freescout. I remember writing about this somewhere in the forum, let me see if I can find it. I think everything looks fine in your setup, just some freescout configuration.
@Dave-Swift I was merely removing Cloudron out of the list of suspects 
You probably did this, but have you tried host -t PTR <ip> already? For example, host -t PTR 45.55.2.141 returns my.cloudron.io . This helps figuring if it's the tools at fault or if the entry itself is wrong. If entry itself is wrong, only Hetzner can fix this since they own the IP and thus the DNS space for the reverse.
