Letsencrypt NGINX Error - lua_load_resty_core

I keep getting NGINX errors regarding lua_load_resty_core…have tried it on two different servers with a fresh /config folder.

Using docker-compose:

image: linuxserver/letsencrypt
container_name: letsencrypt
- /home/letsencrypt:/config
- PUID=1001
- PGID=1001
- TZ=America/New_York
- 80:80
- 443:443
restart: always

relevant logs:

New certificate generated; starting nginx
[cont-init.d] 50-config: exited 0.
[cont-init.d] 99-custom-scripts: executing…
[custom-init] no custom scripts found exiting…
[cont-init.d] 99-custom-scripts: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
Server ready
nginx: [alert] detected a LuaJIT version which is not OpenResty’s; many optimizations will be disabled and performance will be compromised
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:
no field package.preload[‘resty.core’]
no file ‘./resty/core.lua’
no file ‘/usr/share/luajit-2.1.0-beta3/resty/core.lua’
no file ‘/usr/local/share/lua/5.1/resty/core.lua’
no file ‘/usr/local/share/lua/5.1/resty/core/init.lua’
no file ‘/usr/share/lua/5.1/resty/core.lua’
no file ‘/usr/share/lua/5.1/resty/core/init.lua’
no file ‘/usr/share/lua/common/resty/core.lua’
no file ‘/usr/share/lua/common/resty/core/init.lua’
no file ‘./resty/core.so’
no file ‘/usr/local/lib/lua/5.1/resty/core.so’
no file ‘/usr/lib/lua/5.1/resty/core.so’
no file ‘/usr/local/lib/lua/5.1/loadall.so’
no file ‘./resty.so’
no file ‘/usr/local/lib/lua/5.1/resty.so’
no file ‘/usr/lib/lua/5.1/resty.so’
no file ‘/usr/local/lib/lua/5.1/loadall.so’)

Thanks for your help, let me know if you need any further information, I’ve had this running flawlessly for 6+ months and have just now run into this issue.



I’ve got the same issue. My reverse proxy became unavailable, so I checked the log and this was the first [alert] and [error] that popped up.

The Lua errors are harmless unless you use Lua, which I’m almost sure you don’t.
@nholben The only issue you have are the error message?

If your containeriis not working, the Lua errors are not the source of you problem. You should start a new thread detailing your problem.

Might want to give the proxy a little more time to initialize. I have all my proxies unavailable for like 30-60 seconds after these lua errors on letsencrypt container logs.

After that errors stay there but proxies return to work as normal.

The same behavior every restart of the letsencrypt container.