Interactive jobs do not load micrographs (institution firewall blocking requests)

Hello everybody,

I have installed cryosparc in a workstation and calculated the CTF without any problem using motion corrected movies however, when I try to curate exposures or pick micrographs (interactive jobs) the job does not shows the images and get stucked:

log webapp:

[sbgrid@c105627 ~]$ cryosparcm log webapp

Table">\n \n <td class=“contentData”>\n Could not connect to the destination in time.
\n
\n The remote site may be down or the site may be producing errors.\n \n \n\n\n\n\n<table class=“infoTable”>\n \n <td class=“infoData”>\n URL: <script type=“text/javascript”>break_line(“http://c105627.dhcp.swmed.org:46626/get_micrographs”);
\n Status code: <script type=“text/javascript”>break_line(“502”);
\n Transaction time: <script type=“text/javascript”>break_line(“5 milliseconds”);
\n \n \n\n\n\n\n\n\n\n \n \n \n \n \n \n

\n For assistance, please contact the IR Service Desk at 214-648-7600.\n
\n generated <span id=“time”>2021-07-01 21:16:38 by McAfee Web Gateway [129.112.115.42/m-proxy3] \n
\n \n
\n URL Host Matches in List Global Host Whitelist\n
\n Client IP [129.112.52.206]\n
\n\n\n \n \n \n\n\n"
at new StatusCodeError (/home/sbgrid/cryosparc/cryosparc_master/cryosparc_webapp/bundle/programs/server/npm/node_modules/request-promise-core/lib/errors.js:32:15)
at Request.plumbing.callback (/home/sbgrid/cryosparc/cryosparc_master/cryosparc_webapp/bundle/programs/server/npm/node_modules/request-promise-core/lib/plumbing.js:104:33)
at Request.RP$callback [as _callback] (/home/sbgrid/cryosparc/cryosparc_master/cryosparc_webapp/bundle/programs/server/npm/node_modules/request-promise-core/lib/plumbing.js:46:31)
at Request.self.callback (/home/sbgrid/cryosparc/cryosparc_master/cryosparc_webapp/bundle/programs/server/npm/node_modules/request/request.js:185:22)
at emitTwo (events.js:126:13)
at Request.emit (events.js:214:7)
at Request. (/home/sbgrid/cryosparc/cryosparc_master/cryosparc_webapp/bundle/programs/server/npm/node_modules/request/request.js:1161:10)
at emitOne (events.js:116:13)
at Request.emit (events.js:211:7)
at IncomingMessage. (/home/sbgrid/cryosparc/cryosparc_master/cryosparc_webapp/bundle/programs/server/npm/node_modules/request/request.js:1083:12)
at Object.onceWrapper (events.js:313:30)
at emitNone (events.js:111:20)
at IncomingMessage.emit (events.js:208:7)
at endReadableNT (_stream_readable.js:1055:12)
at _combinedTickCallback (internal/process/next_tick.js:138:11)
at process._tickDomainCallback (internal/process/next_tick.js:218:9)
=> awaited here:
at Function.Promise.await (/home/sbgrid/cryosparc/cryosparc_master/cryosparc_webapp/bundle/programs/server/npm/node_modules/meteor/promise/node_modules/meteor-promise/promise_server.js:56:12)
at Promise.asyncApply (imports/api/Interactive/server/methods.js:30:15)
at /home/sbgrid/cryosparc/cryosparc_master/cryosparc_webapp/bundle/programs/server/npm/node_modules/meteor/promise/node_modules/meteor-promise/fiber_pool.js:43:40

This is the job output:

License is valid.

Running job on master node

[CPU: 67.8 MB] Project P2 Job J6 Started

[CPU: 67.9 MB] Master running v3.2.0, worker running v3.2.0

[CPU: 68.1 MB] Running on lane default

[CPU: 68.1 MB] Resources allocated:

[CPU: 68.1 MB] Worker: c105627.dhcp.swmed.org

[CPU: 68.1 MB] --------------------------------------------------------------

[CPU: 68.1 MB] Importing job module for job type manual_picker…

[CPU: 214.8 MB] Job ready to run

[CPU: 214.8 MB] ***************************************************************

[CPU: 214.8 MB] Interactive job running on port 53432

[CPU: 215.2 MB] Loaded info for 100 micrographs

Outputs

micrographs

exposureCount: 0

particles

particleCount: 0

Any ideas to fix this issue?

Thanks in advance

Best
Victor

Hi @Vruiz,

Thanks for your post. From the error message, it looks like the interactive job data is being blocked by ‘McAfee Web Gateway’ - unfortunately cryoSPARC needs to be able to request data from the interactive port for the job to function properly.

Typically this is not an issue since the web application makes requests to and from the same machine, just a different port. Perhaps a system administrator could allow outbound requests from port 39000 (the web application)?

- Suhail