Failed during "Crawling discovered URLs" about static-html-output

[stirtingale]

How is your hosting setup?

My workflow for wp2static is

Host the site in cpanel as www.domain.tld
Add a Wordpress sub-domain as an alias wp.domain.tld

Change the path in wp-config.php to wp.domain.tld

( Doing this enables me to quickly switch back to the primary domain if I wanted to revert the static set up in future )

Access the site via the subdomain and push changes to the www.domain.tld domain.

--

However, if you are intending to remove Wordpress completely or use a different host and export your files to the same www.domain.tld then you can do that.

For clients who do not want to use the serverless set up I run a weekly cron backup to Netlify of their sites that I can fallback to if their hosting goes down. I do this using www.domain.tld as the Wordpress install and destination URL and it works just fine

[stirtingale]

@salamander2 the basic auth is if you protect your whole site install with a htaccess user/pass ( e.g. http://www.htaccesstools.com/articles/password-protection/ )
That works well if you bung WP on sub-domain on a cheap shared host etc and then push out to a static service.

I have no idea on the output issues? I think this goes above my pay grade (as an enthusiastic user) and is something you need @leonstafford for.

[McCloud94]

How is your hosting setup?

My workflow for wp2static is

Host the site in cpanel as www.domain.tld
Add a Wordpress sub-domain as an alias wp.domain.tld

Change the path in wp-config.php to wp.domain.tld

( Doing this enables me to quickly switch back to the primary domain if I wanted to revert the static set up in future )

Access the site via the subdomain and push changes to the www.domain.tld domain.

--

However, if you are intending to remove Wordpress completely or use a different host and export your files to the same www.domain.tld then you can do that.

For clients who do not want to use the serverless set up I run a weekly cron backup to Netlify of their sites that I can fallback to if their hosting goes down. I do this using www.domain.tld as the Wordpress install and destination URL and it works just fine

this sounds like a great idea.. thanks a lot.

If you say thought that the plugin should usually work also with the same domain, then there must be a different issue.

I can't get it to export the html for some reason.

[stirtingale]

I can't get it to export the html for some reason.

How are you actually set up? Is the 'public' address accessible. e.g. if your curl domain.tld does that return your site?

One thing I find helpful is running the generate command via WP-CLI instead of the plugin interface.

There is also a debug option which might tell you the reason

[McCloud94]

I can't get it to export the html for some reason.

How are you actually set up? Is the 'public' address accessible. e.g. if your curl domain.tld does that return your site?

One thing I find helpful is running the generate command via WP-CLI instead of the plugin interface.

There is also a debug option which might tell you the reason

I am afraid some of the terms might be too technical for me ^ ^

that was the weird thing.. when enabling the debug mode, I didn't get any option to see/export the log.

[stirtingale]

@McCloud94 the debug log is a txt file in your /uploads directory @ elementor/wp2static#447 (comment)

[salamander2]

@stirtingale I am having this problem too. I've set up WP on a local linux mint 18.3 server at home, duplicated my WP site and WP2Static simply will not work. There are no errors other than
Failed during "Crawling initial file list", .

• Other info: PHP 7.1.
• Location of WP: /var/www/html/scripsi
• log files: only the first two: Detected WordPress URLS and Modified Crawl List. Crawled Links has a /
• destination url: I've tried various things here but it makes not difference. Obviously a program on my local server is not going to be allowed to actually write to my hosted website. But it should just set up the pages wit the correct links so that I can upload them later.

I chose output to subdirectory on current server

If I try, output to zip file I get the meaningless same error.

[salamander2]

@stirtingale

What is this for? Use basic authentication | My WP site requires Basic Auth to access

Is this my wordpress admin password? Is this my sudo password? Other plugins don't need a password to run. I'd love to have a sentence explanation added to this "Crawling" page.

 

[Freaver]

Dear sir @leonstafford

I have the same issue as the OP has. 4 Months ago I was able to deploy my site from wp2static and suddenly each time I perform a request to start exporting my static site, I get the error: Failed during "Crawling discovered URLs". I have no clue on what to do or fix this problem. Does anyone here have a few solutions which I could utilize?

Kind Regards,

Kendrick

[salamander2]

I'd suggest trying the "Simply Static" plugin. That worked for me. On Wednesday, July 31, 2019, 5:49:34 AM EDT, Freaver <[email protected]> wrote: Dear sir @leonstafford I have the same issue as the OP has. 4 Months ago I was able to deploy my site from wp2static and suddenly each time I perform a request to start exporting my static site, I get the error: Failed during "Crawling discovered URLs". I have no clue on what to do or fix this problem. Does anyone here have a few solutions which I could utilize? Kind Regards, Kendrick — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

[N4rsha]

I'm having the same issue, is there any solution? Leonard doesn't reply

[leonstafford]

@salamander2, @N4rsha - please stay tuned for version 7 release, as it solves many issues and makes troubleshooting easier.

In the meantime, you may look at these places for more information:

• your servers's PHP/webserver logs
• the browser console's JavaScript or Network tabs

You may also try disabling all plugins and switching to the TwentySeventeen or TwentyNineteen themes to try to isolate what is causing the failure on your particular environment.

[salamander2]

Sorry, I dont use this email account much. I ended up with a plugin called SimplyStatic or SimpleStatic or something like that. It worked fine. On Sunday, August 25, 2019, 5:42:11 PM EDT, N4rsha <[email protected]> wrote: I'm having the same issue, is there any solution? Leonard doesn't reply — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

[leonstafford]

Hi all,

Sorry for letting this issue go stale. I've chatted with some of you over Telegram/email since, but for those seeing this issue, V7 is now ready for testing and solves a lot of common environmental issues: https://github.com/WP2Static/wp2static/releases/tag/7.0-alpha-003