-
Notifications
You must be signed in to change notification settings - Fork 23
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
"We couldn't find this image" - background image is replaced by 404 image #134
Comments
Could be some sort of api/token limit...? |
I've only ever used the defaults, so I doubt that's the problem here. Looking at the issue tracker growing, this git might gonna be stale soon. I've removed this app from my instance, as I don't want to have unmaintained apps running on my personal server. Leaving this open though. |
It is also possible that the public unsplash api finally stopped working. The new authenticated api is working already, but you'll need a token for it. I need to update the how-to for that. Also release the current master. |
The url for the api seems to have changed. There seems to be a new api for getting a random image but you need a api-token to access it. Maybe add a configuration-option for this and let users register at unsplash. |
Can you check if this is present in 3.0.0 with the new authenticated api? It is very likely that the original api was finally closed. |
With the new API, it seems to work again. I would recommend removing the unauthenticated API from the dropdown. |
Closed with v3.0.2. It will remove unsplash and fall back to a supported provider. |
use GitHub reactions 👍 to show that you are affected by the same issue. Please don't comment if you have no relevant information to add!
Describe the bug:
Images are not loaded, a 404 error page is shown instead in the background.
background image get's replaced by this 404 error page:
https://images.unsplash.com/source-404?fit=crop&fm=jpg&h=800&q=60&w=1200
Screenshots:
Server:
Additional Information:
I can reach unsplash.com just fine from my network, so I doubt it is a dns or geo-block issue (location: Germany)
The text was updated successfully, but these errors were encountered: