No access to Webif

J

jpberry56

New Member
I've been having problems with my Humax lately, no access to the Webif and unable to playback some recordings. Having read many useful threads here, I've tried allsorts to resolve the problem without success so resosrted to a clean install of the CF 3.13. However I'm still not getting access to the Webif with the browser just giving me the 500 error or partial loading of the grey bar at the top of the page.

Since loading the CF i've tried the following:-

1. fixdisk - took an age to run and found a couple of block errors
2. fixdisk - finished return code 0
3. fixweb

Please select option: fixweb
Removing package webif from root...
Installing webif (1.5.3) to root...
Downloading http://hpkg.tv/hdrfoxt2/base/webif_1.5.3_mipsel.opk.
Upgrading epg on root from 1.2.9 to 1.3.0...
Downloading http://hpkg.tv/hdrfoxt2/base/epg_1.3.0_mipsel.opk.
Upgrading hmt on root from 2.0.11 to 2.0.12...
Downloading http://hpkg.tv/hdrfoxt2/base/hmt_2.0.12_mipsel.opk.
Configuring epg.
Configuring hmt.
Configuring webif.
/mod/bin/jimsh: can't load library 'libcrypto.so.1.1'
/mod/bin/jimsh: can't load library 'libcrypto.so.1.1'

Then I tried the following:-

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

This gave a Segmentation fault error on --force-reinstall openssl_1.1.1.d-1_mipsel.opk

Not sure where to go next, guidance greatly appreciated. Thanks
 
jpberry56 said:
resosrted to a clean install of the CF 3.13.
Click to expand...
If you mean reloading the firmware, there is no need for that.

Basically, your disk data has got into a scramble (even if there are no file system errors), and reinstalling stuff doesn't sort out the scramble. Rather than try to unpick what's happened, strip it out and start again (EDIT: but see post 3 for a potentially easier solution).

If you are happy to reformat your disk, just do that. You could run a system flush as well (apply as if a firmware update, except it doesn't update any firmware). Then the system will be in the raw state, as if you had just installed the CF for the first time, and accessing the WebIF address will come up with the installation page.

An alternative, avoiding reformatting the disk, is to use the Telnet menu to set RMA mode, reboot, then clear RMA. RMA mode erases the CF /mod folder on disk and sets a flag to prevent reinstallation of WebIF, so you have to clear the flag if you want to reinstall.
 
Last edited:
The above is total overkill and unnecessary.
Just select the "cli" option from the menu and enter this command:
diag ssl/fix
 
Morning, i tried the short route (diag ss/fix) which gave the following :-
humax# diag ssl/fix

Code: 
Running: ssl/fix
Connecting to hpkg.tv (89.248.55.75:80)
libcrypto.so.1.1 100% |*******************************| 3557k 0:00:00 ETA
Connecting to hpkg.tv (89.248.55.75:80)
libssl.so.1.1 100% |*******************************| 798k 0:00:00 ETA
humax#

I've reooted (via cli) but still no access to the WebIf, any ideas before I go for blasting the disk ?
 
What happens if you try running jimsh from the command prompt? You should get a banner and a dot prompt (exit gets you out if so).
Otherwise try:
opkg remove --force-depends jim webif
opkg install webif
 
prpr said:
What happens if you try running jimsh from the command prompt? You should get a banner and a dot prompt (exit gets you out if so).
Otherwise try:
opkg remove --force-depends jim webif
opkg install webif
Click to expand...
Hi yes that works, tell me :-

Welcome to Jim version 0.82
 
OK, so the "/mod/bin/jimsh: can't load library 'libcrypto.so.1.1'" error from your original post is fixed. This probably stops the 500 errors.
What does "still no access to the WebIf" mean, exactly, now?
Try re-doing the "fixweb" from post 1.
 
I've done the fixweb and I get:-

Code: 
Removing package webif from root...
Installing webif (1.5.3) to root...
Downloading xxxxx hpkg.tv/hdrfoxt2/base/webif_1.5.3_mipsel.opk.
Configuring webif.
/mod/bin/jimsh: can't load library 'libcrypto.so.1.1'
/mod/bin/jimsh: can't load library 'libcrypto.so.1.1'

I'm trying to access the Webif from a firefox window just entering the ip address in the address bar. It just gives a blank grey bar at the top of the screen, i looks like it's starting to render the page but stops. Looking at the source for the returned web page shows the header of the page and some image references.

HTML: 
<!doctype html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
<meta charset="UTF-8">
<title>

Humax HDR Fox T2 (humax)

</title>
<meta http-equiv=X-UA-Compatible content="IE=edge,chrome=1" />
<link rel=icon href=/favicon.ico sizes="16x16 32x32 64x64"
    type=image/vnd.microsoft.icon />
<link rel=apple-touch-icon href=/img/fav/57.png />
<link rel=apple-touch-icon sizes=57x57 href=/img/fav/57.png />
<link rel=apple-touch-icon sizes=72x72 href=/img/fav/72.png />
<link rel=apple-touch-icon sizes=114x114 href=/img/fav/114.png />
<link rel=apple-touch-icon sizes=144x144 href=/img/fav/144.png />

<link href="/lib/jquery.ui/jquery-ui.min.css?1.5.3" rel=stylesheet type=text/css />
<link href="/css/style.css?1.5.3" rel=stylesheet type=text/css />
<link href="/css/EXTRA.css?1.5.3" rel=stylesheet type=text/css />
<script type=text/javascript src="/js/jquery.js?1.5.3"></script>
<script type=text/javascript src="/lib/jquery.ui/jquery-ui.min.js?1.5.3"></script>
<script type=text/javascript src="/charts/high/highcharts.js?1.5.3"></script>

</head>
<body>


<!-- start of topbar -->

<div id=topbar class=container onclick="location.href='/'; return false;">
    <div class=left>
        <img src=/images/154_1_00_WIN_MD116_1L.png>
    </div>
    <div class=middle>
<!-- Start include diskspace - above other items to work around IE feature.. -->


Any ideas ? many thanks
 
It's difficult to know what the root problem is here. The Jim interpreter is only partially working it seems - it works when run directly, but not when called by the shell to execute a script. We've seen this error several times and never managed to get to the bottom of it.
It's possibly something environmental, but without direct access to the machine it's too difficult/time consuming to diagnose, so, reluctantly, I think you'll have to do the RMA process as BH describes at the bottom of post #2.
 
It's a question of practicality, and how long the patient can remain on the operating table – also bearing in mind that the original problem gets corrupted the more hacks get applied.
 
You must log in or register to reply here.
Back
Top