On Thu, Aug 01, 2019 at 08:41:32AM +0200, Nicolas Mailhot via devel wrote: > Le mercredi 31 juillet 2019 à 16:10 -0700, Brian C. Lane a écrit : > > > > It's odd that they would work from an installed system and not > > anaconda. > > Are you using a self-signed cert on them? > > No, a proper public cert, that even Firefox accepts without grumbling > (not an easy thing to manage those days). Very odd then, possibly a crypto support mismatch with the installer image? dnf has *very* verbose logs in dnf.librepo.log if it is failing inside dnf I'd expect something useful there. You can also try curl from the cmdline while booted into the installer image. I'd probably start with that. > > > If so you can pass > > inst.noverifyssl to anaconda to tell it to ignore the error but still > > use https. > > Thanks for the suggestion, I had forgotten about it. Is it possible to > do that manually without a kickstart? Fot that installation workflow we > start from a minimal unmodified install, and customize it in a later > stage. inst.noverifyssl on the cmdline, or in your kickstart pass --noverifyssl to the url and repo lines: https://pykickstart.readthedocs.io/en/latest/kickstart-docs.html#url -- Brian C. Lane (PST8PDT) - weldr.io - lorax - parted _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
