brookt

Are there any updates to this issue? I am experiencing the same problem with the exact same errors in the browser console. Thanks.

I do not see the directory 20 in either blogs.dir or in uploads.

That directory does not exist.

Parameters of non-admin account.

If it is an account owned by an admin, everything is backed up.
If it is an account not owned by an admin, then only the db is backed up.

I think I spoke too soon and the fact that it worked was due to a previous acceptance of the certificate warning.

Everything I see regarding wildcard certs says they protect all the subdomains(*.wp.example.com) but nothing indicates they protect the “root” domain(wp.example.com). Even wordpress.com has two certificates depending on where you login. If you login at wordpress.com, its cert is for wordpress.com. If you login at site.wordpress.com, its certs is for *.wordpress.com.

However, it appears you can add a Subject Alternative Name (SAN) when the cert is created. Adding *.wp.example.com as a SAN to our wp.example.com certificate worked.

Links regarding SAN:
SAN Link 1
SAN Link 2

Thank you. I was forcing ssl login but was using the cert for wp.example.com instead of *.wp.example.com

I switched to the wild-card certificate and everything works.