Can't connect via browsers

Thanks for the quick fix.
Thought it was the chrome update that popped up earlier!

Post #47 worked on both my HDRs, although one of the two took around 45 seconds (rather than the 5 seconds of the first) and it also worked on my HDFOXT2 which was also suffering.
 
prpr said:
#51
Click to expand...

humax2# service

Name Installed Autostart Running
---- --------- --------- -------
betaftpd Yes Yes No
cifs Yes Yes No
nfs No No No
samba Yes Yes No

Syntax:
service start <service>
service stop <service>
service auto <service> (toggles autostart)

humax2#
 
I've lost track of what everyone has been doing to try and get this working. For anyone who just upgraded to the broken package, another upgrade should fix it. If you've been manually editing the package database then it might take a bit more work!

Try running the fix-lighttpd diagnostic from the telnet menu or the command line:

Code: 
humax# diag fix-lighttpd

You may need to restart afterwards to restore all other services.
 
I have done nothing yet and find the 'fixes' confusing to decide which one or which pair.

I have telnet access, could someone produce a step by step please while I digest my fish.
 
af123 said:
I wouldn't be too worried yet. If the web server isn't installed properly then a lot of the custom startup processes don't run.
Click to expand...

One of the two machines is now recognised by the network. I can access it by file manager, ftp and telnet, but not by browser - still only get the webif bootstrap screen. "Service" showed that lighttpd wasn't installed, so I did that using the command in an earlier post. Service now showed it as installed but not running, so I tried "service start lighttpd" and got


humax2# service start lighttpd
Starting lighttpd...
2015-10-23 20:00:17: (network.c.410) can't bind to port: 80 Address already in use
Done.
humax2#

The other machine is still invisible to the network, but I can now ftp to it after manually starting betaftpd.
 
af123 said:
Just 'diag fix-lighttpd'
Click to expand...

Tried it:

humax2# diag fix-lighttpd
Running: fix-lighttpd
Removing package lighttpd from root...
sh: you need to specify whom to kill
killall: lighttpd: no process killed
Downloading http://hpkg.tv/hdrfoxt2/base/Packages.gz.
Inflating http://hpkg.tv/hdrfoxt2/base/Packages.gz.
Updated list of available packages in /mod/var/opkg/base.
Installing lighttpd (1.4.37-1) to root...
Downloading http://hpkg.tv/hdrfoxt2/base/lighttpd_1.4.37-1_mipsel.opk.
Configuring lighttpd.
sh: you need to specify whom to kill
killall: lighttpd: no process killed
2015-10-23 20:24:41: (network.c.410) can't bind to port: 80 Address already in use
 
Ok, now restart with the remote control and it should be fine.
If you can't restart because it's recording then:

killall bootstrapd
/sbin/modinit run_init

should do at a pinch
 
af123 said:
Ok, now restart with the remote control and it should be fine.
If you can't restart because it's recording then:

killall bootstrapd
/sbin/modinit run_init

should do at a pinch
Click to expand...

I regained browser access to one machine by running the fix diagnostic and rebooting. The fix worked on the second machine without a reboot, but it's still invisible to the network.
 
makem said:
Seems like there are still problems so maybe I will wait until tomorrow.
Click to expand...
On the units I'd not messed about with, running the fix-lighttpd diagnostic fixed it without a reboot. The one I'd fiddled with had to have webif reinstalled too, but did not need rebooting either.
 
af123 said:
Just 'diag fix-lighttpd'
Click to expand...
I was going to fiddle about some more, but the expression "when you are in a hole, stop digging" came to mind. I went away, cooked and ate dinner and when I came back a diagnostic was waiting for me to run. Thirty seconds later Web-If was working again. Thanks af123, I think you have earned that glass of wine;)
 
You must log in or register to reply here.
Back
Top