Request firewall hole for importds to connect to SourceForge Mercurial servers on port 8000

Asked by Max Bowsher

Dear LOSAs,

It seems that SourceForge run their anonymous Mercurial service as HTTP on port 8000. It would seem that the importds currently cannot access this, so I guess it's firewalled?

Please could you consider opening a firewall hole for this traffic so that SourceForge Mercurial code imports can work.

SourceForge use per-project hostnames for the Mercurial service, e.g., so it is difficult to say that a certain set of IP addresses will be sufficient always. However, for a few projects I tested, these all seem to resolve to plain "" at, so a single whitelisted IP would most likely be enough for the short term.

Question information

English Edit question
Launchpad itself Edit question
[LEGACY] Canonical WebOps Edit question
Last query:
Last reply:
Revision history for this message
Stefan Stasik (stefan-stasik) said :


Would it be possible for you to use/setup a HTTP Proxy for this? That way, we don't have to setup special firewall rules, and you can maintain the remote IP-address/hostname if it ever does change?

Let me know if you have any problems with this.

Regards, Stefan

Revision history for this message
Robert Collins (lifeless) said :

Uhm, we shouldn't depend on an external proxy for talking to major hosting sites (like sf, google code, savannah etf)

Revision history for this message
Robert Collins (lifeless) said :

Ok, the rt actually talks about using our in-dc proxy. This needs to be forked into two issues I think:
 - firewall hole for now (immediate rectification)
 - examine using proxies on the code import machines (longer term)

Can you help with this problem?

Provide an answer of your own, or ask Max Bowsher for more information if necessary.

To post a message you must log in.