a year ago
W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/noble/InRelease Could not connect to archive.ubuntu.com:80 (185.125.190.83). - connect (111: Connection refused) Cannot initiate the connection to archive.ubuntu.com:80 (2620:2d:4000:1::16). - connect (101: Network is unreachable) Could not connect to archive.ubuntu.com:80 (185.125.190.81). - connect (111: Connection refused) Cannot initiate the connection to archive.ubuntu.com:80 (2620:2d:4000:1::103). - connect (101: Network is unreachable) Could not connect to archive.ubuntu.com:80 (185.125.190.36). - connect (111: Connection refused) Cannot initiate the connection to archive.ubuntu.com:80 (2620:2d:4000:1::102). - connect (101: Network is unreachable) Could not connect to archive.ubuntu.com:80 (185.125.190.39). - connect (111: Connection refused) Cannot initiate the connection to archive.ubuntu.com:80 (2620:2d:4000:1::19). - connect (101: Network is unreachable) Could not connect to archive.ubuntu.com:80 (185.125.190.82). - connect (111: Connection refused) Cannot initiate the connection to archive.ubuntu.com:80 (2620:2d:4000:1::101). - connect (101: Network is unreachable)
Seems to be an issue with reaching out for packages (EU West)
6a6c4123-f4c9-4c41-ba5f-c3115ddc1753
9 Replies
a year ago
having the same issue: https://station.railway.com/questions/consistently-unable-to-apt-install-and-c-af41c2a4
a year ago
out of curiosity which packages were you trying to install? Seems like both myself and the other person having the issue were trying to install chromium (in that help thread) @gazhay
jms6520
I'm also having the issue, and I am not installing chromium.
a year ago
good to know it's not just chromium, seems like they're now looking into it (in thread I linked above)
a year ago
I'm just deploying a fairly standard node service, no custom build scripts, so nothing I am specifically requesting.
a year ago
Hello,
We have determined that this is indeed an issue with Ubuntu's Archive; unfortunately, it would be out of our control.
a year ago
From the discord chat :
It seems they are actively blocking railway. I understand this is a block at the ubuntu.com end of things, but I am just deploying the standard node service, so I think this will affect a number of users, and leaves me unable to patch our live site because I will hit this failure during any deploy. The only solution I can think of is to migrate away from railway?
I tried activating the static ip option, but I still get the 403 forbidden from the 185.x.x.x address and not the static ip
Ok, switching to railpack allowed the build to go through.
I guess that is the solution for anyone that can switch to railpack (I wasn't sure, but it seems to be ok on first check)
gazhay
From the discord chat : **It seems they are actively blocking railway. I understand this is a block at the** [**ubuntu.com**](http://ubuntu.com) **end of things, but I am just deploying the standard node service, so I think this will affect a number of users, and leaves me unable to patch our live site because I will hit this failure during any deploy. The only solution I can think of is to migrate away from railway?** **I tried activating the static ip option, but I still get the 403 forbidden from the 185.x.x.x address and not the static ip** **Ok, switching to railpack allowed the build to go through.** **I guess that is the solution for anyone that can switch to railpack (I wasn't sure, but it seems to be ok on first check)**
a year ago
Thanks ! Moving to railpack worked for me too.