Common issues

"An error occurred while opening the remote file! Error in the server communication"

This one is a problem on our side! The server hosting the images at NASA can be a bit flaky. A future version will use data from multiple servers, so the problem should be solved for good. Until then, you can manually switch to a different server. This can be done by editing "resources/settings/defaults.properties" and changing the following lines:

API.jp2series.path=http\://helioviewer.ias.u-psud.fr/helioviewer/api/index.php
API.dataSources.path=http\://helioviewer.ias.u-psud.fr/helioviewer/api/?action\=getDataSources&verbose\=true
default.remote.path=jpip\://helioviewer.ias.u-psud.fr\:8080
API.event.path=http\://helioviewer.ias.u-psud.fr/helioviewer/api/
default.httpRemote.path=http\://helioviewer.ias.u-psud.fr/helioviewer/jp2/	
API.jp2images.path=http\://helioviewer.ias.u-psud.fr/helioviewer/api/index.php

"intel_do_flush_locked failed: No such file or directory."

This is a known bug in the Intel GPU Linux driver. You can try this workaround (Thanks to Brian Swan for the suggestion):

export LIBGL_ALWAYS_SOFTWARE=1
export LIBGL_DRI3_DISABLE=1

java.net.SocketTimeoutException: Read timed out

java.io.IOException: Invalid status code returned (500) Internal Server Error

These problems often occur when using the newest 3.0 version. It's something that we have to fix on our end. You can follow our progress here: https://github.com/Helioviewer-Project/api/issues/11