-
Notifications
You must be signed in to change notification settings - Fork 30
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
Pingap in docker does not create certificate correctly by acme #85
Comments
I'd like to add onto this again, still seeing:
Regardless of Docker environment, I've tried EFS, NFS, S3, bare-metal docker, nothing is fixing this error. |
|
It can be confirmed that the TLS version supported by the client? |
Are there multiple pingap instances? |
The host is |
Just one. I cannot get it to generate at all. I think the Docker version is borked as fuck. |
Does pingap have write permission to this directory? |
Yes, it does, or it wouldn't be able to write the conf directory, or any of the conf toml. |
Can you get all logs of acme? You can use grep And please confirm whether the folder
|
No this is what I have been saying /opt/pingap/conf/pingap-acme-tokens doesn't exist, isn't created. |
In short: |
OK, I'll test the docker image. |
Please try to add |
Does it work? |
No sorry, it does not. |
Can you grep the logs using this 2025-01-28T13:00:38.125152944Z ERROR failed to get certificate category="acme" error=Let's Encrypt operation failed: X509 error, category: parse_x509_pem, Parsing Error: MissingHeader, category: new_certificate name="pingap"
2025-01-28T13:00:38.125159113Z INFO acme from let's encrypt category="acme" domains="pingap.io"
2025-01-28T13:00:38.125229746Z ERROR certificate renewal failed, will retry later category="acme" error=ACME instant error: no native root CA certificates found (errors: []), category: create_account domains="pingap.io" name="pingap" |
Is the problem solved? |
This issue has been closed because it has been stalled with no activity. |
-> http://staging.swiftpress.io/
The text was updated successfully, but these errors were encountered: