If you run this release with run-tor.sh, it makes direct connections to tcp6 peers, doesn't go through Tor?



nxt.useWebSockets=false is a temporary fix.



Quote

oh and the ssl connection to api server is now broken.



SSL received a record that exceeded the maximum permissible length. (Error code: ssl_error_rx_record_too_long)



Does it help if you add -Djava.net.preferIPv4Stack=true to the java command line in run-tor.sh? Or is it that websockets using IPv4 also ignore the socks proxy setting?It is now possible to use both SSL and non-SSL for the API server, see the documentation in nxt-default.properties:# Port for http/json API requests.nxt.apiServerPort=7876# Port for https/json API request. If same as nxt.apiServerPort, the nxt.apiSSL setting# determines whether SSL is used or not.nxt.apiServerSSLPort=7876# Enable SSL for the API server (also need to set nxt.keyStorePath and nxt.keyStorePassword).# Non-SSL connections will be disabled if nxt.apiServerSSLPort is equal to nxt.apiServerPort.# Otherwise, both SSL and non-SSL connections will be accepted.nxt.apiSSL=falseIf you have nxt.apiSSL=true and changed nxt.apiServerPort to a different port, the nxt.apiServerSSLPort remains set to the default 7876, so you have ssl on 7876 and non-ssl on your custom port. Set both nxt.apiServerSSLPort and nxt.apiServerPort to your custom port if you want only that port enabled, and with SSL.