Jump to content

Search the Community

Showing results for tags 'proxy'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Alfred 3
  • Make the Most of Alfred
    • Discussion & Help
    • Bug Reports
    • Alfred Feature Suggestions
    • Themes
  • Alfred Workflows
    • Share your Workflows
    • Workflow Help & Questions
    • Workflow Advanced Tips & Tricks
    • Workflow Automation Tasks
  • Alfred Themes
  • Alfred Remote for iOS
    • Alfred Remote Discussion & Help
    • Remote Connection Troubleshooting


  • Articles
    • Forum Integration
    • Frontpage
  • Pages
  • Miscellaneous
    • Databases
    • Templates
    • Media


  • New Features
  • Other

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start




Website URL




Found 10 results

  1. https_proxy url is wrong but i set correctly. my shell script is curl "https://media4.giphy.com/media/xc8HEtzrBTcCA/giphy-preview.gif" -v --output "/Users/qhe/Library/Caches/com.runningwithcrayons.Alfred/Workflow Data/cn.alanhe.giphy/xc8HEtzrBTcCA_preview.gif" If I execute directly at the terminal it is works.
  2. Version of OS X: 10.12.3 (16D32) Version/build of Alfred: v3.3/801 Expected behavior: When checking for updates, be able to connect to remote update server for updates. Actual behavior: Unable to contact update server. Unable to load changelog. Reproduce: 1. Be behind proxy 2. Set `$http_proxy`, `$https_proxy`, `$HTTP_PROXY`, `$HTTPS_PROXY` in environment. 3. Check for updates... Optional: toggle use macOS proxy in network in Alfred -> advanced settings. Try step 3 again. I'd love some guidance on this. FWIW, this worked before upgrading to Sierra. P.S., great tool! Very helpful. Thanks for sharing! Cheers, erip
  3. At my company, all web traffic has to go out through a proxy. This causes all sorts of issues that we have to figure out when apps are inconsistent about how they detect proxy settings. For Alfred, I haven't been able to figure out what to whitelist for updates. I get notifications that an update is available, but when I go to the settings to actually download it, I see the error "Unable to contact update server". Is there any way to find out what exactly Alfred is using (curl, wget, something else) and/or where it is going so I can whitelist this?
  4. it seems workflow support neither pac file nor https , even not allow me to set a port of a host file. i hope i can use the auto proxy by a pac file which is configged by system network setting.
  5. Hi, A lot of workflows are not working when being used behind a proxy. After some debugging it seems that you are just passing the proxy value from the system preferences, alas this will not work with a lot of languages and programs as the correct format for the http_proxy and https_proxy environment variables includes the protocol like so: http_proxy=http://username:password@proxy:port https_proxy=http://username:password@proxy:port And for the system proxy to work, only an ip or a hostname can be specified. I don't know of any way that you can obtain the correct protocol prefix from the system. Prefixing with http:// should work in most(but not all) cases as most proxies are run on a non secure port. If you can't find a way to get the prefix from the system, then you have to connect to the proxy and detect it there. -- Best regards, David Jack Wange Olrik <david@olrik.dk> http://david.olrik.dk GnuPG fingerprint 4171 FCB3 EE86 6A03 B436 5AED 5F41 087D 7AB1 A4B5 ["The first rule of Perl club is You do not talk about Perl club"] Using v2.5.1 (308)
  6. As things stand, workflows that require web access are basically just going to break on a machine that can only access the web via a proxy server. Alfred should set the http_proxy environmental variable before calling any workflow. Currently, it is not only necessary for every workflow to be "proxy aware" if it wants to work on all machines, but it is also extremely difficult to determine the proxy server from a script, as it depends on the current network profile and Apple's command line utilities don't provide a straightforward way to get the proxy address. By setting the http_proxy environmental variable before running a workflow's script, Alfred could make using the proxy entirely transparent to Ruby/Python workflow authors (both languages' standard network libraries will automatically use the proxy specified in http_proxy, as will curl), and much easier to use for workflows written in other languages (they can grab the environmental variable rather than trying to coax the same information out of OS X themselves). Essentially, workflow authors shouldn't need to have to worry about network settings, as far as that can be avoided, not least of all because it represents something that currently needs to be implemented separately in every single workflow that needs web access.
  7. Recently, I need to bring my MBP to office. But when I use Alfred2 I found the all the workflows can't work. The office network need to set http(s) or sock proxy. I've alread set the http and https proxy. But, everything is Ok in my home network. Thanks for all your help.
  8. Hi folks, I often find myself in an usecure wifi network. I don't want to go though the hassle of building a VPN server and I don't like hotspot shield. I ssh tunnel to my server and set socks proxy. it's a hassle so I figured many others may like this workflow too. however, I have a tiny issue. my scripts ask for user's password too many times. if only they could set password in workflow or change script to include the password. It's a shell script. Get it here PS: is there any way to ask user to configure this workflow after installing? like setting their ssh user and server?
  9. All script based workflows are unable to run if you live behind a http proxy. For bash, perl, python etc. all depend upon a couple of environment variables in order to work behind a web proxy. The variables are HTTP_PROXY, HTTPS_PROXY and sometimes also their lowercase variants http_proxy and https_proxy. Most unix commands also use these environment variables so it would be super sweet if Alfred could set these variables before executing the workflow. You can find the correct variables by calling 'networksetup' on the command line. Here is a small perl script that calls networksetup in order to find the values for the environment variables: https://gist.github.com/davidolrik/6699572 Or you can just call: scutil --proxy To get the current proxy config. -- Best regards, David Jack Wange Olrik
  10. I need some help here. Its very frustrating that all the nifty workflows dont work when using proxies. I have narrowed down the problem to curl command used in workflows.php which I think is the one that issues requests to remote locations. I tested out the following command curl --proxy www.proxy.server:proxy_port_number -I https://twitter.com which worked. I am not really familiar with php or python or curl commands/options, so can anyone tell me what changes I should do to the workflows.php file for it to work? Also how do I make sure curl does not use the proxy when I'm at home using regular internet. Also as a feature request, can alfred discover and apply proxy settings automatically the way chrome/firefox do?
  • Create New...