Cloudron Forum

I found a solution to this issue. I created and downloaded backup of data inside of Snipe IT (zip file from it's backup feature), uninstalled Cloudron app, reinstalled cloudron app, and restored from the zip file. All seems to be working now.

Yes, this is running on Cloudron. The zip backups are a function inside of Snit-IT. I just tried running a test upgrade again this evening and I'm still getting the same behavior.

Would also love to see this

I had a strange issue come up after the update to verstion 1.8.4. My technicians lost the ability to view asset history, maintenance, and all other tabs when viewing an asset. Only accounts with Admin permission were able to view them. I made a backup zip in Snipe, rolled back to 1.8.3, and restored zip backup. This solved the issue.

Here's my header showing the SPF failure. I'm using mxtoolbox.com for testing. I'm also using Sendgrid as an SMTP relay with an API key. Sending domain is different than the MX domain as I have a couple different domains I send email from.

Received: (Haraka outbound); Sun, 07 May 2023 15:40:12 +0000
Authentication-Results: mymxdomain.com;
auth=pass (plain);
spf=softfail smtp.mailfrom=sendingdomain.com
Received-SPF: SoftFail (mymxdomain.com: domain of sendingdomain.com does not designate sending client public IP as permitted sender) receiver=mymxdomain.com; identity=mailfrom; client-ip=sending client public IP helo=[LAN IP]; envelope-from=<mailbox@sendingdomain>
Received: from [LAN IP] ([sending client public IP])
by mymxdomain.com (Haraka/3.0.1) with ESMTPSA id 6F7C9FA2-9E4D-4C74-932F-D177277F2FCC.1
envelope-from <mailbox@sendingdomain.com>
tls TLS_AES_256_GCM_SHA384 (authenticated bits=0);
Sun, 07 May 2023 15:40:12 +0000

@ccfu It's the recipient's server that's showing the sending client's IP in the header. Mail is going through ok besides getting a soft fail on SPF and raising spam score

@ccfu I'm seeing the sending clients IP address in the headers instead of the cloudron SMTP server. This causes an SPF failure as the client IP isn't an authorized sender for the domain.

I would also like to add that I have been seeing this behavior as well. I am getting SPF failures for IP mismatch as the header is showing the IP of whatever client is sending email, not the SMTP server.

If I were to migrate my Vaultwarden to a different (non-Cloudron) docker environment. Could I just copy the contents of it's appdata/xxx-app-id-xxx/data folder into the the new data folder of the new container?

@ei8fdb Firefox does take some extra configuration. You have to install a CA cert into the android store via the Adguard app, enable secret options on Firefox app (go to about Firefox and tap logo 5 times), enable use of third party certificates.

For DoT on the Adguard Home side check encryption settings to configure domain names and certificates.

@ei8fdb In the latest release of Android there is an option to specify a private DNS resolver. If your device does not have that option available, the Adguard app acts as a VPN and can provide secure DNS lookups