New Version Available: v{.{ :: {

[RobRiv]

Updated to V1.5.5f and all ok except with Admin initial page: showing "New Version Available: v{.{ :: {"
When trying "Download Here" green button, it goes to http://my domain/my shop/admin/%7B which ends in a 404 page not found.
my domain, my shop and admin are not the actual links. Anybody with same problem and or a solution?
Thanks.

[RobRiv]

This is what appears in Admin home page.

[dennisns7d]

I encountered this a few months ago on my local sandbox (XAMPP). I determined that a CURL error was being tripped when obtaining the current version information from the version server. I'm not remember the exact error (something to do with certificate verification), but installing a cacert.pem file on my computer and adding some information to php.ini solved the problem.

A more detail explanation can be found here.

The weird string of characters display is the result of the code attempting to extract version information from the curl error string.

[RobRiv]

I encountered this a few months ago on my local sandbox (XAMPP). I determined that a CURL error was being tripped when obtaining the current version information from the version server. I'm not remember the exact error (something to do with certificate verification), but installing a cacert.pem file on my computer and adding some information to php.ini solved the problem.

A more detail explanation can be found here.

The weird string of characters display is the result of the code attempting to extract version information from the curl error string.

Thank you dennisns7d for your response. My site is not SSL secured. I checked curl working using curltester.php and all is ok except for SSL.
Must be some other problem...

[mc12345678]

Thank you dennisns7d for your response. My site is not SSL secured. I checked curl working using curltester.php and all is ok except for SSL.
Must be some other problem...

The SSL referenced with this issue is different than when a customer tries to reach your site. The server communicates to other servers and that communication should be performed with SSL. Performing the above actions sounds like it would solve your issue based on what has been described by both of you. It will not offer customers the ability to access your site via SSL.

[RobRiv]

The SSL referenced with this issue is different than when a customer tries to reach your site. The server communicates to other servers and that communication should be performed with SSL. Performing the above actions sounds like it would solve your issue based on what has been described by both of you. It will not offer customers the ability to access your site via SSL.

Thank you mc12345678. I see the difference. One question then is why I didn't have the same problem in version 1.5.4.? Is version 1.5.5f changing anything on this regard?
Thank you again.

[mc12345678]

It's been a while since I've looked into it/described it in detail, but it comes down to increased security (encryption at the origination point) and more frequent use of https: in communication. If anything it should be looked at as a good thing even if it meant having to make a change to the server.

[RobRiv]

Further to mc12345678 suggestion, I run curltester.php and found the following error:
"Windows server: Curl error (60): SSL Certificate problem: Unable to get local issuer"
I investigated previous threads on the issue but are not useful to me for the following reason:
Site is hosted at shared Windows server and therefore can't access php.ini nor install certificates on the server.
Has anybody have the same problem and found a solution?
Thank you.

[mc12345678]

Further to mc12345678 suggestion, I run curltester.php and found the following error:
"Windows server: Curl error (60): SSL Certificate problem: Unable to get local issuer"
I investigated previous threads on the issue but are not useful to me for the following reason:
Site is hosted at shared Windows server and therefore can't access php.ini nor install certificates on the server.
Has anybody have the same problem and found a solution?
Thank you.

Solution generally is either seek assistance from the host about the changes necessary or seek a new host.

[RobRiv]

Solution generally is either seek assistance from the host about the changes necessary or seek a new host.

Than you mc12345678 for such a quick answer.
It seems too radical an action...
May be I can do something about it.