Franz: Proxy Service Seems Hit and Miss on 5.0.0-beta.20

[KyleAtDND]

Proxy Service Mostly Not Working
I'm using Proxy servers from PrivateVPN and having very mixed results, but mostly not working. I'll describe my various experiences below. I'm using DNS addresses instead of IP addresses and trying ports 1080 and 8080, so that the Proxy Host/IP looks like: "is-rey.privatevpn.com:8080." The User field is my PrivateVPN username and the password my PrivateVPN password.

To Reproduce
Turn on Proxy to individual services, and fill out information. Results are below:

WhatsApp

• None of the servers and/or ports work. Doesn't give a network error in the console, just this:
  Uncaught (in promise) TypeError: console.err is not a function at /Users/USERNAME/Library/Application Support/Franz/recipes/whatsapp/webview.js:16 at Generator.next (<anonymous>) at step (/Users/MG/Library/Application Support/Franz/recipes/whatsapp/webview.js:3) at /Users/USERNAME/Library/Application Support/Franz/recipes/whatsapp/webview.js:3 at new Promise (<anonymous>) at /Users/USERNAME/Library/Application Support/Franz/recipes/whatsapp/webview.js:3 at Object.<anonymous> (/Users/USERNAME/Library/Application Support/Franz/recipes/whatsapp/webview.js:18) at Object.<anonymous> (/Users/USERNAME/Library/Application Support/Franz/recipes/whatsapp/webview.js:42) at Module._compile (module.js:642) at Object.Module._extensions..js (module.js:653)

Telegram

• The HTTP (8080) port seems to work, but SOCKS (1080) seems to not. On 1080, most http requests seem to work but XHR requests to Telegram fail, as these:
  Application Cache Error event: Manifest fetch failed (6) https://web.telegram.org/webogram.appcache GET https://t.me/_websync_?authed=0 net::ERR_EMPTY_RESPONSE GET https://telegram.me/_websync_?authed=0 net::ERR_EMPTY_RESPONSE POST https://venus.web.telegram.org/apiw1 net::ERR_EMPTY_RESPONSE

Slack

• Empty network log and empty console

Screenshots
When it fails, the Franz screen is just black (I'm in Dark mode): http://cloud.designanddevelop.io/14d657fd263d

Desktop (please complete the following information):

• OS: 10.14.1 (18B75)
• Browser Chrome
• Version 70.0.3538.110

[adlk]

Thanks for the report. I'll check with PrivateVPN and update this issue as soon as I have more information.

[KyleAtDND]

Awesome, and thanks for the great work! I know these routing issues with proxies and such are extremely annoying.

[KyleAtDND]

@adlk Thanks for the update. It's definitely better. However, I'm still not able to load Slack or Facebook Messenger screenshot of proxy with port 1080 loading and screenshot of 8080 loading. This continues to occur after completely restarting Franz.

I haven't confirmed this, but it appears that the proxy on my Telegram service isn't working anymore. I have it set to use a server in Iceland. Previously, Telegram would pull up the Iceland country code, but not it pulls up the one in the United States. I'm thinking this is because it's seeing a US IP, but I don't know how to confirm it. I am using SOCKS5 Proxy on Port 1080. Either way, it won't let me log-in. It freezes on "Generating keys" with both 1080 and 8080.

[KyleAtDND]

Update: it seems to be fairly inconsistent. After I restarted my entire computer Slack started working on Port 1080, but after I entered my credentials, it gives me "Error: ERR_EMPTY_RESPONSE". Then I switched it to Port 8080 and it worked. I tried to switch it back to 1080 (SOCKS5), and I continue to get the error: ERR_EMPTY_RESPONSE. However, when it was on port 8080, I was able to confirm that it was going through the proxy (access logs for slack showed iceland IP).

Facebook Messenger always gives ERR_EMPTY_RESPONSE, no matter the port.

[KyleAtDND]

@adlk Couple of lasts things, hope these are helpful ;)

Here is a screenshot of the logs for Telegram. For some reason, I've found the Iceland server for PrivateVPN to be the most reliable as I've been testing this. So if you want to emulate what I'm doing, you can test it with:
Server: is-rey.privatevpn.com
Port: 8080

Also, sometimes the error message functioning acts a little weird. It will overlay on the screen like this. You can see it says "Oh no! Telegram has failed to load. Error." It occasionally does that on other services. It seems it should grey out the screen so that the error message has more prominence.

[KyleAtDND]

@adlk I just upgraded to 5.0.0-beta.23 and it seems none of the proxies are working now. They just sit there with a loading screen like this: http://cloud.designanddevelop.io/c3060012c196.

[KyleAtDND]

@adlk I've updated to 5.0.1-beta.1 and seem to be having the same problems.