We discussed this problem here, I had this problem just few days ago:
https://forum.cloudron.io/topic/12632/tarextract-pipeline-error-invalid-tar-header/
Hi @fbartels
You're right, double checked and it always defaults to smtp. instead of .my
When manually changing on both PC and Mobile, the SMTP accounts can be added without the certificate error!
Thanks Everyone!
The log you posted does not show any real errors
Could you maybe post the whole box.log?
If too long for a post you can put it in here https://paste.cloudron.io/ and share the URL to the paste.
@d43m0n1k_sek said in Unable to load dashboard - fresh install:
I know this post looks more like a blog
And that is totally fine, even more, it is very much welcome.
Sharing your experience and walkthrough while having the problem is very beneficial to other users.
So please, keep going!
I do the same e.g. https://forum.cloudron.io/post/43733
@mouse77 you should be able to just use the domain as it is shown in your screenshot, if you own that domain and can change the DNS records for it at your nameserver provider.
For wildcard usage, you need to setup 2 DNS A records as a minimum. One for cloudron.indesigner.net and another one (the wildcard) for *.cloudron.indesigner.net . Both are A records and should point to your server's public IPv4 address.
I finally got to understand IPV6, and now I spoke with Comcast business to set reverse DNS my IPV6 to my.richardapplegate.io then mail will start working again.
@d19dotca said in Shouldn't we get an alert when a service container fails / is unhealthy?:
checking so that it ignores any entries of the current Docker networking ranges such as 172.18.xxx.xxx addresses
For the moment, I have added validation to not accept such addresses . Ignoring this properly is more complicated (since we have to filter it at apply time) but atleast it won't let you save the blocklist easily .
@mrhakash said in Outbound Emails Queued — NXDOMAIN Error and Local DNS Resolution Issue:
dig @127.0.0.1 gmail.com mx returns:
connection refused
You have to check host -t MX gmail.com 127.0.0.150 . Can you also run cloudron-support --troubleshoot for hints?
It seems to be indeed the long volume names. This also explains the strange connection between setting up a backup and the changing view. Thanks for the explanation. I have not seen this connection...
Cloudron will call the app locally by the URL http://${app.containerIp}:${manifest.httpPort}${manifest.healthCheckPath} so by local container IP at the specified httpPort and healthCheckPath specified in the CloudronManifest.json. Any response with a 200 status code will be accepted.