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
The project has been live for a few months with no issues displaying the images through the gateway. The project was built with nextjs and the next config has been set correctly to include the gateway link in nextjs config image remote patterns.
From today all images are not loading from the gateway with a net::ERR_SSL_PROTOCOL_ERROR being returned.
Did infura change something on their backend? It's strange that this error is showing for this gateway, on other dedicated gateways I have the error is not showing.
Is there a fix / diagnosis?
The text was updated successfully, but these errors were encountered:
No i didn't find the problem really, i checked all certificates etc. and everything is correct so it's very strange, the only conclusion I can logically draw is that some ISP's here in the US block ipfs gateways , it's happened quite a lot of web3 storage, hence why i moved to infura... so it might have been that ? If you have any other trouble shooting suggestions for smth like this would love to hear it
I have a custom infura gateway with pinned images that are shown on this website https://www.f3manifesto.xyz/
The project has been live for a few months with no issues displaying the images through the gateway. The project was built with nextjs and the next config has been set correctly to include the gateway link in nextjs config image remote patterns.
From today all images are not loading from the gateway with a
net::ERR_SSL_PROTOCOL_ERROR
being returned.Did infura change something on their backend? It's strange that this error is showing for this gateway, on other dedicated gateways I have the error is not showing.
Is there a fix / diagnosis?
The text was updated successfully, but these errors were encountered: