Configure latest version to use local orthanc
See original GitHub issueHi all I’m having trouble configuring the newest version of the Viewer to get data from an instance of the OrthaNC server that I have running on the same machine. I’m currently using the config from docker_openresty-orthanc-keycloak.js as start but I am running into
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at http://127.0.0.1/auth/realms/ohif/.well-known/openid-configuration. (Reason: CORS header \u2018Access-Control-Allow-Origin\u2019 missing).
IIIRC, the previous version handled this by using a proxy. How do I configure this version to do so? Or is there some other problem? Any help with this issue would be greatly appreciated.
Howard
Issue Analytics
- State:
- Created 4 years ago
- Comments:25 (11 by maintainers)
Top Results From Across the Web
Configuration of Orthanc
This is how the configuration files are provided with the Windows Installer. Once your configuration file is ready, start Orthanc by giving it...
Read more >Configure latest version to use local orthanc - Bountysource
Hi all. I'm having trouble configuring the newest version of the Viewer to get data from an instance of the OrthaNC server that...
Read more >How to Install and Configure the Orthanc DICOM Server
Orthanc is a FREE open-source DICOM Server that allows you to perform DICOM operations such as send, receive, query, and retrieve DICOM ...
Read more >How to configure Orthanc to work with Ginkgo Cad
We are planning to use Orthanc and Ginkgo Cad . ... Local PACS: ... Attached are my actual Orthanc configuration file for the...
Read more >Orthanc Knowledge Base - Confluence
For this, create a new Docker image layer on top of osimis/orthanc that adds your JSON configuration files in /etc/orthanc and the desired...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
wadoUriRoot, qidoRoot, and wadoRoot are paths to where some PACS server is serving DICOMWeb endpoints. The default Orthanc API at localhost/ is NOT DICOMWeb, it is their own custom REST API, and pointing OHIF at those endpoints will not work.
Orthanc is typically serving the dicom-web plugin at /dicom-web/, so that’s what your wadoUriRoot, qidoRoot, and wadoRoot should be. (in your case localhost/dicom-web since you have a proxy)
Well, I seem to have it working using nginx to reverse proxy it. That would have been easier if I knew more about what I was doing, and I can’t shake the feeling I shouldn’t really have to do that. But oh well.
Thanks so much for everyone’s help. If anyone is interested, I can post the working config files, but there isn’t much interesting, it was just finally getting all of the pieces in place.
Thanks again Howard