Closed JueFri closed 7 months ago
I think the 308 is indeed Caddy redirecting from plain HTTP to HTTPS. The acme_tiny.py client is trying to read the .well-known file using HTTP, but Caddy seems to redirect to HTTPS which acme_tiny.py does not follow.
You should try configuring Caddy so that it does not redirect if the path starts with "/.well-known/acme-challenge" or so. The acme_tiny.py seems to be hardcoded to use plain HTTP only.
Thank you very much for your quick reply.
Currently i dont known how to follow your recommendation but i will start to research and then i will report back.
Your thought was correct - redirecting from HTTP to HTTPS through Caddy Reverse Proxy resulted in Response Code 308.
I was able to completely avoid using the Caddy Reverse Proxy for the website pki.hds12.de.
Now I can access the LabCA website without any errors.
Many thanks for your support.
Sincerely Jürgen
First of all i would like to say thank you for creating this software.
I used a Debian 12 Bookworm unprivileged LXC container on Proxmox and installed the software (v24.03) based on the Install section of the README file on GitHub with the command
Everything seems to be ok and the 6 docker containers started up and running fine.
I prepared the my nameserver und the reverse proxy Caddy to access the application via the browser.
After the base install i went through the setup in my browser to finalize the installation process and i got the following error message " OOPS - Some unexpected error occurred! ..." and the Response Code: 308.
I am not shure if 308 stands for Permanent Redirect and what that could mean in this context.
Any help is appriciated.
Best regards Jürgen
Diagnostic information.
/home/labca/nginx_data/ssl/acme_tiny.log
(control)/logs/commander.log
docker compose logs control
docker compose logs boulder
docker compose logs labca