Re: [webmin-l] re: upgrade

[Joe C. <jo...@sw...>]

Cory wrote:
> What happens is when I try to upgrade, I have gotten two error 
> messages.  1 it would just time out when trying to connect.  The other 
> was it would say that it cant downgrade the version.. that is when I try 
> to go from 1.210 to 1.240.  I ended up just downloading the tar file and 
> upgraded I through the console but I cant get the two updates that are 
> out there. 
> 
>  
> 
> When I click on update it looks like it is downloading cause in the 
> bottom left corner it starts to show how many bytes but then it just 
> goes to zero and nothing happens I let it sit there for an hour with no 
> progress

No...that progress meter is your client-side browser and only shows 
what's happening between you and the Webmin server.  You're not 
downloading anything more than the progress page from Webmin to your own 
client machine--you're triggering a download on your Webmin server. 
Webmin has its own progress indicator, and if you don't see it begin 
downloading and reporting the percentages in the browser window the 
download is not starting at all and that is the source of your trouble. 
  It is possibly a firewall, as Vernon mentioned, or just as likely DNS 
trouble--you can find out by trying a download from the command line 
using wget, just as Vernon and I pointed out in the last couple of 
messages...try it, please, and get back to us with the result.  This is 
not a bug in Webmin that anyone else is seeing, nor is it a problem on 
the download servers, so repeatedly telling us "it doesn't work" isn't 
going to do any good.  The problem is on your machine, and we're trying 
to help you solve it.  Help us help you, or we'll never get anywhere.

What happens when you run:

wget 
http://internap.dl.sourceforge.net/sourceforge/webadmin/webmin-1.240.tar.gz

(All on one line.)

If it works (I'll be surprised) then the problem is somewhere in Webmin 
and we'll need to look a bit deeper.  But I'm betting you'll either get 
a host not found error indicating that your DNS is improperly 
configured, or it will just hang for a while and eventually time out 
indicating either a too-strict firewall or routing trouble.  In either 
case, we'll know where to start working on the problem.