librewolf/winupdater
librewolf/winupdater
Watch
5
0
Fork
You've already forked winupdater
 0
Code Issues 2 Pull requests Releases 50 Activity Actions

Winupdater behind a proxy #39

New issue
Open
opened 2025-04-02 18:47:15 +00:00 by WilliW · 4 comments
WilliW commented 2025-04-02 18:47:15 +00:00 (Migrated from codeberg.org)
Copy link

For those users, who work with LibreWolf behind a proxy (with a valid non-default proxy configuration in the browser settings and a default proxy configuration in the Windows control panel - the browser should know the way to the proxy, but not the Windows OS):
It would be great, if the execution of Winupdater would lead to an update of LibreWolf in such an environment.

For those users, who work with LibreWolf behind a proxy (with a valid non-default proxy configuration in the browser settings and a default proxy configuration in the Windows control panel - the browser should know the way to the proxy, but not the Windows OS): It would be great, if the execution of Winupdater would lead to an update of LibreWolf in such an environment.
ltguillaume commented 2025-04-02 18:54:59 +00:00 (Migrated from codeberg.org)
Copy link

Sorry, WinUpdater is a separate program and it uses Windows API calls to check for and download updates. It won't read the browser's proxy settings.

Sorry, WinUpdater is a separate program and it uses Windows API calls to check for and download updates. It won't read the browser's proxy settings.
WilliW commented 2025-04-03 05:43:20 +00:00 (Migrated from codeberg.org)
Copy link

Ok, I understand.
Is or will there a way to override the operation system's proxy configuration for WinUpdater either via

  1. the environment, by setting an environment variable e.g. HTTP_PROXY=host:ip
    or
  2. a command line argument when calling WinUpdater, e.g. --proxy-server=host:ip
    ?

It would be great, if such a configuration would finally lead to an update of LibreWolf.

Ok, I understand. Is or will there a way to override the operation system's proxy configuration for WinUpdater either via 1) the environment, by setting an environment variable e.g. HTTP_PROXY=host:ip or 2) a command line argument when calling WinUpdater, e.g. --proxy-server=host:ip ? It would be great, if such a configuration would finally lead to an update of LibreWolf.
konfiot commented 2026-08-07 15:59:05 +00:00 (Migrated from codeberg.org)
Copy link

I'm running librewolf on a computer with a corporate proxy (with Auth using the windows creds), and winupdater is not working (Error Could not connect to https://codeberg.org.)
I can confirm that codeberg.org is not filtered by the proxy
All other windows programs seems to pick up the correct proxy configuration from the windows settings

I'm running librewolf on a computer with a corporate proxy (with Auth using the windows creds), and winupdater is not working (Error Could not connect to https://codeberg.org.) I can confirm that codeberg.org is not filtered by the proxy All other windows programs seems to pick up the correct proxy configuration from the windows settings
ltguillaume commented 2026-08-07 22:11:04 +00:00 (Migrated from codeberg.org)
Copy link

That's odd, because I explicitly made the changes to accommodate for those very proxy settings since #32 with 90f9ea09ae.

  • Windows version?
  • WinUpdater version?
That's odd, because I explicitly made the changes to accommodate for those very proxy settings since #32 with 90f9ea09ae99b0aeed68f090f5f2e963cf3b0546. - Windows version? - WinUpdater version?
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
binmod
1.18.2
1.18.1
1.18.0
1.16.0
1.15.2
1.15.1
1.15.0
1.14.5
1.14.4
1.14.3
1.14.2
1.14.1
1.14.0
1.12.4
1.12.3
1.12.2
1.12.1
1.12.0
1.11.1
1.11.0
1.10.0
1.9.1
1.9.0
1.8.6
1.8.4
1.8.3
1.8.2
1.7.11
1.7.10
1.7.9
1.7.8
1.7.7
1.7.6
1.7.5
1.7.4
1.7.3
1.7.2
1.7.1
1.7.0
1.6.4
1.6.3
1.6.2
1.6.1
1.6.0
1.5.1
1.5.0
1.4.5
1.4.3
1.4.2
1.4.1
1.4.0
1.3.4
1.3.3
1.3.2
1.3.0
1.3.1
1.2.7
1.2.6
1.2.5
1.2.3
1.2.2
1.2.1
1.2.0
1.1.2
1.1.1
1.1.0
1.0.0
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
librewolf/winupdater#39
No description provided.