HDR-T2 with 500 Internal server error

[dandnsmith]

OK - removed those 'is a directory' files, and then ran the opkg: opkg install --force-reinstall webif openssl jim Removing package webif from root... Not deleting modified conffile /mod/webif/html/css/EXTRA.css. Removing package openssl from root... Removing package jim from root... Installing webif (1.5.2-6) to root... Downloading http://hpkg.tv/hdrfoxt2/base/webif_1.5.2-6_mipsel.opk. wget: can't load library 'libssl.so.1.1' Installing openssl (1.1.1.d-1) to root... Downloading http://hpkg.tv/hdrfoxt2/base/openssl_1.1.1.d-1_mipsel.opk. wget: can't load library 'libssl.so.1.1' Installing jim (0.82-2) to root... Downloading http://hpkg.tv/hdrfoxt2/base/jim_0.82-2_mipsel.opk. wget: can't load library 'libssl.so.1.1' Collected errors: * opkg_download: Failed to download http://hpkg.tv/hdrfoxt2/base/webif_1.5.2-6_mipsel.opk, wget returned 16. * opkg_install_pkg: Failed to download webif. Perhaps you need to run 'opkg update'? * opkg_install_cmd: Cannot install package webif. * opkg_download: Failed to download http://hpkg.tv/hdrfoxt2/base/openssl_1.1.1.d-1_mipsel.opk, wget returned 16. * opkg_install_pkg: Failed to download openssl. Perhaps you need to run 'opkg update'? * opkg_install_cmd: Cannot install package openssl. * opkg_download: Failed to download http://hpkg.tv/hdrfoxt2/base/jim_0.82-2_mipsel.opk, wget returned 16. * opkg_install_pkg: Failed to download jim. Perhaps you need to run 'opkg update'? * opkg_install_cmd: Cannot install package jim.
Obviously something still not correct

 

[prpr]

Nearly there I think. Try this:

cd /tmp
/bin/wget -U "" http://hpkg.tv/hdrfoxt2/base/openssl_1.1.1.d-1_mipsel.opk
opkg install --force-reinstall openssl_1.1.1.d-1_mipsel.opk
opkg update
opkg install --force-reinstall webif jim
opkg upgrade

 

[dandnsmith]

Many thanks for that - it seems to have done the trick, and now I can use the webif again.
All I need is to set a few settings which aren't quite how I want them.

 

[prpr]

This time I was able to telnet in on that address...
I've no idea what got it able to telnet via wifi, but am grateful for the help.

Luck, I suspect.

Having done loads of investigation into this, it turns out that it really was luck.
I've identified not just a two-way but a three-way race condition between the various parts of the CF and have managed to eliminate it. My test machine boots reliably into maintenance mode on wireless now.

 

[EEPhil]

I've identified not just a two-way but a three-way race condition between the various parts of the CF and have managed to eliminate it

Ouch!
But why had this not become obvious before?
The CF is rather mature now. I'd have expected a condition like this to have presented itself in the early stages.

it really was luck.

...that no one had done whatever you're doing.

 

[Black Hole]

But why had this not become obvious before?

Because it doesn't always happen, or even happen most of the time. The circumstances have to align just wrong, eg the WiFi hasn't negotiated in time before the next step. dandnsmith's persistent problem may be down to his particular circumstances.

 

[prpr]

Because it doesn't always happen, or even happen most of the time.

It did for me. 100% failure rate.