Hi all,
I tried to connect to OHIF using osimis/orthanc:master-full-unstable
image but it’s not showing up on the orthanc explorer.
I checked the logs and saw that the OHIF plugin is not getting registered.
This is my configuration JSON file:
{
"AuthenticationEnabled": false,
"DicomWeb": {
"Enable": true,
"Root": "/dicom-web/",
"EnableWado": true,
"WadoRoot": "/wado",
"Ssl": false,
"QidoCaseSensitive": false,
"Host": "",
"StudiesMetadata": "Full",
"SeriesMetadata": "Full",
"PublicRoot": "/dicom-web/",
"Servers": {}
},
"OHIF": {
"DataSource": "dicom-web",
"preload": true,
"UserConfiguration": "ohif.js",
"RouterBasename": "/custom/route/"
}
}
You might need to enable the PlugIn if it doesn’t autoload when the config is present:
OHIF_PLUGIN_ENABLED=“true”
The demo is working:
https://demo.orthanc-server.com/app/explorer.html
Might be getting hit quite a bit. That might help me. Is the ohif.js in the plug-in or somewhere else. My RouterBasename probably needs to be different also with a front-end proxy.
/sds
1 Like
Thanks, Orthanc registered the viewer plugin, but I am getting an error.
The specified path does not point to a regular file: The path does not point to a regular file: /etc/orthanc/ohif.js
I am mounting my ohif.js file this way:
orthanc:
...
environment:
OHIF_PLUGIN_ENABLED: true
volumes:
# Config
- ./ohif.js:/etc/orthanc/ohif.js
I had the same issue with that originally
E0619 23:33:46.252771 PluginsManager.cpp:153] The specified path does not point to a regular file: The path does not point to a regular file: ohif.js
Are you sure the host mapping is correct ? You might need to rebuild after changing that also ?
I have:
- ./pacs/ohif.js:/etc/orthanc/ohif.js, but that is where mine is on the host, and I don’t get that error anymore.
"UserConfiguration": "ohif.js",
I’m not sure where that is in the container really, I presume /etc/orthanc/ohif.js
/sds
I am using docker compose, are you suggesting that I need to use a docker build instead?
I checked, and my orthanc.json and ohif.js are in the same directory, so I am unsure of what the issue is.
You don’t need to use Docker, but you can. Try an absolute path ?
/sds
Hello,
The best way for people to help you would be to provide a minimal working example containing all your Docker Compose files.
Kind Regards,
Sébastien-
Thanks, using the absolute path worked.