Bug 235588 - portsnap fetch failed no mirrors
Summary: portsnap fetch failed no mirrors
Status: In Progress
Alias: None
Product: Services
Classification: Unclassified
Component: Portsnap (show other bugs)
Version: unspecified
Hardware: i386 Any
: --- Affects Only Me
Assignee: Colin Percival
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-02-07 22:17 UTC by Emir
Modified: 2020-10-27 15:40 UTC (History)
5 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Emir 2019-02-07 22:17:49 UTC
hello I have a problem with the portsnap fetch command I see that there are no mirrors and when I try to access the page portsnap.freebsd.org
portsnap1.freebsd.org
portsnap2.freebsd.org
portsnap3.freebsd.org
portsnap4.freebsd.org
portsnap5.freebsd.org
portsnap6.freebsd.org
etcetera I get a message that says 403 Forbidden
nginx / 1.14.0
Comment 1 Walter Schwarzenfeld freebsd_triage 2019-02-07 22:29:49 UTC
I think it is better to try to discuss this problem in freebsd-forum:

 https://forums.freebsd.org/forums/installation-and-maintenance-of-ports-or-packages.5/
Comment 2 VVD 2019-07-03 01:40:38 UTC
403 again on all portsnap mirrors.
Comment 3 Li-Wen Hsu freebsd_committer 2020-10-27 12:33:23 UTC
This should have been improved after using AWS.
Comment 4 Colin Percival freebsd_committer 2020-10-27 15:40:12 UTC
Portsnap mirrors returning 403 for /index.html fetches is normal.  Portsnap doesn't fetch that file.

What's the actual error you were getting from portsnap?