I run OMV on a RockPro64 (4GB RAM).
OMV version 4.1.23-1 (Arrakis)
Kernel: Linux 4.4.167-1213-rockchip-ayufan-g34ae07687fce
Processor: ARMv8 Processor rev 2 (v8l)
I am trying to get Let's Encrypt running using this TDL tutorial (
(This I kind of a follow-up on: Problems installing Let's Encrypt (with DuckDNS) - [TDL tutorial])
I managed to install the Let's Encrypt container and its certificates. I did get this 'alert' afterwards:
New certificate generated; starting nginx
[cont-init.d] 50-config: exited 0.
[cont-init.d] 99-custom-files: executing...
[custom-init] no custom files found exiting...
[cont-init.d] 99-custom-files: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
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)
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')
Server ready
Alles anzeigen
At this point I expected to be able to go to my server address on port 90 and see the "Welcome to our server" message. Instead I got this error in Chromium: ERR_CONNECTION_REFUSED.
Another clue is that, when I use port forwarding, port 80 and 8096 (jellyfin) can be opened, but 90 isn't getting opened, as if nothing is listening.
What could be the case here?
All the best,