Hi everyone, today I start to try an instance of Orthanc in Debian 11, I have a CR modality configured to send studies to a AET and Port that I can’t change (e.g. AET: “PACS-SERVER”, port 104) so, I try to change this info in the orthanc.json configuration file, but when I change the port from 4242 to 104, appears the next error in file logs "The DICOM port is privileged (104 is below 1024), make sure you run Orthanc as root/administator".
Someone have the same problem?
Orthanc.log (3.96 KB)
Hi,
Do you also get this error message when you try to run Orthanc as root as suggested by the error message ?
If yes, then, you should check if there’s another app using the same port. You may try this command to list all TCP port usage:
netstat -puta
HTH,
Alain
Hello Alain, yes I do run Orthanc as root, and I check for ports already used and 104 is not in there, the weird thing is that I installed Orthanc, in an IP segment 192.168.1.X, change the port 4242 to 104, and also enable LocalAet configuration in the Network Topology section of the Orthanc.json configuration file with the actual IP of the CR Modality network (172.16.1.X), but I let the object name of LocalAet “untrusted”, and there is when throw the “PORT PRIVILEGED” error message while trying to run Orthanc, so I change the “Untrusted” name for “EFILM”, the same as the AETitle (this is the AET configured in the CR Modality to send DICOM images), Orthanc runs normally but the Orthanc explorer not work, then I try to reinstall all again from the beginning, but the error message “PORT PRIVILEGED” still appear when change 4242 to 104
Ports below 1024 in Linux are privileged so you may need to run the following:
setcap ‘cap_net_bind_service=+ep’ /path/to/Orthanc_executable
This should allow you to use port 104 for Orthanc.
HTH
Thank you BNOEAFK, finally I make it work with the “setcap” command, this issue is solved now.