Wallabag behind a reverse proxy with directory path

Hi,

I'm using the docker version of wallabag and trying to get it working behind an nginx reverse proxy with the /wallabag path. I've found a few mentions of this online but no configs. Is it possible to do this?

The closest I've gotten is using the domain name variable which works for loading images (when accessing via internal IP) but accessing via the reverse proxy gives a 404 error.

Thanks,

No file or test is named. Start by reviewing the Docker deployment and the nginx reverse-proxy setup, then reproduce access through the /wallabag directory path and compare it with direct access. Done means the application loads through the prefixed path without 404 errors, including its images.

Written by the indexing model from the issue text.