Closed ulrichSchreiner closed 7 years ago
Does it still happen if you take out the header
directive?
hard to say as it is not really reproducable :-). but i changed my playbook and rolled out a new version of the file. and i will set a reminder to give you feedback in about a week (if nothing happens). or earlier :-)
Great, thanks!
hi,
the server is running without problems since a week now. normally i had this issue at least once a week so i think the removal of the header helped. well it is not a hard proof but an indication.
i will close the issue. it the error happens, i will reopen it.
Sounds good, since I think it is fixed on master if it indeed is the header directive. https://github.com/mholt/caddy/commit/14500d8204c806edc69daa1725df7c68aa6f6347
(Are you asking for help with using Caddy? Please use our forum instead: https://forum.caddyserver.com. If you are filing a bug report, please answer the following questions. If your issue is not a bug report, you do not need to use this template. Either way, please consider donating if we've helped you. Thanks!)
1. What version of Caddy are you running (
caddy -version
)?/ $ /usr/bin/caddy -version Caddy 0.9.3
2. What are you trying to do?
Proxy'ing request to a backend server
3. What is your entire Caddyfile?
i have multiple of this configs for different servers. all of them are identical except the backend-proxy-url.
4. How did you run Caddy (give the full command and describe the execution environment)?
Caddy runs inside a dockercontainer (alpine) with this command:
usr/bin/caddy -conf /etc/Caddyfile -agree -log stdout -port 80 -email ...
5. What did you expect to see?
Proxied requests
6. What did you see instead (give full error messages and/or log)?
7. How can someone who is starting from scratch reproduce this behavior as minimally as possible?
I don't know. this happens sometimes once or two times a week. not regularly.