1. Caddy version (caddy version):
v2.4.5 h1:P1mRs6V2cMcagSPn+NWpD+OEYUYLIf6ecOa48cFGeUg=
2. How I run Caddy:
In a docker container
a. System environment:
In a docker container: caddy:latest
b. Command:
c. Service/unit/compose file:
docker run \
-d \
-p 80:80 \
-p 443:443 \
-v "$(pwd)"/Caddyfile:/etc/caddy \
-v "$(pwd)"/data:/data \
-v "$(pwd)"/public:/var/www/html \
--name rb_caddy \
caddy:latest
d. My complete Caddyfile or JSON config:
{
debug
}
parkdash.xyz
root * /var/www/html/parkdash.xyz
reverse_proxy /tows/* rb_tinyows:8080
reverse_proxy /rest/* rb_express:3000
file_server
log {
output file /var/log/access2.log
}
3. The problem I’m having:
So, I’ve 2 reverse_proxy’s. The express rest api is working fine. The second one, a wfs server is giving me troubles. Both backends are running in a docker container, the rb_tinyows is running also on port 8080, with no problems:
curl http://parkdash.xyz:8080/tows/ -v gives:
* Trying 192.255.166.159:8080...
* TCP_NODELAY set
* Connected to parkdash.xyz (192.255.166.159) port 8080 (#0)
> GET /tows/ HTTP/1.1
> Host: parkdash.xyz:8080
> User-Agent: curl/7.68.0
> Accept: */*
>
* Mark bundle as not supporting multiuse
< HTTP/1.1 200 OK
< Date: Wed, 09 Feb 2022 15:41:04 GMT
< Server: Apache/2.4.29 (Ubuntu)
< Vary: Accept-Encoding
< Access-Control-Allow-Origin: *
< Cache-Control: max-age=0, must-revalidate, no-cache, no-store
< Transfer-Encoding: chunked
< Content-Type: application/xml
<
<?xml version='1.0' encoding='UTF-8'?>
<ows:ExceptionReport
xmlns='http://www.opengis.net/ows'
xmlns:ows='http://www.opengis.net/ows'
xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance'
xsi:schemaLocation='http://www.opengis.net/ows http://schemas.opengis.net/ows/1.0.0/owsExceptionReport.xsd'
version='1.1.0' language='en'>
<ows:Exception exceptionCode='InvalidParameterValue' locator='service'>
<ows:ExceptionText>Service Unknown</ows:ExceptionText>
</ows:Exception>
</ows:ExceptionReport>
* Connection #0 to host parkdash.xyz left intact
When trying using
curl http://parkdash.xyz/tows/ -v
i get:
* Trying 192.255.166.159:80...
* TCP_NODELAY set
* Connected to parkdash.xyz (192.255.166.159) port 80 (#0)
> GET /tows/ HTTP/1.1
> Host: parkdash.xyz
> User-Agent: curl/7.68.0
> Accept: */*
>
* Mark bundle as not supporting multiuse
< HTTP/1.1 308 Permanent Redirect
< Connection: close
< Location: https://parkdash.xyz/tows/
< Server: Caddy
< Date: Wed, 09 Feb 2022 15:44:02 GMT
< Content-Length: 0
<
* Closing connection 0
In a browser I get error 502
4. Error messages and/or full log output:
"request":{
"remote_addr":"85.148.190.97:54176",
"proto":"HTTP/2.0",
"method":"GET",
"host":"parkdash.xyz",
"uri":"/tows/?service=WFS&version=1.1.0&request=DescribeFeatureType&Typename=tows:bgv_bezettingen",
"headers":{
"Accept-Encoding":[
"gzip, deflate, br"
],
"Cache-Control":[
"max-age=0"
],
"Upgrade-Insecure-Requests":[
"1"
],
"User-Agent":[
"Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/97.0.4692.71 Safari/537.36"
],
"Sec-Fetch-Site":[
"none"
],
"Sec-Fetch-Mode":[
"navigate"
],
"Accept":[
"text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,image/apng,*/*;q=0.8,application/signed-exchange;v=b3;q=0.9"
],
"Sec-Gpc":[
"1"
],
"Sec-Fetch-User":[
"?1"
],
"Sec-Fetch-Dest":[
"document"
],
"Accept-Language":[
"en-US,en;q=0.9"
]
},
"tls":{
"resumed":false,
"version":772,
"cipher_suite":4865,
"proto":"h2",
"proto_mutual":true,
"server_name":"parkdash.xyz"
}
},
"common_log":"85.148.190.97 - - [09/Feb/2022:12:31:43 +0000] \"GET /tows/?service=WFS&version=1.1.0&request=DescribeFeatureType&Typename=tows:bgv_bezettingen HTTP/2.0\" 502 0",
"user_id":"",
"duration":0.003420513,
"size":0,
"status":502,
"resp_headers":{
"Server":[
"Caddy"
]
}
}
5. What I already tried:
I’ve tried to find out what apache is returning to caddy without any luck. The docker containing tinyows runs on apache, so my guess is that the transport should be http, tinyows itself is a fastcgi application,
changing to:
reverse_proxy /tows/* rb_tinyows:8080 { transport fastcgi } makes no difference
also replacing rb_tinyows with its ip:
reverse_proxy /tows/* 172.18.0.3:8080
does not work, ping (from caddy container to rb_tinyows) is ok:
‘’’
/srv # ping 172.18.0.3
PING 172.18.0.3 (172.18.0.3): 56 data bytes
64 bytes from 172.18.0.3: seq=0 ttl=64 time=0.245 ms
64 bytes from 172.18.0.3: seq=1 ttl=64 time=0.155 ms
^C
--- 172.18.0.3 ping statistics ---
2 packets transmitted, 2 packets received, 0% packet loss
round-trip min/avg/max = 0.155/0.200/0.245 ms
/srv #
/srv #
/srv # ping rb_tinyows
PING rb_tinyows (172.18.0.3): 56 data bytes
64 bytes from 172.18.0.3: seq=0 ttl=64 time=0.082 ms
64 bytes from 172.18.0.3: seq=1 ttl=64 time=0.109 ms
I also tried this with no luck:
reverse_proxy /tows/* rb_tinyows:8080 {
transport http {
dial_timeout 2s
tls_timeout 2s
compression off
}
}
the tinyows docker itself is started with:
docker run \
-d \
-p 8080:80 \
--restart unless-stopped \
--name rb_tinyows \
-v "$(pwd)"/tinyows.xml/:/etc/mapserver/tinyows.xml:ro \
-v "$(pwd)"/tinyows.xml/:/etc/tinyows.xml:ro \
-e MAX_REQUESTS_PER_PROCESS=1000 \
camptocamp/tinyows:master
It would be very nice if someone has a idea whats going wrong!
Thank you
kind regards Robbert
thx again!