Unsolved 403 errors for assets which work fine

[Skites2]

Hi,
I am facing some issue with our moz pro account
We have images stored in a s3 buckets

eg: https://assets2.hangrr.com/v7/s3/product/151/beige-derby-cotton-suit-mb-2.jpg
Hundreds of such images show up in link opportunities - Top pages tool - As 403 ... But all these images work fine and show status 200. Can't seem to solve this. Thanks.

[thejohnwatson]

Hi,

I'm also experiencing a similar issue on my German-based website, https://kopfoderzahl.org/. We use S3 buckets for storing images, and while these images load perfectly fine with a 200 status, they appear in tools like "Top Pages" with a 403 status under link opportunities. It's puzzling since the URLs work as expected when accessed directly.

It seems like a mismatch between how the tool crawls or interprets these URLs and the actual server response. If anyone has insights or potential solutions, I’d love to hear them. Thanks!

[Bastin00]

Hi,

I am facing some issues with our Moz Pro account. We have images stored in S3 buckets, and hundreds of these images appear in the Top Pages tool under link opportunities, showing a status of 403, even though they actually return a status of 200. I can't seem to resolve this issue.

I've encountered a similar problem on my exclusive website, baddiesonlytv, and any insights would be greatly appreciated. Thanks!

[R3_Infosolution1]

@Skites2 R3 Info Solutions is a leading digital marketing company in Kerala, offering comprehensive services to help businesses grow online. With a focus on innovative strategies and proven results, we specialize in SEO, PPC, social media marketing, content creation, and web development.

[GKIS]

@Skites2

You're encountering a discrepancy between your actual image URLs, which return a status 200, and what Moz Pro's Top Pages tool is reporting as 403 errors. Here are some possible reasons and solutions for this issue:

Temporary Access Denials: If the images are stored in Amazon S3 buckets, there could have been temporary access issues when Moz Pro crawled your site. S3 permissions may have momentarily restricted access, resulting in a 403 status at the time of the crawl. Ensure that your S3 bucket and object permissions are set correctly, and make sure they are publicly accessible if intended.

Bucket Policy or CORS Issues: Review your S3 bucket policy and Cross-Origin Resource Sharing (CORS) settings. Sometimes, misconfigured policies can lead to access restrictions that are not consistent, causing 403 errors during certain types of requests or crawls.

IP Blocking or Rate Limiting: Some services or firewalls may block specific IP addresses or impose rate-limiting, which could block the Moz crawler from accessing the images. Ensure that your security settings are not inadvertently blocking bots or crawlers, including Moz’s IP ranges.

Time-Sensitive URLs: If the URLs you are using are pre-signed S3 URLs with an expiration time, it’s possible that Moz crawled the URLs after they had expired. Ensure that you are using permanent or properly timed URLs when linking images on your site.

Check with Moz Support: Since this is occurring within Moz Pro's tool, it might also be a good idea to reach out to their support team. They can provide insights into how their crawler is interpreting your links and whether there are any specific factors causing the 403 errors.

By ensuring your S3 permissions are set correctly, reviewing your access policies, and possibly whitelisting Moz’s crawler, you should be able to resolve this issue. If the problem persists, Moz’s support team can offer further assistance.

[thejohnwatson]

Hi WhiteboardCreations,

I’ve encountered a similar issue on my own website, where I host PDFs. The images were returning 200 when accessed directly but showed up as 403 errors in various tools. In my case, the problem was related to S3 bucket permissions, particularly the settings for public access and how some crawlers interact with them. Double-checking the permissions and ensuring they are correctly configured for Moz's crawler could help. You might also need to refresh Moz's cache for these URLs.

For reference, I also run a PDF-related site: OceanofPDF , and this solution worked for me.

Hope this resolves your issue!

[TomiChpaks]

Hello! My passion for gambling led me to the 1 win casino website, and I couldn't help but leave a review. You can immediately feel that this place is created with love for details: intuitive design, a huge selection of slots and, most importantly, generous bonuses. I have used the opportunity to get free spins more than once, and it really works! If you are looking for a reliable platform to play on, I recommend 1win-freespins.

[semaseti582]

@Stephon110

We provide cheap and premium cals near Sector 56 Noida with cash on delivery.
https://maps.google.com.sa/url?q=https://noidacallgirls.in
https://cse.google.com.sa/url?q=https://noidacallgirls.in
https://cse.google.com.pe/url?q=https://noidacallgirls.in
https://images.google.com.pe/url?q=https://noidacallgirls.in
https://maps.google.com.pe/url?q=https://noidacallgirls.in
https://images.google.com.pk/url?q=https://noidacallgirls.in
https://cse.google.com.pk/url?q=https://noidacallgirls.in
https://cse.google.by/url?q=https://noidacallgirls.in
https://maps.google.by/url?q=https://noidacallgirls.in
https://www.google.no/url?q=https://noidacallgirls.in
https://cse.google.dz/url?q=https://noidacallgirls.in
https://maps.google.dz/url?q=https://noidacallgirls.in
https://images.google.dz/url?q=https://noidacallgirls.in
https://images.google.tn/url?q=https://noidacallgirls.in
https://maps.google.tn/url?q=https://noidacallgirls.in
https://cse.google.com.np/url?q=https://noidacallgirls.in
https://maps.google.com.np/url?q=https://noidacallgirls.in
https://images.google.com.np/url?q=https://noidacallgirls.in
https://cse.google.com/url?q=https://noidacallgirls.in
https://cse.google.co.ma/url?q=https://noidacallgirls.in
https://images.google.co.ma/url?q=https://noidacallgirls.in
https://maps.google.com.jm/url?q=https://noidacallgirls.in
https://cse.google.com.jm/url?q=https://noidacallgirls.in
https://images.google.com.jm/url?q=https://noidacallgirls.in
https://maps.google.mu/url?q=https://noidacallgirls.in
https://cse.google.mu/url?q=https://noidacallgirls.in
https://images.google.mu/url?q=https://noidacallgirls.in
https://cse.google.li/url?q=https://noidacallgirls.in
https://maps.google.li/url?q=https://noidacallgirls.in
https://images.google.li/url?q=https://noidacallgirls.in
https://maps.google.mn/url?q=https://noidacallgirls.in
https://images.google.mn/url?q=https://noidacallgirls.in
https://cse.google.mn/url?q=https://noidacallgirls.in
https://images.google.com.gt/url?q=https://noidacallgirls.in
https://cse.google.com.kh/url?q=https://noidacallgirls.in
https://images.google.com.kh/url?q=https://noidacallgirls.in
https://maps.google.com.kh/url?q=https://noidacallgirls.in
https://images.google.com.lb/url?q=https://noidacallgirls.in
https://cse.google.co.ke/url?q=https://noidacallgirls.in
https://www.google.com.co/url?q=https://noidacallgirls.in
https://cse.google.com.mt/url?q=https://noidacallgirls.in
https://maps.google.iq/url?q=https://noidacallgirls.in
https://cse.google.iq/url?q=https://noidacallgirls.in

https://cse.google.cm/url?q=https://noidacallgirls.in
https://maps.google.cm/url?q=https://noidacallgirls.in
https://cse.google.com.gi/url?q=https://noidacallgirls.in
https://images.google.mg/url?q=https://noidacallgirls.in
https://maps.google.la/url?q=https://noidacallgirls.in
https://cse.google.la/url?q=https://noidacallgirls.in
https://www.google.com.sa/url?q=https://noidacallgirls.in
https://maps.google.com.om/url?q=https://noidacallgirls.in
https://images.google.com.om/url?q=https://noidacallgirls.in
https://cse.google.com.om/url?q=https://noidacallgirls.in
https://images.google.tk/url?q=https://noidacallgirls.in
https://maps.google.tk/url?q=https://noidacallgirls.in
https://cse.google.tk/url?q=https://noidacallgirls.in
https://images.google.co.mz/url?q=https://noidacallgirls.in
https://cse.google.co.mz/url?q=https://noidacallgirls.in
https://maps.google.co.mz/url?q=https://noidacallgirls.in
https://images.google.bs/url?q=https://noidacallgirls.in
https://images.google.al/url?q=https://noidacallgirls.in
https://cse.google.al/url?q=https://noidacallgirls.in
https://images.google.tm/url?q=https://noidacallgirls.in
https://cse.google.tm/url?q=https://noidacallgirls.in
https://maps.google.com.bh/url?q=https://noidacallgirls.in
https://maps.google.dm/url?q=https://noidacallgirls.in
https://images.google.dm/url?q=https://noidacallgirls.in
https://maps.google.com.sb/url?q=https://noidacallgirls.in
https://images.google.com.sb/url?q=https://noidacallgirls.in
https://cse.google.com.sb/url?q=https://noidacallgirls.in
https://cse.google.kg/url?q=https://noidacallgirls.in
https://images.google.kg/url?q=https://noidacallgirls.in
https://maps.google.kg/url?q=https://noidacallgirls.in
https://maps.google.sc/url?q=https://noidacallgirls.in
https://images.google.sc/url?q=https://noidacallgirls.in
https://cse.google.sc/url?q=https://noidacallgirls.in
https://www.google.com.pk/url?q=https://noidacallgirls.in
https://www.google.rs/url?q=https://noidacallgirls.in

[thejohnwatson]

Thanks for bringing up this issue regarding 403 errors! I faced a similar problem with one of my websites where specific assets were giving 403 errors randomly. It took me a while to figure out that the issue was related to server permissions. After tweaking the permissions and making sure all assets were properly accessible, the problem was resolved.

By the way, if anyone’s interested, I’ve implemented some of these solutions on my site https://letmewatchthiss.com/, and it’s been working fine since then. Maybe it might help someone facing a similar issue.

[JamesMason4776]

Thanks for sharing this insight on 403 errors—it can be puzzling when things seem to work fine but still trigger these issues. On a different note, I found a fantastic resource for Canyon County Jail Information that provides up-to-date details and results. It’s a great site if you need accurate and current information about the local jail system!

[Stephon110]

@Skites2 Hi,

Here are some quick steps to resolve your issue with Moz Pro and S3 images showing 403 errors:

1. Check Permissions: Ensure S3 bucket and object permissions are set to public-read or have a policy allowing public access.

2. CORS Configuration: Verify CORS settings in your S3 bucket to allow access from Moz Pro.

3. CloudFront: If using CloudFront, ensure it's configured correctly for public access.

4. IP Blocking: Ensure no IP restrictions are blocking Moz Pro's IP addresses.

5. Logs: Check S3 access logs for 403 errors to understand the cause.

6. Contact Support: Reach out to Moz Pro support for specific guidance on their access requirements.

These steps should help resolve the 403 errors you're seeing.