Hello, in recent build i introduced by default a module that provide direct access to ubus rpc
I need some feedback with this change...
Can someone tell me if latest master with luci on nginx works well or creates any problem?
I tested it for about 1 week but on luci github i see some guy having problem and as i don't have them i need more feedback
Hello! Please describe in detail your working config. Soft/packages set? Kernel settings (if any tohers than default)? Configuration files (for nginx and uwsgi)? Thank you!
Yes. Trying to research a problem from time to time with no success.
Moreover, results vary from platform to platform. For example, on ASUS RT-AC68U there is no problems (in total). But on Xiaomi Mi Router WiFi 3G I have the whole spectrum of hemorrhoids that we can think of. In both cases I am using gcc 9 and different gcc switches (from Os to O3, for example) and the situation on Xiaomi not getting better...
Which router do you use?
#### RPCError
RPC call to luci/getFeatures failed with error -32000: Object not found at ClassConstructor.handleCallReply (https://192.168.7.99/luci-static/resources/rpc.js?v=git-19.292.31773-cc35206:12:3)
("luci/getFeatures" can be vary) on almost every page.
1st case: Xiaomi №1.
Getting error already on the logon page:
RPCError
RPC call to luci/getFeatures failed with error -32000: Object not found
at ClassConstructor.handleCallReply (https://192.168.1.1/luci-static/resources/rpc.js?v=git-19.292.31773-cc35206:12:3)
2nd case: Xiaomi №2.
Again, getting error already on the logon page:
#### RPCError
RPC call to luci/getFeatures failed with error -32000: Object not found at ClassConstructor.handleCallReply (https://192.168.7.99/luci-static/resources/rpc.js?v=git-19.292.31773-cc35206:12:3)