Greetings,
I'd first like to say you've done a very nice job on the 2.0 update and it seems to work quite well so far.
Unfortunately, I can't use it so I'll have to roll back to v1.9 for the time being.
Having the program connect automatically to your soundfont server without my authority or control contravenes a number of well established internet security practices. While I can understand a want or need to monetize your efforts and time in maintaining Polyphone, it really should be up to the end user to determine whether or not he or she wishes to connect to a remote server in this fashion.
My suggestion: Make connecting to your soundfont server disabled until the end user decides to turn it on or return to the way it was done via a web interface in v1.9.
I understand this could be a wish for a couple of people but this is a need for the Polyphone website. I am forced to keep this direction so that I can provide Polyphone for free, I guess this is a good deal.
If Polyphone cannot access the network this is not a problem since it will result in a "timeout" and Polyphone will of course work. This is also not a big CPU overload.