Update Message on Administrators Main Page - Error

I am receiving this error on the main page after I login.

The remote file http://updates.bugzilla.org/bugzilla-update.xml cannot be downloaded (reason: 500 Can't connect to updates.bugzilla.org:80 (No such host is known. )).
Either the remote server is temporarily unavailable, or your web server cannot access the web. If you are behind a proxy, set the proxy_url parameter correctly


When I click the link to go to that site I get the following info:

This XML file does not appear to have any style information associated with it. The document tree is shown below.
<bugzilla>
<branch id="2.20" status="closed" vid="2.20.7" url="https://www.bugzilla.org/releases/2.20.7/" date="2008-11-06"/>
<branch id="2.22" status="closed" vid="2.22.7" url="https://www.bugzilla.org/releases/2.22.7/" date="2009-02-02"/>
<branch id="3.0" status="closed" vid="3.0.11" url="https://www.bugzilla.org/releases/3.0.11/" date="2010-01-31"/>
<branch id="3.2" status="closed" vid="3.2.10" url="https://www.bugzilla.org/releases/3.2.10/" date="2011-01-24"/>
<branch id="3.4" status="closed" vid="3.4.14" url="https://www.bugzilla.org/releases/3.4.14/" date="2012-01-31"/>
<branch id="3.6" status="closed" vid="3.6.13" url="https://www.bugzilla.org/releases/3.6.13/" date="2013-02-19"/>
<branch id="4.0" status="closed" vid="4.0.18" url="https://www.bugzilla.org/releases/4.0.18/" date="2015-04-15"/>
<branch id="4.2" status="closed" vid="4.2.16" url="https://www.bugzilla.org/releases/4.2.16/" date="2015-12-22"/>
<branch id="4.4" status="old-stable" vid="4.4.13" url="https://www.bugzilla.org/releases/4.4.13/" date="2018-02-16"/>
<branch id="5.0" status="stable" vid="5.0.6" url="https://www.bugzilla.org/releases/5.0.6/" date="2019-02-09"/>
</bugzilla>

What is the problem?
0
eko
12/31/2020 2:47:50 AM
mozilla.support.bugzilla 10182 articles. 0 followers. Post Follow

3 Replies
21 Views

Similar Articles

[PageSpeed] 23

* eko...--- via support-bugzilla [30/12/2020 18:47] :
>
> The remote file http://updates.bugzilla.org/bugzilla-update.xml cannot be downloaded (reason: 500 Can't connect to updates.bugzilla.org:80 (No such host is known. )).
> Either the remote server is temporarily unavailable, or your web server cannot access the web. If you are behind a proxy, set the proxy_url parameter correctly
> 

Your server is unable to resolve the hostname updates.bugzilla.org which
prevents it from downloading the xml file that informs it there are new
versions of Bugzilla.

You can change the 'upgrade_notification' parameter if you don't want
this file to be downloaded.

Emmanuel
0
Emmanuel
12/31/2020 9:15:37 AM
I dont believe that to be the case.  I am on the server and able to resolve the hostname fine and see the xml file.  I was looking at the IIS logs and procmon and no where do I see the request being made to get to that server.

Is there a specific module that does this?  Can anyone provide any more information on this?

I believe that the problem may be somewhere  with IIS because our old install was Apache and that worked.  It could also be with strawberry if there are any perl calls.

Thanks.
0
eko
12/31/2020 3:38:57 PM
Guten Tag eko...--- via support-bugzilla,
am Donnerstag, 31. Dezember 2020 um 16:38 schrieben Sie:

> I dont believe that to be the case.  I am on the server and able to
> resolve the hostname fine and see the xml file.  I was looking at
> the IIS logs and procmon and no where do I see the request being made to =
get to that server.

Not seeing anything in ProcMon might be expected if RESOLVING the host
fails already. I don't think that is reflected in whatever ProcMon is
able to monitor. The only events which might make sense are settings
regarding resolving host names or files like [...]\etc\hosts. But all
of that might simply be heavily cached and therefore not recognized by
ProcMon.

> Is there a specific module that does this?  Can anyone provide any more i=
nformation on this?

Bugzilla\Update.pm, especially look at "_synchronize_data". Looking at
the code, it seems that a proxy is ALWAYS considered, so check yur
IIS-environment for any proxy-related settings. Those would take
affect when running Bugzilla.

>  # If the URL of the proxy is given, use it, else get this information
>  # from the environment variable.
>  my $proxy_url =3D Bugzilla->params->{'proxy_url'};
>  if ($proxy_url) {
>    $ua->proxy(['http', 'https'], $proxy_url);
>  }
>  else {
>    $ua->env_proxy;
>  }

https://metacpan.org/pod/LWP::UserAgent#env_proxy

> I believe that the problem may be somewhere  with IIS because our
> old install was Apache and that worked.[...]

The workes running Bugzilla in IIS might be firewalled or something
like that as well.

Mit freundlichen Gr=FC=DFen,

Thorsten Sch=F6ning

--=20
Thorsten Sch=F6ning
AM-SoFT IT-Service - Bitstore Hameln GmbH

E-Mail:  Thorsten.Schoening@AM-SoFT.de
Web:     http://www.AM-SoFT.de/

Telefon: 05151-  9468-55
Fax:     05151-  9468-88
Mobil:    0178-8 9468-04

Firmensitz: Bitstore IT-Consulting, Frankfurter Allee 285, 10317 Berlin
Steuernummer 037/230/30566, HR 27198, Amtsgericht Potsdam Gesch=E4ftsf=FChr=
er Janine Galonska

0
windows
12/31/2020 3:56:19 PM
Reply: