Caddy Lab / Setup Examples

[zzz (B Murphy)]

@francislavoie I’ve got to say from what I’ve seen so far this is one of the best run foss software forums I have seen – you are really on top of things! Can you please move my “Thank You” post to Caddy + Cloudflare tunnel along with the post that you moved. – Thanks.

@francislavoie

I have a problem with the default, as someone who answers questions on the forums. Lots of users post truncated logs, which are entirely useless because they miss the important bits at the end, where the message typically ends up being, causing a bunch of extra back-and-forth to get on the same page.

I understand completely - FYI typing ‘s’ in the default systemctl CLI gives a prompt ‘log file:’. Entering a path/file will save the command output untruncated.

Is there a good way to handle log files? They are beautifully structured for machine reading but there is unstructured text that causes jq to error out. The lines are so long that it’s really hard to read.

@zzz

:443 {
        tls internal

After sorting out the firewall issues and getting the domain working I tried to get the following to work without success:

:80   {                                                                         
    root * /usr/share/caddy                                                     
    file_server                                                                 
}                                                                               
                                                                                
                                                                                
:443   {                                                                        
    tls internal
    root * /usr/share/caddy                                                     
    file_server                                                                 
}    

http:// port 80 failed

$ curl -v --insecure -I http://132.145.103.78/
*   Trying 132.145.103.78:80...
* TCP_NODELAY set
* Connected to 132.145.103.78 (132.145.103.78) port 80 (#0)
> HEAD / HTTP/1.1
> Host: 132.145.103.78
> User-Agent: curl/7.68.0
> Accept: */*
> 
* Mark bundle as not supporting multiuse
< HTTP/1.1 308 Permanent Redirect
HTTP/1.1 308 Permanent Redirect
< Connection: close
Connection: close
< Location: https://132.145.103.78/
Location: https://132.145.103.78/
< Server: Caddy
Server: Caddy
< Date: Tue, 10 May 2022 10:14:30 GMT
Date: Tue, 10 May 2022 10:14:30 GMT
< 
* Closing connection 0

And so dit port 443:

$ curl -v --insecure -I https://132.145.103.78/
*   Trying 132.145.103.78:443...
* TCP_NODELAY set
* Connected to 132.145.103.78 (132.145.103.78) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.3 (IN), TLS alert, internal error (592):
* error:14094438:SSL routines:ssl3_read_bytes:tlsv1 alert internal error
* Closing connection 0
curl: (35) error:14094438:SSL routines:ssl3_read_bytes:tlsv1 alert internal error

Any ideas?