What value of <docker-host> needs to be set so that the archive works when moving to another network

[Alexandr Kuznetsov]

Hello.
I installed dcm4chee-5.22 in the docker on Ubuntu on 18.04.
IP-address 192.168.88.62. When starting arc container, I indicated this address as <docker-host>. This works and I can go to this address in the web interface and view studies from the local network 192.168.88.0/24. I also connected weasis and oviyam2 and this works with this address.

But this computer is designed to work on another local network and I cannot know in advance the address that it will have there. How do I define <docker-host> so that I don't have to start the container with the new address.

I tried to define <docker-host> in /ets/hosts, for example,

192.168.88.62    dcm4chee.archive

and run a container with this value:

docker run --network=dcm4chee_default --name arc \
           -p 8080:8080 \
           -p 8443:8443 \
           -p 9990:9990 \
           -p 9993:9993 \
           -p 11112:11112 \
           -p 2762:2762 \
           -p 2575:2575 \
           -p 12575:12575 \
           -e POSTGRES_DB=pacsdb \
           -e POSTGRES_USER=pacs \
           -e POSTGRES_PASSWORD=pacs \
           -e WILDFLY_WAIT_FOR="ldap:389 db:5432" \
           -e AUTH_SERVER_URL=https://dcm4chee.archive:8843/auth \
           -v /etc/localtime:/etc/localtime:ro \
           -v /etc/timezone:/etc/timezone:ro \
           -v /var/local/dcm4chee-arc/wildfly:/opt/wildfly/standalone \
           -d dcm4che/dcm4chee-arc-psql:5.22.0-secure

, but this does not work when I want to log into the server from the local network: Internal Server Error

Может мне кто-нибудь здесь по-русски объяснить, как сделать так, чтобы не нужно было каждый раз при изменении адреса сервера перезапускать контейнер с новым адресом. Английский у меня только с гуглом :(

Thank you in advance

[Gunter Zeilinger]

There must be an entry for the docker host in the DNS of your network, so any web-browser and the archive container resolves the host name to the right IP.

Sent with ProtonMail Secure Email.

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐

, but this does not work when I want to log into the server from the local network.

Может мне кто-нибудь здесь по-русски объяснить, как сделать так, чтобы не нужно было каждый раз при изменении адреса сервера перезапускать контейнер с новым адресом. Английский у меня только с гуглом :(

Thank you in advance

--

You received this message because you are subscribed to the Google Groups "dcm4che" group.

To unsubscribe from this group and stop receiving emails from it, send an email to dcm4che+u...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/dcm4che/f5422032-a3f3-46e6-8871-07062b600139%40googlegroups.com.

[Alexandr Kuznetsov]

Thank you so much for the answer. I registered the host address in the DNS settings of the router. And launched the container with the option

-e AUTH_SERVER_URL = https: //dicom.archive: 8843 / auth \

Now everything works inside the network.

How to connect to the server from outside the network? What ports do I need to forward on the router? And do I need to change the settings in keycloak?

How to organize access if dcm4chee-arc work on virtual computers KVM with a virtual network NAT?

Best regards,

Aleksandr Kuznietsov

понедельник, 23 марта 2020 г., 18:30:37 UTC+2 пользователь gunterze написал:

There must be an entry for the docker host in the DNS of your network, so any web-browser and the archive container resolves the host name to the right IP.

Sent with ProtonMail Secure Email.

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐

To unsubscribe from this group and stop receiving emails from it, send an email to dcm...@googlegroups.com.

[Alexandr Kuznetsov]

воскресенье, 22 марта 2020 г., 16:43:46 UTC+2 пользователь Alexandr Kuznetsov написал:

[Gunter Zeilinger]

For access via public network I recommend to prefer https://dicom.archive:8443/dcm4chee-arc/ui2 over http://dicom.archive:8080/dcm4chee-arc/ui2 for accessing the UI. So you have to forward port 8443 and 8843 at your public access point to the docker host, and take care that host name "dicom.archive" get resolved to the IP of your access point by web browsers on external hosts - e.g. by a correspondent entry in their host file.

Sent with ProtonMail Secure Email.

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐

On Monday, March 23, 2020 8:58 PM, Alexandr Kuznetsov <alexandr.v...@gmail.com> wrote:

Thank you so much for the answer. I registered the host address in the DNS settings of the router. And launched the container with the option

-e AUTH_SERVER_URL = https: //dicom.archive: 8843 / auth \

Now everything works inside the network.

How to connect to the server from outside the network? What ports do I need to forward on the router? And do I need to change the settings in keycloak?

Sorry, but I'm really a teapot :) :) :)

To unsubscribe from this group and stop receiving emails from it, send an email to dcm4che+u...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/dcm4che/3fd42386-b676-4497-ab13-e11d852c1000%40googlegroups.com.

[Alexandr Kuznetsov]

Forwarding ports 8443 and 8843 on the router gives nothing. After switching to port 8843, the message Invalid parameter: redirect_uri
Please explain to me how to access the server from outside the local network. For example: the server address is 192.168.78.21, the external address of the router is 192.168.168.88.243. On the router, ports 8443 and 8843 are forwarded to the address 192.168.78.21.
Port 11112 is also forwarded. On this port I can send studies from outside the local network, as well as watch other viewers using the C-Get protocol.
I think the problem is in the wrong keycloak setup.
Please help

вторник, 24 марта 2020 г., 10:53:52 UTC+2 пользователь gunterze написал:

For access via public network I recommend to prefer https://dicom.archive:8443/dcm4chee-arc/ui2 over http://dicom.archive:8080/dcm4chee-arc/ui2 for accessing the UI. So you have to forward port 8443 and 8843 at your public access point to the docker host, and take care that host name "dicom.archive" get resolved to the IP of your access point by web browsers on external hosts - e.g. by a correspondent entry in their host file.

Sent with ProtonMail Secure Email.

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐

To view this discussion on the web visit https://groups.google.com/d/msgid/dcm4che/3fd42386-b676-4497-ab13-e11d852c1000%40googlegroups.com.

[Gunter Zeilinger]

You have to add https://<docker-host>:8443/dcm4chee-arc/ui2/* as Valid Redirect URI and https://<docker-host>:8443  as Web Origin in the Keycloak Client Settings tab

s.

https://github.com/dcm4che/dcm4chee-arc-light/wiki/Run-secured-archive-services-on-a-single-host#register-the-archive-ui-as-oidc-client-in-keycloak

Sent with ProtonMail Secure Email.

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐

On Tuesday, March 24, 2020 7:44 PM, Alexandr Kuznetsov <alexandr.v...@gmail.com> wrote:

Forwarding ports 8443 and 8843 on the router gives nothing. After switching to port 8843, the message Invalid parameter: redirect_uri

Please explain to me how to access the server from outside the local network. For example: the server address is 192.168.78.21, the external address of the router is 192.168.168.88.243. On the router, ports 8443 and 8843 are forwarded to the address 192.168.78.2.

To unsubscribe from this group and stop receiving emails from it, send an email to dcm4che+u...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/dcm4che/01563272-bdac-482d-890a-985f9f99f3d0%40googlegroups.com.