Your webserver is not forcing the use of SSL.
You may want to add a redirect to ensure a secure connection is used
Strange, because i have a redirect, and i cant goto http
(2) Protocols
You currently have TLSv1 enabled.
This version of TLS is being phased out. This warning won't break your padlock, however if you run an eCommerce site, PCI requirements state that TLSv1 must be disabled by June 30, 2018.
osiris@erazer ~ $ curl -LIv trygghetsmaklarna.se
* Trying 3.125.81.48:80...
* Connected to trygghetsmaklarna.se (3.125.81.48) port 80 (#0)
> HEAD / HTTP/1.1
> Host: trygghetsmaklarna.se
> User-Agent: curl/7.84.0
> Accept: */*
>
* Mark bundle as not supporting multiuse
< HTTP/1.1 200 OK
HTTP/1.1 200 OK
< Date: Mon, 24 Oct 2022 13:58:49 GMT
Date: Mon, 24 Oct 2022 13:58:49 GMT
< Server: Apache
Server: Apache
< Link: <http://trygghetsmaklarna.se/wp-json/>; rel="https://api.w.org/", <http://trygghetsmaklarna.se/wp-json/wp/v2/pages/1317>; rel="alternate"; type="application/json", <http://trygghetsmaklarna.se/>; rel=shortlink
Link: <http://trygghetsmaklarna.se/wp-json/>; rel="https://api.w.org/", <http://trygghetsmaklarna.se/wp-json/wp/v2/pages/1317>; rel="alternate"; type="application/json", <http://trygghetsmaklarna.se/>; rel=shortlink
< Content-Type: text/html; charset=UTF-8
Content-Type: text/html; charset=UTF-8
<
* Connection #0 to host trygghetsmaklarna.se left intact
osiris@erazer ~ $
Certbot doesn´t. The (awful) tutorial you've used uses certbot certonly, which does not modify your webserver in any way. So Certbot cannot even "activate TLSv1".
Please don't use the guide you've currently followed, but see the "Important" box at the top of it. Using Certbot with Bitnami can only lead to tears and regrets.