the server responded with a status of 500

[gardnerinfotech]

I installed the Plausible Docker containers, and have a simple reverse proxy using Caddy v2 to expose the server to the web. This installation was very simple and straightforward, I've installed services like this many times.

At first, everything appears to run correctly; I was able to log in to the web service and add a domain. I added the tracking code to a new site, but the events never register on my Plausible instance. Looking at the browser console, it is returning error 500 when attempting to POST to /api/event. Below are the details reported by the browser, followed by my Caddyfile directive for the reverse proxy.

Request URL: https://plausible.infotech.link/api/event
Request Method: POST
Status Code: 500 
Remote Address: 3.17.3.215:443
Referrer Policy: strict-origin-when-cross-origin
access-control-allow-credentials: true
access-control-allow-origin: *
access-control-expose-headers
cache-control: max-age=0, private, must-revalidate
content-length: 39
content-type: application/json; charset=utf-8
date: Fri, 22 Jan 2021 02:30:57 GMT
server: Caddy
server: Cowboy
x-request-id: FlxtCkKzRFxOT68AABxh
:authority: plausible.infotech.link
:method: POST
:path: /api/event
:scheme: https
accept: */*
accept-encoding: gzip, deflate, br
accept-language: en-US,en;q=0.9
content-length: 173
content-type: text/plain
origin: https://onelightdistributing.com
referer: https://onelightdistributing.com/
sec-fetch-dest: empty
sec-fetch-mode: cors
sec-fetch-site: cross-site
sec-gpc: 1
user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/88.0.4324.96 Safari/537.36
{n: "pageview", u: "https://onelightdistributing.com/", d: "onelightdistributing.com",…}
d: "onelightdistributing.com"
n: "pageview"
r: "https://onelightdistributing.com/wp-admin/post.php?post=22&action=edit"
u: "https://onelightdistributing.com/"
w: 1164

Here's my Caddyfile directive for the reverse proxy:

plausible.infotech.link {
        reverse_proxy 172.26.5.57:8000 {
                header_up X-Forwarded-For {http.request.remote}
                header_up X-Forwarded-Port {http.request.port}
                header_up X-Forwarded-Proto {http.request.scheme}
        }
}

Any ideas where the problem may reside?

[Vigasaurus]

You'll want to check your docker logs as those will actually have some meaningful data, if you were able to login and add your sites etc, it's likely not a caddy or web server issue, but rather likely some config mishap with one of the docker containers. docker-compose logs should give you all you need, but you can tack on a -f to follow them and send your POST after. Feel free to post the relevant portions here

[gardnerinfotech]

Yes, I first used the recommended setup, but the results were exactly the same; I combined them primarily for testing and to see all the config in one place.

GEOLITE2_COUNTRY_DB=/geoip/GeoLite2-Country.mmdb

[gardnerinfotech]

I give up - not worth the time. I can find absolutely nothing wrong with my config; it's very straightforward and I've worked with far more complex docker-compose projects than this one. I'm sure there's something else wrong that's probably horribly obvious. :)
I greatly appreciate your help and your contributions to a very nice product - in the near future, I will likely subscribe and transition all of my sites away from Google Analytics as I move towards more humane technology.

[ukutaht]

:/ Sorry about that. I'm stumped as well. I'm running the recommended geoip config and everything works smooth.

One thing I might try is to run docker-compose pull on my end to get the latest versions of everything. Maybe an update in one of the dependencies broke something? Some images like the geoip one are not pinned down to a specific version.

[gaetandezeiraud]

Exact same problem. And the geoip key is used.

As far as I'm concerned, I run on Windows Server and IIS like proxy. But I don't think it's important.
And, If I don't setup geoip with a fresh install, I still have the error. Even if I don't want this feature.

docker-compose pull fix nothing.

[GodGardensGuns]

Running into this issue as well. I have the same GEOLITE2_COUNTRY_DB env variable set:
GEOLITE2_COUNTRY_DB=/geoip/GeoLite2-Country.mmdb
I installed everything about an hour ago, so as expected, docker-compose pull had no effect.
I'm running a reverse proxy through Caddy 2. Here's my Caddyfile:

{
    # email to use on Let's Encrypt
    email dayvista@my.domain

    # Uncomment for debug
    #acme_ca https://acme-staging-v02.api.letsencrypt.org/directory
    #debug
}

# Add gzip compression to requests
(webconf) {
  encode gzip
}

# Add forward headers to requests
(theheaders) {
    header_up X-Forwarded-Ssl on
    header_up Host {host}
    header_up X-Real-IP {remote}
    header_up X-Forwarded-For {remote}
    header_up X-Forwarded-Port {server_port}
    header_up X-Forwarded-Proto {scheme}
    header_up X-Url-Scheme {scheme}
    header_up X-Forwarded-Host {host}
}

my.domain, www.my.domain {
    root * /var/www/my.domain/
    file_server
    import webconf
}

stats.my.domain {
    reverse_proxy http://127.0.0.1:8000 {
      import theheaders
    }
    import webconf
}