Better support systems running with a proxy

[johan-bjareholt]

Should we add a config option for proxy or should we ignore the systems default proxy?

https://github.com/ActivityWatch/activitywatch/issues/266

[Mishco]

Hello, I agree that should be there some ignore option. I have similar issue with proxy. On personal computer works fine. On company computer (proxy and no_proxy setup in ENV variables) In logs:

• For aw-server

* Running on http://127.0.0.1:5600/ (Press CTRL+C to quit)  (werkzeug:122)

• For aw-watcher-afk

[WARNING]: 403 Client Error: Forbidden for url: http://127.0.0.1:5600/api/0/buckets/aw-watcher-afk_PC  (aw_client.client:28)
[WARNING]: Not connected to server, 49 requests in queue  (aw_client.client:380)
[WARNING]: 403 Client Error: Forbidden for url: http://127.0.0.1:5600/api/0/buckets/aw-watcher-afk_PC  (aw_client.client:28)

• For aw-watcher-window

[INFO ]: aw-watcher-window started  (aw_watcher_window.main:40)
[WARNING]: 403 Client Error: Forbidden for url: http://127.0.0.1:5600/api/0/buckets/aw-watcher-window_PC  (aw_client.client:28)
[WARNING]: Not connected to server, 132 requests in queue  (aw_client.client:380)
[WARNING]: 403 Client Error: Forbidden for url: http://127.0.0.1:5600/api/0/buckets/aw-watcher-window_PC  (aw_client.client:28)
[WARNING]: Not connected to server, 134 requests in queue  (aw_client.client:380)
[WARNING]: 403 Client Error: Forbidden for url: http://127.0.0.1:5600/api/0/buckets/aw-watcher-window_PC  

[ErikBjare]

@Mishco Looks like your set no_proxy doesn't have any effect, but it should. What is it set to?

[Mishco]

Hi @ErikBjare. In NO_PROXY I have: localhost, .company.com, some-othercompany.com. Should I add there 127.0.0.1 ?

[Mishco]

I try to add 127.0.0.1 into NO_PROXY and it helps. Maybe it can be added into gettings-started docs. Thanks

[ErikBjare]

@Mishco Nice. I improved the notice about it in the getting started guide: https://github.com/ActivityWatch/docs/commit/033321ddaf3948ed250b11080128a5e17fdda448