Hmmmm.

When I reach an impasse, I usually run sudo-apt-get update and sudo apt-get upgrade in the console on general principles. Not a universal solution, but it sometimes fixes something that only an expert (not me) would find. I suggest this because WebHTTrack may need some files that weren't in the standard version of the installation. I do this anyway after every
run of Software Updater.

Have you ever started the browser first, before starting WebHTTrack  ?

Make sure that the hostname that WebHTTrack is trying to use ("bishop:8080") is the same as the one that you see when in Terminal mode, if not, find out why this could be so.

Make sure that the browser that WebHTTrack wants to use is actually installed on your
system and that it is the same version as WebHTTrack's preferred browser.

Also, before you start WebHTTrack, navigate to the target website and make an exact copy of the URL from the address line of your browser, including the http:// and checking for its use of www or not in the URL. Then make sure there aren't any spaces or forbidden
characters in that URL.

Make sure that your Port 8080 is not blocked, either at your router, somewhere in your operating system, or in the browser. There are plenty of threads on the subject of open ports on the 'Net, and you should use the suggestions in the linux-based pages to find out whether your Port 8080 is available. This will be a software issue, not hardware, because these ports are programmed in the motherboard and not actual physical connections.

I got a lot of hits in Google on "closed port 8080 trisquel" (without the quotes) and you
may find one or another helpful.

Wishing you better results ...

George Langford

Reply via email to