-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
.PNG .JPG and .GIF files cannot be viewed via IPFS import #16758
Comments
@GeetaSarvadnya if you turn off Shields, does it render? I had a similar issue on Linux, also
/cc @spylogsster |
This seems to be a variant of #13641 however here we are on a trusted API port (45004) that tries to fetch the image from the trusted Gateway port (45083). This is a pretty safe environment, as both Origins are controlled by Brave (brave runs go-ipfs binary, which exposes those ports) I think the right way of fixing this class of bugs is to allow API port to fetch data from local Gateway. |
@stephendonner with Shields ON/OFF I am getting the same issue. |
This is the same issue as #16752 (comment) The fix here is to wait until we have go-ipfs 0.9.1 with bugfix release of webui: ipfs/kubo#8243 |
blocked by ipfs/kubo#8243 |
@GeetaSarvadnya mind retesting with This worked for me using
Verified on Linux as well. Imported images for PNG/JPG/JPEG/GIF all show and can be loaded as well |
Verified
and
|
@stephendonner Apologies somehow missed the issue. Today I have verified the issue on Windows 10 x64 - |
Description
Found while testing #16267
.PNG .JPG and .GIF files cannot be viewed via IPFS import
Steps to Reproduce
using --use-dev-goupdater-url
0.9.0
in brave://ipfs-internalsActual result:
.PNG and .JPG files cannot be viewed via IPFS import
Expected result:
Should be able to view .PNG and .JPG files via IPFS import
Reproduces how often:
Easy
Brave version (brave://version info)
Version/Channel Information:
Other Additional Information:
Miscellaneous Information:
cc: @spylogsster @brave/legacy_qa @rebron
The text was updated successfully, but these errors were encountered: