RHN Configuration registration problem.
We have an internet connexion by an HTTP proxy. This systeme work fine with
Netscape, Helix Gnome updater, etc..
In the update-config, there is no reference to an HTTP Proxy, but in the
/etc/sysconfig/rhn/up2date there is a value for proxy that I have modified
to reflate our configuration:
pkgProxy=http://192.168.98.254:8080 and enableProxy=1
But there is no success.
Have an idea ?
Can you please try specifying your serverURL in /etc/sysconfig/rhn/up2date as:
And let me know if that works?
I'm having the same problem. I tried your fix for the serverURL line and got the
following error when I try to register:
"There was a fatal error communicating with the server. The message was: Proxy
denies fulfilling the request."
I tried this with the enableProxy variable set to both 0 and 1. Same response.
tested your proposition with no success when launched up2date or rhn_register.
i precise that it works with helix-update. Why not use the same code, it's GPL.
When attempt to browse with netscape this URL:
where 192.168.98.254:8080 is our proxy (netscape proxy server)
I have got the same error that i have with up2date:
Proxy denies fulfilling the request
The proxy's access control configuration denies access to the requested object
through this proxy.
any help will be appreciate.
we have 60 redhat workstation that i hope we could register to the redhat
network one day, and in fact use the up2date package.
a new version of update agent will be released this week with proxy support
*** Bug 19317 has been marked as a duplicate of this bug. ***
let there be light,
there was light
which good news
i know no information is better than misinformation
but a such silence is connected as Micro$oft
one week last, nothing on updates.redhat.com & redhat-watchlist.
Is there any new problem with the so much waited up2date with http proxy
My RHN Register report
Numerous bugfixes and enhancements have been made to Update Agent since the
release of Red Hat Linux 7.0. While not a required upgrade, it is suggested.
But cannot download it.
Verification refer to python-xmlrpc-1.2-1.i386.rpm
So do we wait python-xmlrpc-1.2 release in stable tree or apply rawhide
12/12/2000 python-xmlrpc, up2date-2.1.6-1
tested new RPM from rawhide (12-12-2000)
with no success
this is the message i have with invocate
up2date in console mode
There was a fatal error communicating with the server. The message was:
good proxy URL in /etc/sysconfig/rhn/up2date
rawhide doesn't have any new rhn_register RPM
so RedHat Network registering other than web access isn't possible.
up2date appears to work but is very slow in comparaison of a connexion whithout
so there remains the problem of rhn_register which could not negociate a
connexion by HTTP proxy.
the new version of up2date is being officially released today and includes proxy
support. A new version of rhn_register is also being made available, and it
includes proxy support.
is up2date currently being modified to accept HTTP proxy with user/pass access ?
What to do when the proxy is configured with a user and password
Where can I add that to the proxy setting
Now I got the error message: unable to set up CONNECTION tunnel
my 7.2 attempts to use a proxy and issues the error message:
A protocol error occured: Proxy Error , attempt #1
A protocol error occured: Proxy Error , attempt #2
A protocol error occured: Proxy Error , attempt #3
A protocol error occured: Proxy Error , attempt #4
A protocol error occured: Proxy Error , attempt #5
even though i have not enabled the proxy config
We've been experiencing similar problems running up2date from behind a
firewall. We had all the correct proxy information in the up2date configuration
file, but we kept getting the following error 5 times when we ran rhn_register
from the command line: "A socket error occurred: Unable to set up CONNECTION
tunnel" -- and, you can't run the up2date app without registering with RedHat.
(what it seems at least...)
We viewed the rhn_register file and saw that there were manual proxy parameters
that could be run. This did the trick for us. We are now able to run up2date
Do "rhn_register --help" (without quotes) from the command line for complete
details. Hope this helps others experiencing the same problem.
NOTE: Forgot to mention that this is for version RH Linux 7.3 for the above