Orthanc is still not working : Please I need your help.

Google Groups archive
1

Hello; Good morning to you all.
Please I need help to finalize the setup of ORTHANC.

This is the answer the web browser is responding when I launched the address : http://135.181.176.237/:18042/ ( I have confiured an access from remote to the server through the port 18042

and
I have also set the option “RemoteAccessAllowed” to “true” in the configuration file.

but I am still receiving this message from my dispaly :

Désolé, impossible d’accéder à cette page.

135.181.176.237 a refusé la connexion.

Essayez :

  • Vérification de la connexion
  • Vérification du proxy et du pare-feu

ERR_CONNECTION_REFUSED

Masquer les détails

Capture.JPG

I configure the password already in the file credentials.json
as you can read below :

{
/**

  • Sensitive configuration options. This file must not be
  • publicly-readable. It must only be readable by the users that run
  • the “orthanc” service.
    **/
    // The list of the registered users. Because Orthanc uses HTTP
    // Basic Authentication, the passwords are stored as plain text.
    “RegisteredUsers” :
    {
    “alice” : “alicePassword”
    },
    }

credentials.json (373 Bytes)

orthanc.json (37.1 KB)

2

In your orthanc.json file you did not change HttpPort from 8042 to 18042

Not sure if you are trying to do a reverse proxy, which is a separate issue.

If that does not work, please post the contents of your orthanc log file.

BR

3

Thanks a million for your response.
I will apply what you recommend and revert.
Could you please advise on where to find the logs file of ORTHANC SERVER ?

Clement BAVOUA !

4

Take a look at the orthanc book: https://book.orthanc-server.com/faq/log.html

BR

5

Thanks/ I appreciate. I am actually going through the different steps listed there and will revert
when I finish.

6

Hi Clemente

Try removing the slash before the colon

http://135.181.176.237:18042/

7

Thanks a million for your suggestion.
I’ve gone through the installation process again from scratch and it looks like they are modules that are in conflict with others during the installation process.

Thanks once again.
it is now working properly.