WhitewaterFoundry / Pengwin

A Linux distro optimized for WSL based on Debian.
Other
1.48k stars 105 forks source link

apt upgrade behind corporate firewall #489

Closed ryn1x closed 5 years ago

ryn1x commented 5 years ago

I am behind a corporate firewall with self signed certs and cannot get apt upgrade with the Pengwin repos to work:

Preconfiguring packages ...
Setting up pengwin-base (0.1-221) ...
Symlinking /etc/dpkg/origins/pengwin to default
Installing Whitewater Foundry GPG keys...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:--  0:00:41 --:--:--     0curl: (7) Failed to connect to packagecloud.io port 443: Con
nection refused
dpkg: error processing package pengwin-base (--configure):
 installed pengwin-base package post-installation script subprocess returned error exit status 2
Errors were encountered while processing:
 pengwin-base
E: Sub-process /usr/bin/dpkg returned an error code (1)
crramirez commented 5 years ago

Hello,

First, try to go to https://packagecloud.io/ in your browser and try to solve it.

Regards

ryn1x commented 5 years ago

I can get to https://packagecloud.io/ just fine. I can also curl https://packagecloud.io/ from Pengwin.

sirredbeard commented 5 years ago

The offending code is here. Can you copy and paste lines 49-54 into your terminal and share the results? Thank you.

sirredbeard commented 5 years ago

Closing to due to no response.

ryn1x commented 5 years ago

Sorry. I honestly just ended up installing Linux on bare metal. Too many headaches with WSL for my specific use cases.

sirredbeard commented 5 years ago

Maybe WSL2 will address those issues? It is still in Fast Ring and not recommended for production, but perhaps you could revisit it in a few months or try it in Gnome Boxes?

KiranMohan commented 3 years ago

I was facing this issue on WSL2. But adding the corporate proxy to /root/.curlrc solved the issue for me.

proxy = <proxy_host>:<proxy_port>

crramirez commented 3 years ago

Thanks for sharing