Error
Unhandled exception during request dispatching
module 'luci.ucodebridge' not found:
no field package.preload['luci.ucodebridge']
no file './luci/ucodebridge.lua'
no file '/usr/share/lua/luci/ucodebridge.lua'
no file '/usr/share/lua/luci/ucodebridge/init.lua'
no file '/usr/lib/lua/luci/ucodebridge.lua'
no file '/usr/lib/lua/luci/ucodebridge/init.lua'
no file './luci/ucodebridge.so'
no file '/usr/lib/lua/luci/ucodebridge.so'
no file '/usr/lib/lua/loadall.so'
no file './luci.so'
no file '/usr/lib/lua/luci.so'
no file '/usr/lib/lua/loadall.so'
In [anonymous function](), file [C]
In [anonymous function](), file /usr/share/ucode/luci/runtime.uc, line 133, byte 10:
called from function [arrow function] (/usr/share/ucode/luci/runtime.uc:141:63)
called from function render ([C])
called from function [anonymous function] (/usr/share/ucode/luci/runtime.uc:141:64)
called from function run_action (/usr/share/ucode/luci/dispatcher.uc:778:34)
called from function [anonymous function] (/usr/share/ucode/luci/dispatcher.uc:1003:48)
called from anonymous function (/www/cgi-bin/luci:39:13)
` die(ex);`
Near here --------^
what now?
i have been using raw 23.05.5 but i was thinking maybe i get luck and nothing will fuk up if i use renew buttons (especially banip) is most important for me, and that s how it ended
i just used update packages, one by one in luci, propably some config file has some new part somewhere but old doesnt and is saved as -opkg (i just assume)
Upgrading packages (via the CLI opkg upgrade command or the LuCI Upgrade... button) can result in major problems. It is generally highly discouraged, unless you know what you are doing or if there is specific instruction to do so.
To resolve your issue, make a backup using the command line, then reset the router to defaults. You can then restore your backup. If the problem was caused by your package upgrades, restoring the backup should be safe.
The package upgrade process was almost certainly the cause of the problem. This can happen in general for a number of reasons, but is essentially guaranteed to happen if you start installing packages from the snapshot repo (or really any repo that is linked against a different OpenWrt/kernel version).
Yes, you can create a custom image with the firmware selector that has all of your packages pre-installed. Or you can reset to defaults and then install those packages post-reset. The result will be largely the same, although the firmware selector method will actually consume less space because the images are squashfs compressed.