-
Notifications
You must be signed in to change notification settings - Fork 56
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Currency fetching doesn't respect proxies #63
Comments
It does use a proxy if one is set. UNIX-y tools and languages automatically use proxies specified by Have you configured Alfred to "Use macOS http proxy settings for scripts" in Alfred Preferences > Advanced? Note: that only works if you've configured static proxies in System Preferences > Network (i.e. you're using "Web Proxy (HTTP)" and "Secure Web Proxy (HTTPS)". If you're using auto discovery/configuration, it won't work. |
Proxies are set in System Prefs. Export proxies is set in Alfred. If I type "conv 10 usd" I get two results: "fetching currencies" and "set APP_KEY". APP_KEY is set in the workflow variables to my key on openexchangerates.org. |
Yeah, I think that's an unrelated bug. It should still fetch the rates. Check the log file (enter |
Well, two things.
It really is set in the workflow variables. Looks like the proxy isn't reaching the update checker too.
|
Yes. I told you: it's an unrelated bug. That message is triggered by there being no exchange rates available, not by As you can see from my log, it's showing the same "error" but fetching the exchange rates all the same:
And like I also told you, Python automatically uses the proxy if it's properly configured, so you need to double-check your setup because that's where the problem is. Open the echo "http_proxy=$http_proxy" >&2
echo "https_proxy=$https_proxy" >&2 Then check what's in Alfred's debugger when you run the workflow. I'll fix the incorrect "APP_KEY is not set" error, but that isn't actually stopping the workflow downloading exchange rates. |
I'm still pretty sure it's a problem with your setup. Uncheck "Automatic Proxy Configuration" and try again. |
No change (and that would be a bug in Alfred, as I'm only setting http/https proxies for applications too dumb to use the PAC). |
Try restarting Alfred. It might not have picked up the changes.
Alfred can't use PAC. |
Still no change.
Or more accurately, typical shell scripts can't use PAC. I understand how PAC and friends works. |
Then I don't know what the problem is. It works correctly on my machine. If "Web Proxy" and/or "Secure Web Proxy" are set, Alfred also sets them in the workflow environment, and the workflow also uses them. It looks like Alfred isn't finding the settings, so I suggest you go over your setup again. Make sure you're setting them on the right interface, pressing "Apply" etc. If that doesn't work, you'll have to set the variables yourself on any workflows that need them. At any rate, it's not an issue with the workflow, and there's nothing I can do about it.
Exactly. |
@rossburton Could you update to v3.7.1? I think your issue might be fixed. |
Sorry, I've left the job with the evil proxy of doom. |
My work laptop has a tight VPN so to access the real internet a proxy needs to be used. However the currency script doesn't appear to use the proxies, so never actually fetches the data.
The text was updated successfully, but these errors were encountered: