Page History

...

ecFlowUI accesses certain local files (e.g. output and server logs in the Output, Timeline and Server Load panels) directly (standard file I/O) without using the ecFlow client-server communication. This poses a limitation if we run it via proxychains because these files are only local on the remote hosts so ecFlowUI cannot access them. To overcome this difficulty you need to use ecFlowUI version >= 5.9.0 and file fetching will automatically work for you. The only settings that you might need to change is the SOCKS port number, which by default is assumed to be 9050.  Should you set up dynamic port forwarding and use proxychains with a different port number you need to set it in Tools→ Configure→Network:

System server lists via proxychains (only in version >= 5.9.0)

When using ecflowUI outside ECMWF the system server lists are not automatically accessible and you need to configure them manually. However, when it is done they will automatically transferred from the remote SOCKS host and loaded on each start-up. To define the system server lists probably the best option is to set Preferences > Server > System server list. The paths specified here have to be local paths on the remote SOCKS host.  

Image Added

Alternatively, you can use the ECFLOW_SYSTEM_SERVERS_LIST environment variable to specify the very same paths. See more details about the system server lists (here, LINK TO BE ADDED)

Comments

• when running ecFlowUI via proxychains local ecFlow servers are inaccessible.
• the dynamic port forwarding sometimes stops/hangs and as a result ecFlowUI loses connection to the servers (it is indicated by the orange strip on the left and the dotted background (TODO: this should be improved because it is barely visible on a Mac)):

...