VIRTUAL_PORT is set to 5000. No changes made to container…
At this point, I’m wondering if I should rebuild the VPS with something like Ubuntu. I only used Alma as my cloud service had this image available with docker already installed.
Any recommendations on the distro that other people have been successful with?
If it works without SSL, you definitely just have an error somewhere in the config. I use the setup @emyoulation linked and it works. You can share your compose config. I bet it has nothing to do with the host OS.
[Mon Jul 3 12:29:17 UTC 2023] Creating domain key
[Mon Jul 3 12:29:49 UTC 2023] The domain key is here: /etc/acme.sh/default/gramps.xxx.com/gramps.xxx.com.key
[Mon Jul 3 12:29:49 UTC 2023] Single domain='gramps.xxx.com'
[Mon Jul 3 12:29:49 UTC 2023] Getting domain auth token for each domain
[Mon Jul 3 12:29:51 UTC 2023] Create new order error. Le_OrderFinalize not found. {
"type": "urn:ietf:params:acme:error:rateLimited",
"detail": "Error creating new order :: too many failed authorizations recently: see https://letsencrypt.org/docs/failed-validation-limit/",
"status": 429
}
[Mon Jul 3 12:29:51 UTC 2023] Please check log file for more details: /dev/nullSleep for 3600s
I am not sure if this is due to firewalling, or because the VPS is a subdomain and not hosting the DNS entry locally, or …
I don’t see any smoking gun in your config. I see LETSENCRYPT_EMAIL is missing - not sure if that is compulsory, you can try if that helps. I guess you have also tried docker-compose restarting it … what do the logs say?
And I assume you are trying to access it through the right hostname, not the IP (which will not work)?
Learned something new. I’m getting an error from nginx on startup…
Attaching to nginx-proxy, grampsweb_redis, nginx-proxy-acme, grampsweb, grampsweb_celery
grampsweb_redis | 1:C 03 Jul 2023 16:39:53.573 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
grampsweb_redis | 1:C 03 Jul 2023 16:39:53.573 # Redis version=7.0.11, bits=64, commit=00000000, modified=0, pid=1, just started
grampsweb_redis | 1:C 03 Jul 2023 16:39:53.573 # 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 03 Jul 2023 16:39:53.580 * monotonic clock: POSIX clock_gettime
grampsweb_redis | 1:M 03 Jul 2023 16:39:53.589 * Running mode=standalone, port=6379.
grampsweb_redis | 1:M 03 Jul 2023 16:39:53.589 # Server initialized
grampsweb_redis | 1:M 03 Jul 2023 16:39:53.590 # 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 03 Jul 2023 16:39:53.593 * Ready to accept connectionsnginx-proxy | Info: running nginx-proxy version 1.3.1-22-g4304dcd
nginx-proxy | Warning: A custom dhparam.pem file was provided. Best practice is to use standardized RFC7919 DHE groups instead.
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/03 16:39:53 [crit] 16#16: pread() "/etc/nginx/conf.d/my_proxy.conf" failed (21: Is a directory)
nginx-proxy | nginx.1 | nginx: [crit] pread() "/etc/nginx/conf.d/my_proxy.conf" failed (21: Is a directory)
I have a docker-compose folder, and in it I place the yml file and the find conf file.
root@localhost:~/docker-compose# ls
dc2.bak dc.bak docker-compose.yml ng.bak nginx_proxy.conf
Files live together in the same folder.
I just did a remove all images and tried to a docker-compose up… Pertinent updates below…
Creating nginx-proxy ... error
Creating grampsweb ...
Creating grampsweb_redis ...
Creating nginx-proxy-acme ...
ERROR: for nginx-proxy Cannot start service proxy: failed to create task
for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container
init: error mounting "/root/docker-compose/nginx_proxy.conf" to rootfs at
"/etc/nginx/conf.d/my_proxy.conf": mount /root/docker-compose/nginx_proxy.conf:/etc/nginx/conf.d/my_proxy.conf (via /proc/self/fd/6), flags: 0x5001:Creating grampsweb ... done
Creating grampsweb_redis ... done
Creating nginx-proxy-acme ... done
Creating grampsweb_celery ... done
ERROR: for proxy Cannot start service proxy: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init:
error mounting "/root/docker-compose/nginx_proxy.conf" to rootfs at "/etc/nginx/conf.d/my_proxy.conf": mount /root/docker-compose/nginx_proxy.conf:/etc/nginx/conf.d/my_proxy.conf (via /proc/self/fd/6), flags: 0x5001: not a directory: unknown: Are you trying to mount a directory onto a file (or vice-versa)? Check if the specified host path exists and is the expected type
ERROR: Encountered errors while bringing up the project.
root@localhost:~/docker-compose#
