I’ve found a number of posts online about this, but the answers are a bit above my skill level. Surely somebody running FreeBSD on Digital Ocean has/had the same problem.
# sudo freebsd-update fetch
Looking up update.FreeBSD.org mirrors... 5 mirrors found.
Fetching metadata signature for 10.2-RELEASE from update6.freebsd.org... invalid signature.
Fetching metadata signature for 10.2-RELEASE from update5.freebsd.org... invalid signature.
Fetching metadata signature for 10.2-RELEASE from update4.freebsd.org... invalid signature.
Fetching metadata signature for 10.2-RELEASE from update2.freebsd.org... invalid signature.
Fetching metadata signature for 10.2-RELEASE from update3.freebsd.org... invalid signature.
No mirrors remaining, giving up.
Regarding this solution:
Edit /etc/freebsd-update.conf and check the line:
Components src world kernel
and change it to:
Components world kernel
My freebsd-update.conf was already set up like that.
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
if you have for example 10.3-STABLE and have error after freebsd-update upgrade -r 11.3-RELEASE
src component not installed, skipped Looking up update.FreeBSD.org mirrors… 3 mirrors found. Fetching metadata signature for 10.3-STABLE from update1.freebsd.org… failed. Fetching metadata signature for 10.3-STABLE from update2.freebsd.org… failed. Fetching metadata signature for 10.3-STABLE from update4.freebsd.org… failed.
need setenv UNAME_r “10.3-RELEASE” then freebsd-update upgrade -r 11.3-RELEASE
The solution is related to how the openssl file was altered during the upgrade. Link goes to the solution in the freebsd forum.
https://forums.freebsd.org/threads/invalid-signature-using-freebsd-update.54234/
I’m not sure the link is showing up. The solution was to comment out these lines in the openssl.conf file
<<<<<<< current version
=======
# $FreeBSD: releng/10.2/crypto/openssl/apps/openssl.cnf 238405 2012-07-12 19:30:53Z jkim $
>>>>>>> 10.2-RELEASE
Become a contributor for community
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
DigitalOcean Documentation
Full documentation for every DigitalOcean product.
Resources for startups and AI-native businesses
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
The developer cloud
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Start building today
From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.
