Change Port 8080 to another port when using the docker implementation

21 views
Skip to first unread message

gerald thomas

unread,
Dec 5, 2019, 7:01:32 AM12/5/19
to OpenHIE Implementers Network (OHIN)
Dear All,
I am trying to build installing openHIM on docker but i have other instances running on port 8080. I change the port to 5000 and now i can't login to my openHIM. Please can someone help.

Ryan Crichton

unread,
Dec 9, 2019, 9:39:22 AM12/9/19
to gerald thomas, OpenHIE Implementers Network (OHIN)
Hi,

Did you change the port in the docker config? You will probably also need to change to port in the OpenHIM console configuration so that it knows what the new port it. Also, port 5000 is already used in the OpenHIM for routing so you may need to use a port other than 5000 as well.

Cheers,
Ryan

On Thu, Dec 5, 2019 at 2:01 PM gerald thomas <geral...@gmail.com> wrote:
Dear All,
I am trying to build installing openHIM on docker but i have other instances running on port 8080. I change the port to 5000 and now i can't login to my openHIM. Please can someone help.

--
You received this message because you are subscribed to the Google Groups "OpenHIE Implementers Network (OHIN)" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ohie-implement...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ohie-implementers/9293614f-3eef-4d83-82d0-3cea74331897%40googlegroups.com.


--
Ryan Crichton 
Lead Developer and Technical Architect 
ry...@jembi.org 
Skype: ryan.graham.crichton 

Jembi Health Systems | Durban 
www.jembi.org

This e-mail contains proprietary and confidential information some or all of which may be legally privileged. It is for the intended recipient only. If an addressing or transmission error has misdirected this e-mail, please notify the author by replying to this e-mail and then deleting same. If you are not the intended recipient you must not use, disclose, distribute, copy, print or rely on this e-mail. Jembi Health Systems NPO, its subsidiaries and associated companies is not liable for the security of information sent by e-mail and accepts no liability of whatsoever nature for any loss, damage or expense resulting, directly or indirectly, from the access of this e-mail or any attachments hereto.

Reply all
Reply to author
Forward
0 new messages