Hi all,
this issue has been discussed before. If running behind a firewall, access to the external resources times out after a long delay, blocking access to the interface on startup. This can be avoided by disabling access to external https ressources completely with setting the flag
CRYOSPARC_DISABLE_EXTERNAL_REQUESTS=true
in config.sh.
But of course I’d like to get this up and running. Usually we do not have problems in our system, but access to https/http requires the proxy to be configured.
Which environment variable is used by cryosparc to look up a proxy? I did not find this in the documentation.
Thanks for help.
Cheers,
Eckhard
Has a proxy URL been provided to you by your IT support?
Yep, same for http and https, and set for all variables (http_proxy, https_proxy, HTTP_PROXY, HTTPS_PROXY) in the bash environment of the cryosparc instance user. Seems not to be used, though…
Would be good to know, where cryosparc looks for the information to use a proxy.
Cheers,
Eckhard
External resources for the App’s landing page’s info panels cannot currently be accessed via a proxy that is defined by environment variables. We made a note of the issue. Thanks @eckhardhofmann for bringing it to our attention.
Are you able to run jobs on this CryoSPARC instance?
Jep, everything works fine regarding job submission. We just had this enoying timeout at first startup of the interface (up to a minute or even a little more, felt like ages), after that everything works fine. Switching off the access with CRYOSPARC_DISABLE_EXTERNAL_REQUESTS=true solves the problem completely.
Seems that the licence checking luckily is not affected by the proxy issue, at least not in our environment.
I would suggest to add a specific configuration variable like CRYOSPARC_HTTPS_PROXY=myproxy.mydomain.mycountry:80 to supply both proxy and port.
That way you would be independent of any environment setting, which varies sometimes between distributions and local installation procedures.
Thanks for your great support!!!
Eckhard