APT repository broken

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Somewhere else…

Describe the Bug

Your APT repository for Ubuntu is broken

Err:12 https://downloads.cursor.com/aptrepo stable InRelease                                                                        
  403  Forbidden [IP: 104.18.16.128 443]

E: Failed to fetch https://downloads.cursor.com/aptrepo/dists/stable/InRelease  403  Forbidden [IP: 104.18.16.128 443]
E: The repository 'https://downloads.cursor.com/aptrepo stable InRelease' is no longer signed.

Steps to Reproduce

sudo apt update

Operating System

Linux

Version Information

not relevant

Does this stop you from using Cursor

Yes - Cursor is unusable

14 Likes
Https://downloads.cursor.com/aptrepo stable InRelease 403 Forbidden [IP: 104.18.16.128 443]
Apt repo unavialable
3

Hey, thanks for the report. The IP 104.18.16.128 is Cloudflare, so a 403 can happen for a few different reasons. A couple questions to narrow it down:

  1. Are you using a VPN or a corporate network or proxy?
  2. What region are you in?
  3. Did this APT repo work fine before?

As a temporary workaround, you can download the .deb directly from the downloads page and install it with sudo dpkg -i.

I’ll pass this to the team. We know about issues with the Linux APT repo, but 403 Forbidden specifically is a new symptom. Let me know the answers to the questions above.

4
  1. no difference if VPN or home internet, doesn’t work on any VPN location I tested
  2. Europe
  3. yes, apt repo worked yesterday

yes, I know I can install from file directly, but doesn’t fit into automated workflows

1 Like
5

Seeing the same:

Err:7 https://downloads.cursor.com/aptrepo stable InRelease403  Forbidden [IP: 104.18.16.128 443]
  1. same network as always (no changes)
  2. LV
  3. Also worked yesterday
1 Like
6

I am facing this too.

  1. No VPN
  2. Pakistan
  3. Worked yesterday
1 Like
9

Hey get the exact same issue with the Fedora repo

Status code: 403 for https://downloads.cursor.com/yumrepo/cursor-2.4.31.el8.x86_64.rpm (IP: 104.18.17.128)

Status code: 403 for https://downloads.cursor.com/yumrepo/repodata/repomd.xml (IP: 104.18.17.128)

10

Same here.

  1. Company LAN
  2. South Korea
  3. Worked yesterday
11

Same.

Local ISP

Cyprus

Works yesterday

12

Yep same.

  1. Local ISP
  2. Netherlands
  3. Worked yesterday
13

Additional context - after executing apt update it points out that Cursor repo is no longer signed
E: The repository ‘https://downloads.cursor.com/aptrepo stable InRelease’ is no longer signed.

14
  1. Local ISP, no VPN
  2. Romania
  3. worked yesterday
E: Failed to fetch https://downloads.cursor.com/aptrepo/dists/stable/InRelease  403  Forbidden [IP: xxxxxxxxxxxxxx]

E: The repository 'https://downloads.cursor.com/aptrepo stable InRelease' is no longer signed.
15

https://downloads.cursor.com/keys/anysphere.asc also 403

16

Same here.

Brazil

17

Same issue with me too.
Local ISP
No vpn
India
Worked earlier

18

Local ISP
No vpn
france
E: Failed to fetch https://downloads.cursor.com/aptrepo/dists/stable/InRelease 403 Forbidden [IP: 2606:4700::6812:1180 443]
E: The repository ‘https://downloads.cursor.com/aptrepo stable InRelease’ is not signed.

19

Same for RPM repo

20

+1

Even the key download is a 403:

$ curl -fsSL https://downloads.cursor.com/keys/anysphere.asc 
curl: (22) The requested URL returned error: 403
21

Same for me:

Err:15 https://downloads.cursor.com/aptrepo stable InRelease
403  Forbidden \[IP: 104.18.16.128 443\]
Reading package lists… Done
E: Failed to fetch https://downloads.cursor.com/aptrepo/dists/stable/InRelease  403  Forbidden \[IP: 104.18.16.128 443\]
E: The repository ‘https://downloads.cursor.com/aptrepo stable InRelease’ is no longer signed.
N: Updating from such a repository can’t be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
  1. No VPN
  2. I’m in Egypt → North Africa
  3. And yes it was working fine up until today
22

Can confirm the same issue - location: United Kingdom

23

Same here, Europe (France), with and without a VPN, same connection as always but broken since today.