search

nextgenhealthcare / connect

The swiss army knife of healthcare integration.
Other
868 stars 265 forks source link

{BUG} Error Downloading / Verifying Codebase #5929

Closed knappl-mmri closed 9 months ago

knappl-mmri commented 9 months ago

Describe the bug Receive "Error downloading/verifying codebase" (unable to retrieve payload from HTTP request...). when attempting to launch a Mirth connection after re-opening launcher

To Reproduce

  1. Open launcher, check box to close launcher window.
  2. Launch a Mirth connection.
  3. Open the launcher
  4. attempt to launch another Mirth connection
  5. error, "Error downloading/verifying codebase" (unable to retrieve payload from HTTP request...).

Expected behavior Mirth connection should open without error

Actual behavior "error downloading/verifying codebase" (unable to retrieve payload from HTTP request...).

Screenshots image

Environment (please complete the following information):

Workaround(s) Not that I know of

Additional context

jonbartels commented 9 months ago

The interesting part of your stack trace is the "unknown address" and "cached address" line.

I am doing some Googling but that sounds like maybe the cache is invalid or the address somehow changed between launches? See "Inet Address Caching" at https://docs.oracle.com/javase/8/docs/api/java/net/InetAddress.html

Can you copy and paste the text of the stack trace and post it here using code formatting please?

When the issue happens can you use a browser, curl, or wget to fetch https://interface:8443/ ? Do other HTTP clients fail too?

You might try https://github.com/kayyagari/ballista as a workaround. It is an open-source alternative to the launcher. If this is a genuine DNS or networking issue the client won't matter.

knappl-mmri commented 9 months ago

Thank you for your time! I was working with NextGen Success Community and this error was supposed to go there. I don't know if this can be deleted, but it can certainly be closed. I couldn't access with a browser and realized there was a typo :( Your comments were a big help!