Skip to content

Title: License error: ConnectionError persists even after updating to latest version and re-applying Academic license #2095

@zy137849833

Description

@zy137849833

Checklist before submitting the issue:

  • [√] The issue is strongly related to the MiXCR software
  • [√] The issue can be reproduced with the most recent version of MiXCR
  • [√] There is no answer to the question in the official documentation and there is no duplicate issue in the bug tracker
  • Inspection of raw alignments with exportAlignmentsPretty shows that data has the expected architecture, and sample preparation artefacts are not the reason of the problem (if this is the matter of the issue)

Expected Result

MiXCR should start normally and recognize the valid Academic license (mi.license) without attempting to connect to the license server.

Actual Result

MiXCR fails with the following error even after:

  • Updating to the latest version from GitHub
  • Re-applying for a new Academic license
  • Replacing the mi.license file
  • The license file location has not changed (it worked before)

Exact MiXCR commands

#bash
/work/*/mixcr -V
# or
/work/*/mixcr align \
    --species HomoSapiens \
    --force-overwrite \
    input.fa \
    output.vdjca

MiXCR report files

Screen output: License error: ConnectionError
No report files (license check fails before any analysis starts)

Additional Information

DNS diagnosis:

$ curl -v https://cloud.milaboratory.com
* Could not resolve host: cloud.milaboratory.com

$ curl -v https://licensing.milaboratory.com
* Could not resolve host: licensing.milaboratory.com

nslookup returns NXDOMAIN for both domains.
The cluster can access GitHub normally (wget works), but cannot resolve Milaboratory license domains. Setting RES_OPTIONS with public DNS (8.8.8.8, 1.1.1.1) does not help — the internal DNS appears to be enforced.
We would like to run MiXCR completely offline on this cluster. Could you please advise on the best way to achieve this with an Academic license?

Thank you very much for your help!
Best regards,
Yang

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions