Skip to content
Connection through authenticating proxy fails after saving proxy credentials
Got a problem with Viscosity or need help? Ask here!
- Posts: 6
- Joined: Thu Jul 01, 2021 4:46 pm
I've got an authenticating HTTP proxy at work (plain login/password). I connect to TCP OVPN server.
Problem: if I enter proxy credentials in Viscosity manually, I can connect fine. If I save them to keychain, proxy server breaks connection. In log I get this:
Problem: if I enter proxy credentials in Viscosity manually, I can connect fine. If I save them to keychain, proxy server breaks connection. In log I get this:
Code: Select all
...
2021-07-01 10:04:48: TCP/UDP: Preserving recently used remote address: [AF_INET]10.1.250.250:8080
2021-07-01 10:04:48: Attempting to establish TCP connection with [AF_INET]10.1.250.250:8080 [nonblock]
2021-07-01 10:04:49: TCP connection established with [AF_INET]10.1.250.250:8080
2021-07-01 10:04:49: SIGUSR1[soft,init_instance] received, process restarting
...
Hi AlexFullmoon,
If you view the saved username and password using the Keychain Access application, are they both saved correctly? You should be able to find the correct Keychain item in Keychain Access by searching for the address of your proxy server.
https://support.apple.com/en-au/guide/k ... ca1083/mac
Cheers,
James
If you view the saved username and password using the Keychain Access application, are they both saved correctly? You should be able to find the correct Keychain item in Keychain Access by searching for the address of your proxy server.
https://support.apple.com/en-au/guide/k ... ca1083/mac
Cheers,
James
Web: https://www.sparklabs.com
Support: https://www.sparklabs.com/support
Twitter: https://twitter.com/sparklabs
Support: https://www.sparklabs.com/support
Twitter: https://twitter.com/sparklabs
- Posts: 6
- Joined: Thu Jul 01, 2021 4:46 pm
Yes, credentials in keychain are correct. I tried with two different sets of proxy credentials with same results.
Also, OVPN server credentials are also saved in keychain, but they work fine.
(maybe nonsense, but it's as if Viscosity sends saved credentials too quick for the proxy to respond or something?)
Also, OVPN server credentials are also saved in keychain, but they work fine.
(maybe nonsense, but it's as if Viscosity sends saved credentials too quick for the proxy to respond or something?)
Hi AlexFullmoon,
We haven't been able to replicate any issues in Viscosity with some quick test proxy servers, but that's not to say there couldn't be any. What type of proxy are you using (HTTP or SOCKS)? What type of authentication are you using (Automatic, Basic, or NTLM)? Does your password have any special characters in it (i.e. non letter or number characters)?
Cheers,
James
We haven't been able to replicate any issues in Viscosity with some quick test proxy servers, but that's not to say there couldn't be any. What type of proxy are you using (HTTP or SOCKS)? What type of authentication are you using (Automatic, Basic, or NTLM)? Does your password have any special characters in it (i.e. non letter or number characters)?
maybe nonsense, but it's as if Viscosity sends saved credentials too quick for the proxy to respond or something?The authentication details are sent along with the proxy connection request itself, so the timing shouldn't affect it.
Cheers,
James
Web: https://www.sparklabs.com
Support: https://www.sparklabs.com/support
Twitter: https://twitter.com/sparklabs
Support: https://www.sparklabs.com/support
Twitter: https://twitter.com/sparklabs
- Posts: 6
- Joined: Thu Jul 01, 2021 4:46 pm
Proxy is HTTP with basic authentication (squid 3.5.23). One set of credentials is literally test:12345678, another contains a couple of # in password.
Hmm. Turns out, automatic authentication also works, the problem still exists, and it gives different line in the log:
Hmm. Turns out, automatic authentication also works, the problem still exists, and it gives different line in the log:
Code: Select all
It also shows notification window with „OpenVPN check error please reconnect“ (Ошибка проверки OpenVPN. Пожалуйста, переподключитесь еще раз.)...
2021-07-09 11:47:24: Attempting to establish TCP connection with [AF_INET]10.1.250.250:8080 [nonblock]
2021-07-09 11:47:26: TCP connection established with [AF_INET]10.1.250.250:8080
2021-07-09 11:47:26: Note: previous 'HTTP Proxy' credentials failed
...
Thanks for the additional information.
We've identified a situation that could result in the Keychain data being fetched incorrectly - it shouldn't affect most proxy setups but it's likely what you're running into. This should now be fixed in the latest beta version of Viscosity: please give it a try and let us know if you still encounter any issues.
https://www.sparklabs.com/support/kb/ar ... -versions/
Cheers,
James
We've identified a situation that could result in the Keychain data being fetched incorrectly - it shouldn't affect most proxy setups but it's likely what you're running into. This should now be fixed in the latest beta version of Viscosity: please give it a try and let us know if you still encounter any issues.
https://www.sparklabs.com/support/kb/ar ... -versions/
Cheers,
James
Web: https://www.sparklabs.com
Support: https://www.sparklabs.com/support
Twitter: https://twitter.com/sparklabs
Support: https://www.sparklabs.com/support
Twitter: https://twitter.com/sparklabs
- Posts: 6
- Joined: Thu Jul 01, 2021 4:46 pm
Sat Jul 10, 2021 2:55 pmJames wrote: We've identified a situation that could result in the Keychain data being fetched incorrectly - it shouldn't affect most proxy setups but it's likely what you're running into. This should now be fixed in the latest beta version of Viscosity: please give it a try and let us know if you still encounter any issues.Problem fixed, thanks for quick solution.
https://www.sparklabs.com/support/kb/ar ... -versions/
- Posts: 6
- Joined: Thu Jul 01, 2021 4:46 pm
Note — now I sometimes get disconnected with
1.9.4b1 (1572)
Code: Select all
This might be proxy glitching (I had disconnects before) but it seems to be more frequent today, and I don't recall this lin the log in stable version.2021-07-12 14:15:13: Assertion failed at proxy.c:250 (strlen(p->up.username) > 0)
2021-07-12 14:15:13: Mon Jul 12 14:15:13 2021 Exiting due to fatal error
2021-07-12 14:15:13: State changed to Отключено (Process Terminated)
1.9.4b1 (1572)
- Posts: 6
- Joined: Thu Jul 01, 2021 4:46 pm
Mon Jul 12, 2021 9:22 pmAlexFullmoon wrote: Note — now I sometimes get disconnected withSorry, disregard that, same happens on 1.9.3, so in must be proxy being particularly glitchy today.Code: Select allThis might be proxy glitching (I had disconnects before) but it seems to be more frequent today, and I don't recall this lin the log in stable version.2021-07-12 14:15:13: Assertion failed at proxy.c:250 (strlen(p->up.username) > 0) 2021-07-12 14:15:13: Mon Jul 12 14:15:13 2021 Exiting due to fatal error 2021-07-12 14:15:13: State changed to Отключено (Process Terminated)
1.9.4b1 (1572)
9 posts
Page 1 of 1