[error] lua_load_resty_core failed to load the resty.core module

Looks like there is an issue with the latest version of docker image of letsencrypt docker. It’s returning an error after the cert is generated but not actually stored. The docker-compose is a duplicate of https://hub.docker.com/r/linuxserver/letsencrypt/ example … I’m using duckdns and duckdnstoken as my validation method. After the “Server ready” message the container hangs indefinably … the only way to continue is break out of the container. My original validation was http, I switched it to duckdns as a let’s try something else to see if it’s the validation method.

My domain is: mbcli.duckdns.org

I ran this command: docker-compose -f docker-compose-letsencrypt.yaml up

It produced this output:

letsencrypt    | [services.d] done.
letsencrypt    | nginx: [alert] detected a LuaJIT version which is not OpenResty's; many optimizations will be disabled and performance will be compromised (see https://github.com/openresty/luajit2 for OpenResty's LuaJIT or, even better, consider using the OpenResty releases from https://openresty.org/en/download.html)
letsencrypt    | nginx: [error] lua_load_resty_core failed to load the resty.core module from https://github.com/openresty/lua-resty-core; ensure you are using an OpenResty release from https://openresty.org/en/download.html (rc: 2, reason: module 'resty.core' not found:
letsencrypt    |        no field package.preload['resty.core']
letsencrypt    |        no file './resty/core.lua'
letsencrypt    |        no file '/usr/share/luajit-2.1.0-beta3/resty/core.lua'
letsencrypt    |        no file '/usr/local/share/lua/5.1/resty/core.lua'
letsencrypt    |        no file '/usr/local/share/lua/5.1/resty/core/init.lua'
letsencrypt    |        no file '/usr/share/lua/5.1/resty/core.lua'
letsencrypt    |        no file '/usr/share/lua/5.1/resty/core/init.lua'
letsencrypt    |        no file '/usr/share/lua/common/resty/core.lua'
letsencrypt    |        no file '/usr/share/lua/common/resty/core/init.lua'
letsencrypt    |        no file './resty/core.so'
letsencrypt    |        no file '/usr/local/lib/lua/5.1/resty/core.so'
letsencrypt    |        no file '/usr/lib/lua/5.1/resty/core.so'
letsencrypt    |        no file '/usr/local/lib/lua/5.1/loadall.so'
letsencrypt    |        no file './resty.so'
letsencrypt    |        no file '/usr/local/lib/lua/5.1/resty.so'
letsencrypt    |        no file '/usr/lib/lua/5.1/resty.so'
letsencrypt    |        no file '/usr/local/lib/lua/5.1/loadall.so')
letsencrypt    | Server ready

My web server is (include version): home-assistant

The operating system my web server runs on is (include version): Linux CentOS running docker 18.09.5, build e8ff056

I can login to a root shell on my machine (yes or no, or I don’t know): yes

I’m using a control panel to manage my site (no, or provide the name and version of the control panel): no

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you’re using Certbot): docker image: “build_version”: “Linuxserver.io version:- 0.34.2-ls33 Build-date:- 2019-05-30T08:30:17-04:00”

:wave: Hi @aram535, welcome to the community forum.

This isn’t the official Certbot docker image, instead it looks like it’s a 3rd party image provided by https://linuxserver.io.

I think your best bet is to open an issue on the Linuxserver/docker-letsencrypt repository describing the potential bug. Hopefully the project maintainers will know the best next steps for you to take.

Thanks!

2 Likes

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.