Yes you are right it was a cache problem because of header time config.

Found the solution here :
https://community.letsencrypt.org/t/always-redirect-to-https/10838/2

Seems like you added the HSTS header to your apache conf. This directive tells the browser visiting your site that for the max age configured in the directive, the browser should access your site always using https. So the “problem” is in your browser right now.

In your apache conf you should have/had something like this:

Header always set Strict-Transport-Security "max-age=63072000; includeSubdomains; preload"

3.- Recover all the apache and letsencrypt files that you removed, edit apache conf and change the header directive using max-age=0, something like this:
Header always set Strict-Transport-Security “max-age=0; includeSubdomains; preload”

Reload or restart apache and visit again your site, once visited the browser will ignore the htst header and you could access your site using only http.

I modified this directive using max-age=0 and it worked right away....