I have particular circumstances that require apps to be installed as an admin user.īut when running Signal as a normal user the app still tries to access the admin user's home directory and fails (as gleaned from the logfile). However, I found a completely different reason for the failure (and a nasty workaround): Unfortunately, even starting px before running Signal still fails. Just launch it and you can use as a proxy for Signal (and others) right away. And the best thing: it does not require any configuration as it uses the current user's session.
#Connect to proxy for pc download
The solution to this was to simply download px: a HTTP proxy that automatically authenticates you against NTLM proxies. Turns out, they had changed the configuration and are requiring NTLM authentication now (as opposed to HTTP Basic authentication). It simply starts a cmd session (the first window that flashes past), runs a command line that first sets the HTTPS_PROXY variable (so it will only be available in that session) and second launches Signal, which then has access to the HTTPS_PROXY I had a similar problem some time ago: I was unable to supply credentials to my company's proxy as I used to all the years before. Signal should start with proxy configured, and you will probably also note another window quickly flash first. Save the file (for example on your desktop) and test by double-clicking.
![connect to proxy for pc connect to proxy for pc](https://img-16.ccm2.net/uacxcp0PmgctXXNaNnTZCWXDh84=/325x/e018458a9c694a85972bca76b6275160/ccm-faq/EhVJBCmcme1bXc4HkRrP1yhfjzTr-lax1-s-.png)
Modify paths so it corresponds to your system. īasically, create a file named startSignal.bat (or something equally suitable, the important part is the file extension) and put this oneliner in it:Ĭ:\Windows\System32\cmd.exe /c "set HTTPS_PROXY=pac+ & start C:\Users\youruser\AppData\Local\Programs\signal-desktop\Signal.exe" I have another solution, which I believe should work even if you are not able to edit environment variables through the control panel - but I haven't tested it with that limitation so your mileage may vary. I am neither a developer nor an admin, but I hope anyone can look into this. This fallback could be triggered if all other means of trying to connect fail and the command above yields a non-zero value. Signal could then try to connect using the proxy settings described in the PAC file. (Get-ItemProperty -Path 'hkcu:\Software\Microsoft\Windows\CurrentVersion\Internet Settings' -Name AutoConfigURL).AutoConfigURL This can be done using a powershell command like this:
#Connect to proxy for pc windows
So one solution could be a fallback rule for Signal Desktop to extract the PAC files URL from the Windows registry.
![connect to proxy for pc connect to proxy for pc](https://i.ytimg.com/vi/DOBXQyYzJWo/maxresdefault.jpg)
However, I needed local admin rights on my machine to do this and it's not feasable for the normal user. I could solve the issue by creating a new environmental variable HTTPS_PROXY like described by jnasm. manually set the URL in Window's internet settings to load the PAC file.set a group policy for client computers to use WPAD to discover the PAC file OR.
![connect to proxy for pc connect to proxy for pc](https://www.perfect-privacy.com/images/manuals/windows_7_httpproxy/windows_7_httpproxy_en_img1.jpg)