Hello everyone,
I have the same error as in this case: https://forum.omeka.org/t/universal-viewer-not-loading-over-https/18530/1
I have added in the .htaccess the following line:
SetEnv HTTPS “on”
Now I get the following error:
ERR_SSL_PROTOCOL_ERROR
I hope someone can help me.
I have looked and also all the images are broken.
If I add:
RequestHeader set X-Forwarded-Proto https.
I get this error:
’ was loaded over HTTPS, but requested an insecure XMLHttpRequest endpoint '.
The SetEnv HTTPS “on” option isn’t a good one and will cause problems. I’ve edited my old post in that thread to make that clearer.
Can you share a link to your site?
OK, and can you do just the “X-Forwarded-Proto” option mentioned in your first post so I can see what that looks like?
Hello,
I have added the following line:
RequestHeader set X-Forwarded-Proto https
It still doesn’t work.
Regards
Felix
OK: I think the “X-Forwarded-Proto” change is a good one and you should keep it. Your site is now correctly generating HTTPS urls as its absolute URLs.
Now, you still have an issue that the manifest you’re trying to load on that page is an HTTP URL. I don’t know exactly which modules and so on you’re using, but I’d suggest that the “bad” URL here has just been saved somewhere and needs to be cleared/replaced. Does the problem happen the same way if you make a new item?
Hello,
Now creating a new item, it works: Test 2 · Weltkriegsalben-Archiv
Thank you very much.
Regards Felix
Hello,
Now I have noticed that if I upload the image everything is fine, but then once I edit it as I add a description it brokes and appears in bad quality in UniversalViewer.
From the admin panel it looks like this:
Omeka s Admin Panel:
Web:
Item link: TEST 2 · Weltkriegsalben-Archiv
Greetings Felix
Ultimately the issue there is that your IIIF manifest is pointing to tiles that don’t actually exist, like this one as an example: https://weltkriegsalben-archiv.de/omeka-s/files/tile/89b57689547ff478d33f6db237a29de0b3d7ee99_files/10/1_1.jpg . Similarly on the backend OpenSeadragon is trying to show the tiles for the image, but they don’t actually exist.
This probably comes down to the module you’re using to make those tiles, and/or the IIIF manifest, and some sort of configuration or other problem in that area. Maybe the background job that’s supposed to produce the tiles isn’t running, just as one guess? (You could check in the Jobs admin section on that.) I can’t provide much help on this tiling front since that kind of stuff is all the work of other developers.
Hello,
So who can help me?
And what do those Http/Https errors in the console have to do with it?
Greetings Felix
Hello,
I just thought of something, the requests point to for example: /omeka-s/files/tile/13e5a7a7a6d4a6eea2f4eef324579a292eede17858_files/10/0_0.jpg
Where there is always in front ‘/omeka-s’,
I first install Omeka in the folder called “omeka-s” and then through the cmd, I moved all the contents of the folder “omeka-s” to the root of the web. Now I have checked in the FileManager and in this path are the images ‘weltkriegsalben-archiv.de/files/original’.
So I must have to change some configuration to change that path that includes ‘/omeka-s’.
Could this be the reason? How do I fix it?
Greetings Felix
It’s probably possible to do this other ways, but you might try simply uninstalling the modules and reinstalling them, to clear out their saved settings, since I believe you’re just starting out. And you’d probably have to add files again after reinstalling the modules to test if the problem is fixed.
Now it works!
How can I remove the universal viewer on this page?
I believe that’s just something the Universal Viewer module is adding there… if you look at the documentation or README for the module, I believe it explains how you could turn that off.
This topic was automatically closed 360 days after the last reply. New replies are no longer allowed.
