htdave
The system messages tell us that there is currently an issue with a certificate - which is normal if you use a self-signed certificate; this is the default unless you install a proper one yourself.
Unfortunately, this has nothing to do with the R3 service not being able to access the repository. This is something that is extremely straightforward - as long as you have HTTPS access to the internet and DNS working, your R3 system can access the repository. I have not seen this fail unless there is a firewall blocking basically all internet access or a network misconfiguration. I can offer to look over your system to find issues - but I would need to charge for the time.
Regarding certificates: This is not something that can be easily explained, because it really depends. On how your systems are operated, if they need to be accessible to the internet, how your clients are configured in your own network, if you have a PKI inhouse or not.
Some basic ideas:
- If you have only internal clients and the system is not accessible from the internet, you can think about deploying an internal root certificate and installing it on your clients. There are many articles and guides on how to do that but it does require some admin skills. There are also straightforward approaches, depending on whether you have a modern ActiveDirectory on hand.
- If your system is accessible to the internet, you could use services like Let´sEncrypt to auto-generate certificates for your R3 system.
There are also options to buy certificates online and then use internal DNS to redirect traffic to local systems. But again, this is highly specific to your environment, tech stack, internal skills and requirements.
Both these topics (how the R3 server reaches the repository and how certificates can work) are not related to Linux. This works basically the same on Windows Server, which btw. you can also use, if you prefer it over Linux and have access to.
