Replies: 1 comment 1 reply
-
There shouldn't be anything preventing that. Have you attempted standard troubleshooting steps by attempting the connection outside of Mirth? Using tools such as telnet? netcat? Are you sure Mirth had stopped and restarted during the upgrade process? |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi,
For a customer of ours I have upgraded Mirth Connect from 3.5.1 to 3.12. One channel has a TCP Sender destination that worked fine in 3.5.1, but which fails to connect in 3.12: the Test Connection button gives a message "Could not connect to host: ..."
I upgraded by closely following the official upgrade guide: https://github.com/nextgenhealthcare/connect/wiki/Upgrading. What I did not do, however, was upgrade Java. This is version 1.8.0_191. Perhaps this is relevant.
What can I do to obtain a working connection? Thanks!
Beta Was this translation helpful? Give feedback.
All reactions