Railgun for Ubuntu 18?

I’m interested in trying Railgun but as I see here Ubuntu 18 isn’t supported:

When will it be available?

There is no APT repository available:

Err:2 http://pkg.Cloudflare.com bionic Release
404 Not Found [IP: 2606:4700::6813:c497 80]

I’m trying with the 16.04 one, there are some warnings during the installation, like:

update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults


Any update for support on ubuntu 18.04 servers?
It’s not listed in the requirements

Ok, so I’m not the only one struggling with this. I can’t use Railgun because my servers all run Ubuntu 18.04. Has anybody opened a support ticket on this?

Yup, I actually contacted them right after posting and was able to get an update pretty quick
Response is below

"Our support article has the most updated versions listed. I am afraid that at the moment we do not support installing Railgun in Ubuntu 18.04 (Bionic).

As we are working on a “revamp” of Railgun, I am afraid there is no ETA on when this will be available.

I would recommend you to check back with us later in a few months.

Please let us know if you have any other questions.



Hi there,

Has anyone received any updates on this?

Magic 8-Ball says “Outlook not so good.”

I really think they’re heading toward using Argo Tunnel to replace Railgun. Maybe that’s what they meant by “revamp.”

1 Like

Now we need also for Ubuntu 20… it seems this service is being abandoned
Also I had problems with high amount of traffic, if I remember well with ports exhaustion… at the end I downgraded from business since it had no use to me

huh https://pkg.cloudflare.com/#ubuntu-title ?

Supported Versions

  • Focal (20.04)
  • Bionic (18.04)
  • Xenial (16.04)
  • Wily (15.10)
  • Vivid (15.04)
  • Utopic (14.10)
  • Trusty (14.04)
  • Precise (12.04)

I think that’s for the entire repository itself.

I don’t think they are really supporting or maintaining the Railgun package anymore. I brought a bug to their attention recently and worked with them for almost two weeks to prove the bug was with their package, and they were finally able to reproduce the issue. But at that point they decided it was a “non-issue” and that they have no intention of fixing it… Sucks for a service that costs $200 /month for most users. I think the assumption that this is being phased out is correct unfortunately.