How to Whitelist Pin Generator for Image Access

If you're experiencing broken images when generating pins, you can whitelist our server to allow direct image access. This will improve image loading speed and reliability.

What You Need to Whitelist:

IP Address: 34.107.93.115

User Agent: PinGeneratorBot/1.0 (optional but recommended)

Common Whitelisting Methods:

1. Apache (.htaccess)

# Allow Pin Generator to access images
<Files "*.jpg,*.jpeg,*.png,*.gif,*.webp">
Order Allow,Deny
Allow from 34.107.93.115
</Files>

# Or allow all image requests from Pin Generator
<If "%{HTTP_USER_AGENT} =~ /PinGeneratorBot/">
Require all granted
</If>

2. Nginx

# Define a variable for Pin Generator's user agent
map $http_user_agent $is_pingenerator {
default 0;
"~*PinGeneratorBot" 1;
}

# Optional: You can add logging if helpful for debugging
# access_log /var/log/nginx/pingenerator_image_access.log;

# Image access block
location ~* \.(jpg|jpeg|png|gif|webp)$ {
# Explicitly allow Pin Generator IP
if ($remote_addr = 34.107.93.115) {
# Do nothing — just continue to serve the image
break;
}

# Or allow by user agent
if ($is_pingenerator = 1) {
# Also do nothing — just serve the image
break;
}
}

3. Cloudflare

  1. Go to Security → WAF → Custom Rules
  2. Create a rule: Field: IP Source Address Operator: equals Value: 34.107.93.115 AND Field: URI Path Operator: matches regex Value: .*\.(jpg|jpeg|png|gif|webp)$ Action: Allow Expression:

(ip.src eq 34.107.93.115 and http.request.uri.path matches "(?i).*\\.(jpg|jpeg|png|gif|webp)

quot;)

4. WordPress (functions.php)

// Allow Pin Generator to access images
add_action('init', function() {
if (isset($_SERVER['HTTP_USER_AGENT']) &&
strpos($_SERVER['HTTP_USER_AGENT'], 'PinGeneratorBot') !== false) {
// Allow access to images
header('Access-Control-Allow-Origin: *');
}
});

💡 This helps avoid CORS issues if your server blocks cross-site image access. It won’t restrict or grant access to images directly, but it improves compatibility with tools like Pin Generator.

🔒 Important Notes for WordPress implementation:

  • This doesn’t restrict or protect images — it just helps ensure they can be loaded when needed.
  • If users want actual whitelisting (by IP or UA), they should use their server config (like .htaccess) instead.

Testing Your Whitelist:

  1. Whitelist Pin Generator IP address and user agent
  2. Try generating pins from your website
  3. Try downloading or scheduling pins
  4. Check your server logs for requests from 34.107.93.115
  5. Look for the user agent PinGeneratorBot/1.0

What Happens After Whitelisting:

✅ Faster image loading - Direct connection instead of proxy

✅ Better reliability - No proxy timeouts or blocks

✅ Improved performance - Reduced latency

✅ Automatic fallback - Still uses proxy if direct fails

Need Help?

If you're still experiencing issues after whitelisting:

  • Check your server's error logs
  • Verify the IP address is correctly whitelisted
  • Ensure image files are publicly accessible
  • Contact your hosting provider if needed

Note: Pin Generator will automatically fall back to proxy access if direct connection fails, so your images will still load even if whitelisting isn't configured perfectly.

Still need help?

Open a ticket and our team will get back to you by email, usually within one business day.