You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thank you for your support in helping us improve FlyonUI!
We’ve received your submission and will respond within few business days. Our team handles issues one at a time, and we’ll be reviewing yours as soon as possible.
In the meantime, any additional details or a reproducible example would be greatly appreciated and will help us resolve the issue more efficiently.
The error regarding “Cross-Origin-Resource-Policy response header” indicates a CORS (Cross-Origin Resource Sharing) issue. This happens when a resource (like the widget from api.producthunt.com) is blocked from being loaded due to cross-origin security policies. To resolve this:
Check the CORS settings on the external service (https://api.producthunt.com). It’s possible that the ProductHunt API is not configured to allow loading of its resources from flyonui.com.
Use a proxy or host the resource locally: As a workaround, you could fetch the image or asset server-side and serve it from your own server to avoid CORS restrictions.
Could you please share a screenshot of how the webpage looks line in the browser?
Also, consider sharing the browser developer tools console tab screenshot.
What version of FlyonUI are you using?
No response
Which browsers are you seeing the problem on?
Safari
Reproduction URL
https://flyonui.com
Describe your issue
Cancelled load to https://api.producthunt.com/widgets/embed-image/v1/featured.svg?post_id=495768&theme=light because it violates the resource's Cross-Origin-Resource-Policy response header.
Failed to load resource: Cancelled load to https://api.producthunt.com/widgets/embed-image/v1/featured.svg?post_id=495768&theme=light because it violates the resource's Cross-Origin-Resource-Policy response header.
Failed to load resource: 发生SSL错误,无法建立到该服务器的安全连接。
Failed to load resource: 请求超时。
The text was updated successfully, but these errors were encountered: