...
ecFlowUI is now behaving (in terms of client/server communication) as if it were running on the SOCKS host (hpc-login in this case) and you should be able to interact with all the ecFlow servers available from that host.
...
Local file access via proxychains (only in version >= 5.9.0)
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 is running 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 edit the network settings in Tools→ Configure->Network:
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:
These settings must match the proxy jump and SOCKS host settings you used in your dynamic port forwarding command. With this ecFlowUI will behave exactly as if it were running on the SOCKS host as far as client/server communication and log file access is concerned.
Comments
- when running ecFlowUI via
proxychainslocal 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)):
...