Recently when starting FluentTerminal while my VPN is on, FT will come up but stuck in blinking courser screen, and won't load powershell or any other. but when I force to close it and try again without VPN, terminal comes up successfully and ready for use. even trying for going to setting page or even trying to close the terminal with closing icon, will Endup to crash.

My guess is that it's unable to complete the check for a new version. This
process should probably be non-blocking.
I don't think so! because I remember I saw the update notification last time opened this with VPN. I even checked Recourse Monitor > Network > Network Activity, and I looked for IP address when FT comes up, and I saw lb-140-82-118-6-ams.github.com and trying this with a browser was useless.

I don't know! maybe it is new version checking problem!
Can't work with OpenVPN either. I can see the notification 'Update available'. The version is the latest in chocolatey: 0.5.1.0.
When I canceled the proxy setting in IE's Internet Option, FluentTerminal worked. I think as an offline app, it should work in any network environment.
Agreed. This should be a non-blocking event.
If you see the update notification the version check already succeeded (which is also done in the SystemTray process, not the App itself) The problem here is more probably the WebSocket communication between the App and the WebView. The VPN must interfere with it in some way
so @felixse, how can I solve this problem? VPN is just the normal windows PTPP connection. I even try to listen to HTTP request going out from pc with Wireshark, but when I launch Wireshark and then launch the FT, same happens! with closing Wireshark, and launching FT again, it works normally!
I also encountered this problem, when I open the global proxy for shadowsocksr, I can't open a new window.
I also encountered this problem, when I open the global proxy for shadowsocksr, I can't open a new window.
Before the author (may) fix this, I'm just wondering, in which case do you need it to be Global
I add an exclude ip address list to my proxy config. Add "local*;127.0.0.1" works for me. like this

I also encountered this problem.
as @pangjian said, by excluding 127.0.0.1 so it won't throw the VPN the problem temporary solved. first, get your getaway with ipconfig command, then execute this: route add 127.0.0.1 <getaway ip>.
Thanks for sharing your solution @pangjian
There is not much we can do here right now, but I haved linked this discussion to our FAQ
Most helpful comment
I add an exclude ip address list to my proxy config. Add "local*;127.0.0.1" works for me. like this