CUPS asking for https access

[Rakhesh Sasidharan]

> Hi there!
>
> I'm running Fedora Core 6. Installed CUPS. Default config, didn't make
> any changes except change things to allow access from my local
> network.
>
> Then I try to access the CUPS server through my browser at
> "http://192.168.17.13:631/". That works fine too. I get the page and
> all. After that, I click on one of the links on top (viz. "Add
> Printer") and I get a message thus:
>
> "426 Upgrade Required
>
> You must access this page using the URL
> https://myhostname.fqdn:631/admin?OP=add-printer."
>
> After that nothing happens. The browser just keeps trying to connect
> ... that's all. Going back to the main page and then clicking any of
> the links has no effect ... it just keeps trying to connect. (That's
> ok, I am guessing the browser is trying to redirect to the https link
> and hence getting stuck). Going to the https link directly too has no
> effect.
>
> Here's the entries from "/var/log/cups/error_log" after doing a
> restart of cupsd and trying again:
>
> I [08/Feb/2007:16:32:24 +0400] Allowing up to 100 client connections per host.
> I [08/Feb/2007:16:32:24 +0400] Using policy "default" as the default!
> I [08/Feb/2007:16:32:24 +0400] Full reload is required.
> I [08/Feb/2007:16:32:24 +0400] Loaded MIME database from '/etc/cups':
> 34 types, 38 filters...
> I [08/Feb/2007:16:32:24 +0400] Loading job cache file
> "/var/cache/cups/job.cache"...
> I [08/Feb/2007:16:32:24 +0400] Full reload complete.
> I [08/Feb/2007:16:32:24 +0400] Listening to 127.0.0.1:631 on fd 3...
> I [08/Feb/2007:16:32:24 +0400] Listening to 192.168.17.13:631 on fd 4...
> I [08/Feb/2007:16:32:24 +0400] Listening to /var/run/cups/cups.sock on fd 5...
> I [08/Feb/2007:16:32:40 +0400] Generating SSL server key...
>
> As you can see, its trying to generate an SSL key and getting stuck.
> Which explains why the https access/ redirects too are getting stuck
> ...
>
> Any ideas what I can do to avoid this? I have put statements like
> "Encryption Never" my cupsd.conf, but that doesn't seem to solve the
> problem.
>
> Thanks,
> Rakhesh
>

No ideas anyone ...?