Configuration Issues

  • Resolved Ben

    (@benleow)


    2 years ago

    I have this error in my Staatic Settings page;

    Configuration Issues
Some configuration issues have been found which require your attention:

Staatic is unable to access your WordPress site
Client error: <code>GET https://domainname/wp-content/plugins/staatic/readme.txt</code> resulted in a <code>403 Forbidden</code> response: <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>403 Forbidden</title> </head><body> <h1>Forbidden (truncated...) .

    How do I fix this?

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author Team Staatic

    (@staatic)

    Hi @benleow, in order to generate the static version of your site, Staatic needs to be able to access your dynamic WordPress site over http/https. This error indicates that it got a 403 permission denied error preventing it from crawling.

    Could it be that you have restricted access to the site based on IP address? In that case the server IP should be accepted as well, since HTTP requests from the plugin originate from the server.

    Thread Starter Ben

    (@benleow)

    thanks again for the fast reply.

    Own server IP restriction is set in .htaccess, php settings or other location in Cpanel?

    Anyway, after I reported this, I enabled HTTP Authentication for the website and set the username and password in Staatic Settings (Advanced) and the error is gone.

    Then I initiated Publish. I managed to crawl over 2,000 resources until it hits this error…

    Error during task Staatic\WordPress\Publication\Task\CrawlTask: The path of a URI without an authority must not start with two slashes "//"

    Plugin Author Team Staatic

    (@staatic)

    Restricting access by IP on cPanel can be done using a .htaccess file. However, if you have configured HTTP basic authentication, then that should be enough.

    Regarding the other error, there is either an invalid URL referenced somewhere within your site, or Staatic was unable to extract/transform the URL for some reason.

    In order to identify the responsible URL, can you please provide us with a diagnostics JSON file as well as the publication logs?

    The diagnostics file can be generated by going to /wp-admin/admin.php?staatic=diagnostics. It contains some environment information that helps us troubleshoot the issue (feel free to open it in a text editor to verify).

    In order to export the publication logs, you should first change these plugin settings (under Advanced):

    Logging: Extensive Logging
    HTTP Concurrency: 1

    Then start a new publication and once it has finished, go to the publication details and click the Logs tab. Then click the Export button at the top of the page.

    Both files may be sent to [email protected]. Looking forward to your feedback.

    Plugin Author Team Staatic

    (@staatic)

    After some troubleshooting we found out that the error was caused by a URL with double slashes at the start of the path segment (https://example.com//something), which Staatic was unable to process.

    This should be fixed in the next release of the plugin.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Configuration Issues’ is closed to new replies.