Whether you're troubleshooting specific issues or seeking to ensure smooth integration of TwicPics, you may encounter or anticipate the scenarios below:

Experiencing these? Whitelisting TwicPics should be your next step.

The primary way to resolve these conflicts is to whitelist TwicPics by using the x-twicpics-token header. By default TwicPics add the x-twicpics-token header to every request made to your origin.
This token's value is specific to your domain and can be found on the backend:

Whitelist the token: Ensure that your server or security layer accepts requests that come with the x-twicpics-token header. The general rule is: "if a request has this header with its unique value, it should be allowed access."

If for some reason you cannot whitelist using the token, TwicPics offers alternative authentication methods for private servers:

You can setup one during path creation or edition.

TwicPics doesn't use fixed IPs due to the decentralised nature of our service. If your server uses IP filtering as a security measure we highly recommend to add, or to replace it by, header authentication with the x-twicpics-token header provided.

As a last resort, if you need to continue using IP-based security, you can find Cloudfront IP masks used by TwicPics at this address: http://d7uri8nf7uskq.cloudfront.net/tools/list-cloudfront-ips for temporary whitelisting, especially during development or troubleshooting phases.

TwicPics aims to provide seamless image optimization. Ensuring our service is whitelisted will help maintain uninterrupted service and optimal image delivery. If any conflicts arise, always refer back to these solutions or reach out to our support team for further assistance.