The presence of a SSL certificate in and of itself is not the issue. In fact, that file only gets read into memory by core if an extension is trying to make a remote call to another service.

With that said though, the file has moved to libraries/src/Http/Transport/cacert.pem, if an extension is trying to use that file on its own the reference needs to be updated.

@ranpre have you found which Extension is trying to use?

Can't say yet, since log files are available on Monday earliest. However, when searching by FTP I found 8 different versions of cacert.pem co-existing on the server.

Another observation ist that the error indeed only happens on SSL secured site. When upgrading to J3.8 on a non-SSL test site (holding an exact copy of the SSL-site) everything went fine.

@ranpre Please give paths of cacert.pem.

@ranpre /libraries/joomla/http/transport/cacert.pem should not exist after update to Joomla 3.8.0 if this file exist on ssl site in question then update was not completed correctly.

Hmm. This contradicts somehow what @mbabker said before. If I understood him right, there's extensions that may use the file.

quote from @mbabker reply

With that said though, the file has moved to libraries/src/Http/Transport/cacert.pem, if an extension is trying to use that file on its own the reference needs to be updated.

So correct localisation of this file in 3.8.0 is libraries/src/Http/Transport/cacert.pem. Try using postupdate.php on dev copy of the site.

@ranpre any Updates as @wojsmol suggested?

@franz-wohlkoenig After days of faithing with those errors I can teal you that - they are not remove 1 file cases.

So its better to discuss on forums - Migrating and Upgrading to Joomla! 3.x and close here?

@franz-wohlkoenig yes

closed as stated above.

Set to "closed" on behalf of @franz-wohlkoenig by The JTracker Application at issues.joomla.org/joomla-cms/18004