# Setup Issues: Gramps Web on VPS with SSL **URL:** \ **Category:** Gramps Web\ **Created:** [July 2, 2023, 2:39pm UTC](https://gramps.discourse.group/t/setup-issues-gramps-web-on-vps-with-ssl/3761 "2023-07-02T14:39:39Z")\ **Posts on this page:** 16\ **Page:** 2
**Author:** ![DavidMStraub](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/davidmstraub/32/7_2.png) [@DavidMStraub](https://gramps.discourse.group/u/DavidMStraub)\ **Post date:** [July 3, 2023, 7:39pm UTC](https://gramps.discourse.group/t/setup-issues-gramps-web-on-vps-with-ssl/3761/21 "2023-07-03T19:39:30Z")
If `/root/docker-compose/nginx_proxy.conf` is _not_ a directory (please check), try changing the file name on the RHS; nginx should use any `*.conf` file in `conf.d`. ---
**Author:** ![TheOtherGuy](https://avatars.discourse-cdn.com/v4/letter/t/ecccb3/32.png) [@TheOtherGuy](https://gramps.discourse.group/u/TheOtherGuy)\ **Post date:** [July 4, 2023, 2:58am UTC](https://gramps.discourse.group/t/setup-issues-gramps-web-on-vps-with-ssl/3761/22 "2023-07-04T02:58:51Z")
I’ve tried many different ways of doing the bind and it seems current docker and docker-compose will not allow a single file to be bound… It does allow a folder containing a single file to be bound to a target, but that has downstream problems. If someone has the let’s encrypt working please let me know which version of docker and docker-compose. ---
**Author:** ![DavidMStraub](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/davidmstraub/32/7_2.png) [@DavidMStraub](https://gramps.discourse.group/u/DavidMStraub)\ **Post date:** [July 4, 2023, 6:54am UTC](https://gramps.discourse.group/t/setup-issues-gramps-web-on-vps-with-ssl/3761/23 "2023-07-04T06:54:02Z")
Did you find any documentation about that? I find it very surprising. What are your versions? ---
**Author:** ![TheOtherGuy](https://avatars.discourse-cdn.com/v4/letter/t/ecccb3/32.png) [@TheOtherGuy](https://gramps.discourse.group/u/TheOtherGuy)\ **Post date:** [July 4, 2023, 8:51am UTC](https://gramps.discourse.group/t/setup-issues-gramps-web-on-vps-with-ssl/3761/24 "2023-07-04T08:51:33Z")
Hi David I’m sure it’s a bug and not an intended change. In fact it looks like this bug has existed in the past, and was fixed before. I’ve seen evidence for this in other people having posted the same problem years ago. The behaviour does not reflect the documentation, and I’ve tried 2 different Linux distros. Docker: ```python Client: Docker Engine - Communitydocker version Version: 24.0.2 API version: 1.43 Go version: go1.20.4 Git commit: cb74dfc Built: Thu May 25 21:53:10 2023 OS/Arch: linux/amd64 Context: default Server: Docker Engine - Community Engine: Version: 24.0.2 API version: 1.43 (minimum version 1.12) Go version: go1.20.4 Git commit: 659604f Built: Thu May 25 21:52:10 2023 OS/Arch: linux/amd64 Experimental: false containerd: Version: 1.6.21 GitCommit: 3dce8eb055cbb6872793272b4f20ed16117344 f8 runc: Version: 1.1.7 GitCommit: v1.1.7-0-g860f061 docker-init: Version: 0.19.0 GitCommit: de40ad0 ``` Docker-Compose ```python Docker Compose version v2.19.1 ``` ---
**Author:** ![TheOtherGuy](https://avatars.discourse-cdn.com/v4/letter/t/ecccb3/32.png) [@TheOtherGuy](https://gramps.discourse.group/u/TheOtherGuy)\ **Post date:** [July 4, 2023, 8:42pm UTC](https://gramps.discourse.group/t/setup-issues-gramps-web-on-vps-with-ssl/3761/25 "2023-07-04T20:42:27Z")
Hey David… On a whim I started from scratch again. This time with no pre installs of docker… And guess what, I made it beyond the darn file mount… Yay… But still got stuck… Boo… ```python ✔ Container nginx-proxy-acme Created 0.0s Attaching to grampsweb, grampsweb_celery, grampsweb_redis, nginx-proxy, nginx-proxy-acme nginx-proxy | Info: running nginx-proxy version 1.3.1-30-g6329ea9 nginx-proxy | Warning: A custom dhparam.pem file was provided. Best practice is to use standardized RFC7919 DHE groups instead. grampsweb_redis | 1:C 04 Jul 2023 20:37:50.605 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo grampsweb_redis | 1:C 04 Jul 2023 20:37:50.606 # Redis version=7.0.11, bits=64, commit=00000000, modified=0, pid=1, just started grampsweb_redis | 1:C 04 Jul 2023 20:37:50.606 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf grampsweb_redis | 1:M 04 Jul 2023 20:37:50.607 * Increased maximum number of open files to 10032 (it was originally set to 1024). grampsweb_redis | 1:M 04 Jul 2023 20:37:50.607 * monotonic clock: POSIX clock_gettime grampsweb_redis | 1:M 04 Jul 2023 20:37:50.626 * Running mode=standalone, port=6379. grampsweb_redis | 1:M 04 Jul 2023 20:37:50.626 # Server initialized grampsweb_redis | 1:M 04 Jul 2023 20:37:50.626 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can can also cause failures without low memory condition, see https://github.com/jemalloc/jemalloc/issues/1328. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect. grampsweb_redis | 1:M 04 Jul 2023 20:37:50.642 * Loading RDB produced by version 7.0.11 grampsweb_redis | 1:M 04 Jul 2023 20:37:50.642 * RDB age 33728 seconds grampsweb_redis | 1:M 04 Jul 2023 20:37:50.642 * RDB memory usage when created 0.82 Mb grampsweb_redis | 1:M 04 Jul 2023 20:37:50.642 * Done loading RDB, keys loaded: 0, keys expired: 0. grampsweb_redis | 1:M 04 Jul 2023 20:37:50.642 * DB loaded from disk: 0.012 seconds grampsweb_redis | 1:M 04 Jul 2023 20:37:50.642 * Ready to accept connections nginx-proxy | Warning: TRUST_DOWNSTREAM_PROXY is not set; defaulting to "true". For security, you should explicitly set TRUST_DOWNSTREAM_PROXY to "false" if there is not a trusted reverse proxy in front of this proxy. nginx-proxy | Warning: The default value of TRUST_DOWNSTREAM_PROXY might change to "false" in a future version of nginx-proxy. If you require TRUST_DOWNSTREAM_PROXY to be enabled, explicitly set it to "true". nginx-proxy | forego | starting dockergen.1 on port 5000 nginx-proxy | forego | starting nginx.1 on port 5100 nginx-proxy | nginx.1 | 2023/07/04 20:37:50 [notice] 16#16: using the "epoll" event method nginx-proxy | nginx.1 | 2023/07/04 20:37:50 [warn] 16#16: 10240 worker_connections exceed open file resource limit: 1024 nginx-proxy | nginx.1 | nginx: [warn] 10240 worker_connections exceed open file resource limit: 1024 nginx-proxy | nginx.1 | 2023/07/04 20:37:50 [notice] 16#16: nginx/1.25.1 nginx-proxy | nginx.1 | 2023/07/04 20:37:50 [notice] 16#16: built by gcc 12.2.0 (Debian 12.2.0-14) nginx-proxy | nginx.1 | 2023/07/04 20:37:50 [notice] 16#16: OS: Linux 5.15.0-76-generic nginx-proxy | nginx.1 | 2023/07/04 20:37:50 [notice] 16#16: getrlimit(RLIMIT_NOFILE): 1024:524288 nginx-proxy | nginx.1 | 2023/07/04 20:37:50 [notice] 16#16: start worker processes nginx-proxy | nginx.1 | 2023/07/04 20:37:50 [notice] 16#16: start worker process 22 nginx-proxy | dockergen.1 | 2023/07/04 20:37:54 Generated '/etc/nginx/conf.d/default.conf' from 5 containers nginx-proxy | dockergen.1 | 2023/07/04 20:37:54 Running 'nginx -s reload' nginx-proxy-acme | Info: running acme-companion version v2.2.8-8-g6106556 nginx-proxy | nginx.1 | 2023/07/04 20:37:55 [notice] 16#16: signal 1 (SIGHUP) received from 24, reconfiguring nginx-proxy | nginx.1 | 2023/07/04 20:37:55 [notice] 16#16: reconfiguring nginx-proxy | nginx.1 | 2023/07/04 20:37:55 [notice] 16#16: using the "epoll" event method nginx-proxy | nginx.1 | 2023/07/04 20:37:55 [warn] 16#16: 10240 worker_connections exceed open file resource limit: 1024 nginx-proxy | nginx.1 | 2023/07/04 20:37:55 [notice] 16#16: start worker processes nginx-proxy | nginx.1 | 2023/07/04 20:37:55 [notice] 16#16: start worker process 25 nginx-proxy | nginx.1 | 2023/07/04 20:37:55 [notice] 22#22: gracefully shutting down nginx-proxy | nginx.1 | 2023/07/04 20:37:55 [notice] 22#22: exiting nginx-proxy | nginx.1 | 2023/07/04 20:37:55 [notice] 22#22: exit nginx-proxy | dockergen.1 | 2023/07/04 20:37:55 Watching docker events nginx-proxy | nginx.1 | 2023/07/04 20:37:55 [notice] 16#16: signal 17 (SIGCHLD) received from 22 nginx-proxy | nginx.1 | 2023/07/04 20:37:55 [notice] 16#16: worker process 22 exited with code 0 nginx-proxy | nginx.1 | 2023/07/04 20:37:55 [notice] 16#16: signal 29 (SIGIO) received nginx-proxy | dockergen.1 | 2023/07/04 20:37:55 Contents of /etc/nginx/conf.d/default.conf did not change. Skipping notification 'nginx -s reload' ^CGracefully stopping... (press Ctrl+C again to force) ``` Have you seen this behaviour before? And hints on how to fix? Chris ---
**Author:** ![SNoiraud](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/snoiraud/32/72_2.png) [@SNoiraud](https://gramps.discourse.group/u/SNoiraud)\ **Post date:** [July 5, 2023, 7:29am UTC](https://gramps.discourse.group/t/setup-issues-gramps-web-on-vps-with-ssl/3761/26 "2023-07-05T07:29:08Z")
The answer is in the log: > [@TheOtherGuy](#): > > ```python > grampsweb_redis | 1:M 04 Jul 2023 20:37:50.626 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can can also cause failures without low memory condition, see https://github.com/jemalloc/jemalloc/issues/1328. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and > then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect. > > ``` You have a memory management problem and you need to tune the linux kernel. ---
**Author:** ![TheOtherGuy](https://avatars.discourse-cdn.com/v4/letter/t/ecccb3/32.png) [@TheOtherGuy](https://gramps.discourse.group/u/TheOtherGuy)\ **Post date:** [July 5, 2023, 7:44pm UTC](https://gramps.discourse.group/t/setup-issues-gramps-web-on-vps-with-ssl/3761/27 "2023-07-05T19:44:21Z")
Thanks SNoiraud… I’ll look into my options… ---
**Author:** ![TheOtherGuy](https://avatars.discourse-cdn.com/v4/letter/t/ecccb3/32.png) [@TheOtherGuy](https://gramps.discourse.group/u/TheOtherGuy)\ **Post date:** [July 6, 2023, 2:25am UTC](https://gramps.discourse.group/t/setup-issues-gramps-web-on-vps-with-ssl/3761/28 "2023-07-06T02:25:59Z")
Thank you David and SNoiraud, I had a breakthrough tonight! System is up. VPS - Ubuntu 22.04 and current docker Thanks again, Chris ---
**Author:** ![DavidMStraub](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/davidmstraub/32/7_2.png) [@DavidMStraub](https://gramps.discourse.group/u/DavidMStraub)\ **Post date:** [July 22, 2023, 11:31am UTC](https://gramps.discourse.group/t/setup-issues-gramps-web-on-vps-with-ssl/3761/29 "2023-07-22T11:31:15Z")
Hi, I finally updated the DO image at [Gramps Web | DigitalOcean Marketplace 1-Click App](https://marketplace.digitalocean.com/apps/gramps-web) because I think the Let’s Encrypt setup had an issue. Hope it will run more smooth for future users. ---
**Author:** ![assanj](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/assanj/32/3433_2.png) [@assanj](https://gramps.discourse.group/u/assanj)\ **Post date:** [November 7, 2023, 10:36pm UTC](https://gramps.discourse.group/t/setup-issues-gramps-web-on-vps-with-ssl/3761/30 "2023-11-07T22:36:01Z")
plz tell what s solution for problem: **- ./nginx\_proxy.conf:/etc/nginx/conf.d/my\_proxy.conf:ro** **Chris, plz call me on email!** ---
**Author:** ![emyoulation](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/emyoulation/32/67_2.png) [@emyoulation](https://gramps.discourse.group/u/emyoulation)\ **Post date:** [November 7, 2023, 10:54pm UTC](https://gramps.discourse.group/t/setup-issues-gramps-web-on-vps-with-ssl/3761/31 "2023-11-07T22:54:07Z")
Have you looked at this message above on this thead: > [@Setup Issues: Gramps Web on VPS with SSL](https://gramps.discourse.group/t/setup-issues-gramps-web-on-vps-with-ssl/3761/19): > > Is the expected outcome a conf folder in the proxy image with the nginx\_proxy.conf within it? What is the objective of this volume line? - ./nginx\_proxy.conf:/etc/nginx/conf.d/my\_proxy.conf:ro ---
**Author:** ![assanj](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/assanj/32/3433_2.png) [@assanj](https://gramps.discourse.group/u/assanj)\ **Post date:** [November 7, 2023, 11:02pm UTC](https://gramps.discourse.group/t/setup-issues-gramps-web-on-vps-with-ssl/3761/32 "2023-11-07T23:02:41Z")
**sorry.** yes, i have looked, but HOW i can find answer for it: > Is the expected outcome a conf folder in the proxy image with the nginx\_proxy.conf within it? everybody dancing from [https://www.grampsweb.org/LetsEncrypt/](https://www.grampsweb.org/LetsEncrypt/) and receives this error - ./nginx\_proxy.conf:/etc/nginx/conf.d/my\_proxy.conf:ro Looks like, this line from [docker-compose.yml](https://raw.githubusercontent.com/gramps-project/web/main/examples/docker-compose-letsencrypt/docker-compose.yml) says: > mount the file on the _LeftHandSide_ to the file on the _RightHandSide_, to have nginx pick up the client\_max\_body\_size setting. is it possible to mount a file on a directory? is the _RightHandSide_ = folder in the proxy image (_how check it)_? is the _LeftHandSide_ = my local path (on pic below)? ![Снимок экрана от 2023-11-08 02-12-38](https://global.discourse-cdn.com/free1/uploads/gramps/original/2X/6/619b352bce34e1ec4c426148d32f61438542aa63.png) **if it cant be easy mounted =\> What should be in this mount line in the standard way for user@user-v:~/app$ sudo docker compose up -d ?** What should be the local file hierarchy in ubuntu/linux? Tnx ---
**Author:** ![emyoulation](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/emyoulation/32/67_2.png) [@emyoulation](https://gramps.discourse.group/u/emyoulation)\ **Post date:** [November 7, 2023, 11:19pm UTC](https://gramps.discourse.group/t/setup-issues-gramps-web-on-vps-with-ssl/3761/33 "2023-11-07T23:19:49Z")
Thanks for expanding the details on your question. The 1st posting was vague. There’s a better chance of getting an actionable reply now. ---
**Author:** ![amashkin](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/amashkin/32/4267_2.png) [@amashkin](https://gramps.discourse.group/u/amashkin)\ **Post date:** [April 6, 2024, 8:11pm UTC](https://gramps.discourse.group/t/setup-issues-gramps-web-on-vps-with-ssl/3761/34 "2024-04-06T20:11:58Z")
I have the same issue on 2 Ubuntu and Debian instances. docker-compose.yml is original [Docker with Let's Encrypt - Gramps Web](https://www.grampsweb.org/LetsEncrypt/) and the same as from @TheOtherGuy Diagnostick is the same: nginx: [crit] pread() “/etc/nginx/conf.d/my\_proxy.conf” failed (21: Is a directory) Is there any solution? Could you please explain my steps for this: (The [nginx\_proxy.conf](https://raw.githubusercontent.com/gramps-project/gramps-web-docs/main/examples/docker-compose-letsencrypt/nginx_proxy.conf) needs to be stored in the same directory to allow uploading large media files to Gramps Web.) ---
**Author:** ![DavidMStraub](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/davidmstraub/32/7_2.png) [@DavidMStraub](https://gramps.discourse.group/u/DavidMStraub)\ **Post date:** [April 7, 2024, 5:55am UTC](https://gramps.discourse.group/t/setup-issues-gramps-web-on-vps-with-ssl/3761/35 "2024-04-07T05:55:03Z")
Hi, can you look at this issue for instance? > > > I'm trying to override the .conf file for a subdomain (I've tried to do it with …the domain too) and when I try to run my container I see this > \`\`\` > proxy\_1 | nginx.1 | 2017/09/10 20:38:16 \[crit\] 27#27: pread() "/etc/nginx/conf.d/demo.getdairyfarms.com.conf" failed (21: Is a directory) > proxy\_1 | nginx.1 | nginx: \[crit\] pread() "/etc/nginx/conf.d/demo.getdairyfarms.com.conf" failed (21: Is a directory) > \`\`\` > when my volumes are these: > \`\`\` > volumes: > - "/var/run/docker.sock:/tmp/docker.sock" > - app-public:/usr/share/nginx/html/dairyfarms/ > - "./containers/production/demo\_getdairyfarms\_com.conf:/etc/nginx/conf.d/demo.getdairyfarms.com.conf:ro" > \`\`\` > > Im not sending two files with the same name. Any idea? I suspect you have a similar problem. ---
**Author:** ![amashkin](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/amashkin/32/4267_2.png) [@amashkin](https://gramps.discourse.group/u/amashkin)\ **Post date:** [April 7, 2024, 1:21pm UTC](https://gramps.discourse.group/t/setup-issues-gramps-web-on-vps-with-ssl/3761/36 "2024-04-07T13:21:59Z")
Looks like it is out of my case. Could you please explaine where I should put nginx\_proxy.conf file? Instruction is: A particularly convenient option is to use a dockerized Nginx reverse proxy with automated Let’s Encrypt certificate generation. This is achieved with this docker-compose.yml. (The nginx\_proxy.conf needs to be stored in the same directory to allow uploading large media files to Gramps Web.) As a test I put nginx\_proxy.conf here: (it is part of conf volume) /var/lib/docker/volumes/gramps-web\_conf/\_data/my\_proxy.conf Could you please explaine where I should put nginx\_proxy.conf file? Is there alternative way to path this file? [Previous page](https://gramps.discourse.group/t/setup-issues-gramps-web-on-vps-with-ssl/3761.md?page=1)