> 1) Always post the ACTUAL command line used (or log
> file line two) so we know what the site is, what ALL
> your settings are, etc.
> 2) Always post the URLs you're not getting and from
> what URL.
> 3) Always post anything USEFUL from the log file.
> 4) If you want everything use the near flag (get
> non-html files related) not filters.
> 5) I always run with No External Pages so I know
> where the mirror ends. I always run with broswer
> ID=msie6 as some sites don't like a HTT one. I
> always run with Attempt to detect all links.

I see that you put this at the top of your posts... almost a reverse
signature. This is good, but you should put before all of that "See my
responses mixed in with your original question below".  Or maybe not,
whatever

> Reason: You're speaking plain HTTP to an SSL-enabled
> server port.< br />
> Instead use the HTTPS scheme to access this URL,
> please.< br />

...

> Your url is invalid. Also you can't login using
> httpS directly
> <http://forum.httrack.com/readmsg/29365/index.html>


Ah, this is both obvious and subtle. The proxy can't intercept httpS. Someone
needs to spell that out better in the related faq pages, troubleshooting,
etc.

Also, this:
<http://forum.httrack.com/readmsg/7154/6418/index.html>

I think the key point there was to use the "--update" option to tell httrack
to use the cookie file provided. All in all, I found that getting httrack to
use my cookie file was laborious.

The program is great, but a bit difficult to use.