@THI_Staff Apologies for a late response on this. I haven't used this yet. I was grandfathered on some free monitoring elsewhere. That being said, some of the delivery reports tell you servers that attempted to send email on your behalf. That has helped me resolve some delivery issues where others were sending legitimate emails, but using one of our email addresses instead of theirs. That tripped a DMARC fail. I would start their service without and then see if you want more.
@matix131997 my understanding is that issuance from E1 requires whitelisting of your LE account - https://letsencrypt.org/certificates/ . This is why ISRG Root X2 is still limited availability.
Can you try pulling that image manually using docker pull registry.docker.com/cloudron/g raphite:3.4.2@sha256:bc30121baecfa887856de56278fca5a532543c8ff439b60dc178132d578 ?
@pixeltablet as long as the DNS settings are copied over to cloudflare, everything will continue to work.
You can also make Cloudron add the DNS entries into Cloudflare by first switching to cloudflare and then sync DNS - https://docs.cloudron.io/domains/#sync-dns . Just so you don't hit any DNS issues, you can add the 'my' subdomain record manually into Cloudflare.
I thought I would just restart the server in case that fixes things after the weekend. The dashboard came up and I was able to start troubleshooting the unresponsive apps. I guess this is one of those things that cloudron fixes itself with those health checks. Thanks
The full solution is :
First run (as-is): mysql -uroot -ppassword box -e "delete from blobs where id='sftp_private_key' OR id='sftp_public_key'"
Then, /home/yellowtent/box/setup/start.sh to complete the migrations
Then, systemctl restart box
@girish said in trying to use cloudron openid connect with cloudflare0trust:
@
ok i tryed that.
only problem, it keeps changing the token, the zero-trust does. everytime i put it in, it puts like 34more bullets (what i hear on the screen reader when trying to enter) in the tokens field.
@saikarthik said in Incoming email not being received:
I had to re-add the entry for netlify load balancer in my DNS.
Maybe next time lead with that. The use of „netlify load balancer“ seems to be some vital information while people are trying to guess-troubleshoot your DNS problems….