WebHTTrack Website Copier not working in Belenos

Be sure you're not just trying to browse the target domain without first capturing it with WebHTTrack.

See the step-by-step instructions here: https://www.httrack.com/html/step.html
That's what has worked several times for me over the last couple of years. I'll
try it again this morning, just in case ...

George Langford

Didn't get to it 'til much later, but I cloned a website of mine ... no difficulties, no errors ... 100+ files,
ca. 50 MB in half an hour.

The graphical version ... be sure to create a folder on your HDD beforehand and use the complete path to that
file as the target folder for HTTrack.

Afterwards, you can browse the cloned website, but don't expect to use it as a web-based website, because all
the links will reflect the local nature of your copy ... they don't translate to an online website without a
lot of work.

George Langford

I can't follow any of the instructions at the link you gave me, because starting the app (whether from the Start menu, or from a terminal) doesn't open a WebHTTrack window of any kind. It just opens a browser window.

See the original post:

> "I tried launching it from the start menu, and it opened a browser tab, and tried to open a page at: "bishop:8080" (Bishop is the name of this PC)"

strypey wrote:

"I can't follow any of the instructions at the link you gave me, because starting the app
(whether from the Start menu, or from a terminal) doesn't open a WebHTTrack window of any
kind. It just opens a browser window."

Actually, you're on the right track. WebHTTrack always wants me to confirm my browser
preference when I first open WebHTTrack. Then, later on when I start another browser
session, the browser makes me confirm again that I want it to be the default, even
though that's the same browser that I use when running WebHTTrack.

More:
"... and it opened a browser tab, and tried to open a page at: "bishop:8080"

That's normal also.

In response to an earlier question: I'm using Flidas with my current attempt to capture
a webpage ... but it seems to work exactly like it did with Belanos, except that now it
stalls and I get an error: "Connection activation failed (24) Timeout was reached"
ThinkPenguin support suggests that this is a firmware problem, but I haven't tried the
"fix" yet. Others are having a similar problem:https://trisquel.info/en/forum/wifi-issues-tl-wn822n-usb-adapter-it-connects-seems-shut-down-after-few-minutes-despite-update but that is probably unrelated to your
present situation.

You can also start WebHTTrack from the console. Don't use sudo webhttrack, which would run
it as root ! Just use webhttrack, which opens the WebHTTrack GUI. I'll try it now to see
if that makes my WebHTTrack problem go away ...

George Langford

George wrote:
> "WebHTTrack always wants me to confirm my browser preference when I first open WebHTTrack"

Yes, but that's *all* it does. See the screenshot. It doesn't open a WebHTTrack window of any kind. Same when opening from the terminal (see OP and last comment).

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