Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ERROR: The file named /var/tmp/cert.7EUgVE is unreadable or doesn't exist #105

Open
modernmagic opened this issue May 12, 2021 · 6 comments

Comments

@modernmagic
Copy link

MY CRON:
[email protected]:~/www/modernmagic.com/public_html/cgi-bin$ /home/u16-uwgkceqglfgn/www/modernmagic.com/public_html/cgi-bin/ssl-cert-check -a -f ssldomains -q -x 60 -e [email protected]

EXECUTED SCRIPT
ERROR: The file named /var/tmp/cert.7EUgVE is unreadable or doesn't exist
ERROR: Please check to make sure the certificate for avpack702.com 443:avpack702.com 443 is valid

Can you help troubleshoot this?

@rodgomes
Copy link

rodgomes commented May 18, 2021

I had a similar issue and the problem was the file format, which is not mentioned in this repo but in these docs
https://prefetch.net/articles/checkcertificate.html
Basically, you need to have a SERVER PORT per line (notice the space after server).

@modernmagic
Copy link
Author

modernmagic commented May 18, 2021

Thanks. Where exactly is there a missing space?

My ssldomains file looks like this:
avpack702.com 443
modernmagic.com 443

@rodgomes
Copy link

ah, it does look correct and it works for me if I run:
ssl-cert-check -f ssldomains

Result:
`
Host Status Expires Days


avpack702.com:443 Valid Jun 19, 2021 31
modernmagic.com:443 Valid Jun 19, 2021 31
`

@ryantm
Copy link

ryantm commented Oct 13, 2021

This error message means there was some problem with the openssl but it wasn't caught by the error checking logic.

When I got this problem it turned out that openssl was timing out. I've fixed that one with this PR: #114

A more general fix to this problem would be to output the openssl error message in the event of an error here. Like I did in this commit:

ryantm@589e418

@gilbertosoareslopes
Copy link

Hello,
I am also getting the same problem, how to resolve this?

@leahneukirchen
Copy link

#114 has a fix.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants