connection to aws cloudfront /index.html error

Hi @atleet, first of all thanks for using Staatic.

From what I understand, the static version of your site has been deployed to an AWS S3 bucket with website hosting enabled. A CloudFront distribution has been created with the S3 website bucket configured as the origin. When requesting as asset through CloudFront like style.css, CloudFront translates this to style.css/index.html, is that correct?

In order to set up this configuration, did you follow this article from our documentation? https://staatic.com/documentation/administrator-guide/deployment/amazon-s3-or-compatible/#preparation

Also, can you find the asset file in S3 using the AWS Console, within the correct path? Does the origin (S3 website) asset URL work?

Looking forward to your feedback.

Hi guys, i got it fully running and facing the last problem ??

how can i disable the backend wordpress from being viewed or indexed in search engine?

Thanks!

Hi @atleet, we’re glad to hear that you managed to resolve the issue. It would be good to hear what the cause was, for future reference and helping others facing the same issue.

Regarding your question, there are multiple methods to prevent or discourage search engines from indexing your backend WordPress site, for example:

– restricting site access using HTTP basic authentication or similar;
– implementing the “X-Robots-Tag” HTML meta tag or HTTP header;
– implementing the robots.txt file;
– setting the Search engine visibility setting in WP-Admin > Settings > Reading to Discourage search engines from indexing this site.

We highly recommend HTTP basic authentication or the X-Robots-Tag HTTP header, or a combination of the two. The X-Robots-Tag HTML meta tag, robots.txt and Search engine visibility setting are discouraged, because these can leak into your public static site, preventing it from being indexed as well.

Please let us know if this answers your question.

i created a new bucket and it worked then

i setup the HTTP basic athentification (directory privacy) for public_html but now the Staatic cant reach the files anymore, its just endless spinning in “Preparing publication.”

is there any workaround for this?

Thanks guys!

• This reply was modified 1 year, 9 months ago by atleet.

Alright, thanks for sharing.

In order for Staatic to be able to crawl your site with HTTP basic authentication enabled, you need to make sure that the basic authentication credentials are filled in within Staatic > Settings > Advanced > HTTP authentication. See also this article from our documentation: https://staatic.com/documentation/administrator-guide/configuration/advanced-settings/#http-auth

Does this resolve the issue for you?

This thread was marked resolved due to a lack of activity, but you’re always welcome to re-open the topic.