Use https URLs when possible

user/pages/02.Tutorials/07.affinity/docs.en.md

@@ -198,12 +198,12 @@ openstack server show server_1 -c name -c hostId
 
 ## Link Resources/Sources
 
-* [Heat Template Guide](http://docs.openstack.org/developer/heat/template_guide/index.html)
-* [Heat Template ServerGroup Resource](http://docs.openstack.org/developer/heat/template_guide/openstack.html#OS::Nova::ServerGroup)
-* [Nova Scheduler Reference](http://docs.openstack.org/mitaka/config-reference/compute/scheduler.html)
-* [Nova Scheduler Affinity Filter](http://docs.openstack.org/mitaka/config-reference/compute/scheduler.html#servergroupaffinityfilter)
-* [OpenStack Client Server Create](http://docs.openstack.org/developer/python-openstackclient/command-objects/server.html#server-create)
-* [OpenStack Client ServerGroup](http://docs.openstack.org/developer/python-openstackclient/command-objects/server-group.html)
+* [Heat Template Guide](https://docs.openstack.org/developer/heat/template_guide/index.html)
+* [Heat Template ServerGroup Resource](https://docs.openstack.org/developer/heat/template_guide/openstack.html#OS::Nova::ServerGroup)
+* [Nova Scheduler Reference](https://docs.openstack.org/mitaka/config-reference/compute/scheduler.html)
+* [Nova Scheduler Affinity Filter](https://docs.openstack.org/mitaka/config-reference/compute/scheduler.html#servergroupaffinityfilter)
+* [OpenStack Client Server Create](https://docs.openstack.org/developer/python-openstackclient/command-objects/server.html#server-create)
+* [OpenStack Client ServerGroup](https://docs.openstack.org/developer/python-openstackclient/command-objects/server-group.html)
 
 ## Links/Examples
 

user/pages/02.Tutorials/10.cinder-multiattach/docs.en.md

@@ -164,4 +164,4 @@ Now it is possible to read and write files on the volume from all VMs.
 ## References
 
 * [SysEleven Stack block storage reference guide](../../04.Reference/04.block-storage/docs.en.md)
-* [OCFS2 best practices guide](http://www.oracle.com/us/technologies/linux/ocfs2-best-practices-2133130.pdf)
+* [OCFS2 best practices guide](https://www.oracle.com/us/technologies/linux/ocfs2-best-practices-2133130.pdf)

user/pages/02.Tutorials/11.object-storage-acls/docs.en.md

@@ -11,7 +11,7 @@ taxonomy:
 
 ### Overview
 
-In this tutorial we will use the [Object Storage](../../04.Reference/05.object-storage/docs.en.md) to create buckets and objects with and limit the access to these by applying ACLs. We will be using the [s3cmd](http://s3tools.org/s3cmd) S3 client and the python library [boto3](https://boto3.readthedocs.io) to manage our resources.
+In this tutorial we will use the [Object Storage](../../04.Reference/05.object-storage/docs.en.md) to create buckets and objects with and limit the access to these by applying ACLs. We will be using the [s3cmd](https://s3tools.org/s3cmd) S3 client and the python library [boto3](https://boto3.readthedocs.io) to manage our resources.
 
 !! **A word of caution**
 !! If possible stick to canned ACLs. We want to discourage the usage of custom ACLs.
@@ -23,7 +23,7 @@ In this tutorial we will use the [Object Storage](../../04.Reference/05.object-s
 * You know the basics of using the [OpenStack CLI-Tools](../../03.Howtos/02.openstack-cli/docs.en.md).
 * Environment variables are set, like shown in the [API-Access-Tutorial](../../02.Tutorials/02.api-access/docs.en.md).
 * You have created EC2 credentials for your OpenStack user to be able to use the [Object Storage](../../04.Reference/05.object-storage/docs.en.md).
-* You have installed [s3cmd](http://s3tools.org/s3cmd)
+* You have installed [s3cmd](https://s3tools.org/s3cmd)
 * You have installed python and the [boto3](https://boto3.amazonaws.com/v1/documentation/api/latest/index.html) library
 
 We suggest you use the python library boto3 to reproduce all scenarios shown in this tutorial. Using only s3cmd will leave buckets open for group members. We are in contact with the software manufacturer of our object storage about that.
@@ -45,16 +45,16 @@ check_ssl_hostname = False
 
 #host_base = s3.cbk.cloud.syseleven.net
 #host_bucket = %(bucket).s3.cbk.cloud.syseleven.net
-#website_endpoint = http://%(bucket)s.s3.cbk.cloud.syseleven.net/%(location)s/
-#website_endpoint = http://s3.cbk.cloud.syseleven.net/%(bucket)s/%(location)s/
+#website_endpoint = https://%(bucket)s.s3.cbk.cloud.syseleven.net/%(location)s/
+#website_endpoint = https://s3.cbk.cloud.syseleven.net/%(bucket)s/%(location)s/
 host_base = s3.dbl.cloud.syseleven.net
 host_bucket = %(bucket).s3.dbl.cloud.syseleven.net
-#website_endpoint = http://%(bucket)s.s3.dbl.cloud.syseleven.net/%(location)s/
-website_endpoint = http://s3.dbl.cloud.syseleven.net/%(bucket)s/%(location)s/
+#website_endpoint = https://%(bucket)s.s3.dbl.cloud.syseleven.net/%(location)s/
+website_endpoint = https://s3.dbl.cloud.syseleven.net/%(bucket)s/%(location)s/
 #host_base = s3.fes.cloud.syseleven.net
 #host_bucket = %(bucket).s3.fes.cloud.syseleven.net
-#website_endpoint = http://s3.fes.cloud.syseleven.net/%(bucket)s/%(location)s/
-#website_endpoint = http://%(bucket)s.s3.fes.cloud.syseleven.net/%(location)s/
+#website_endpoint = https://s3.fes.cloud.syseleven.net/%(bucket)s/%(location)s/
+#website_endpoint = https://%(bucket)s.s3.fes.cloud.syseleven.net/%(location)s/
 ```
 
 We can configure an s3 client with the boto3 library using following python snippet (example is in DBL region):

user/pages/03.Howtos/05.nova-rescue-mode/docs.en.md

@@ -148,7 +148,7 @@ $ sudo testdisk /dev/vdb1
 
 TestDisk 7.0, Data Recovery Utility, April 2015
 Christophe GRENIER <[email protected]>
-http://www.cgsecurity.org
+https://www.cgsecurity.org
 
   TestDisk is free software, and
 comes with ABSOLUTELY NO WARRANTY.

user/pages/04.Reference/05.object-storage/docs.en.md

@@ -102,7 +102,7 @@ openstack ec2 credentials list
 
 ### S3cmd
 
-Information about the `s3cmd` client can be found [here](http://s3tools.org/s3cmd).
+Information about the `s3cmd` client can be found [here](https://s3tools.org/s3cmd).
 
 Now you can create an `s3cmd` configuration which could look like this:
 
@@ -117,16 +117,16 @@ check_ssl_hostname = False
 
 #host_base = s3.cbk.cloud.syseleven.net
 #host_bucket = %(bucket).s3.cbk.cloud.syseleven.net
-#website_endpoint = http://%(bucket)s.s3.cbk.cloud.syseleven.net/%(location)s/
-#website_endpoint = http://s3.cbk.cloud.syseleven.net/%(bucket)s/%(location)s/
+#website_endpoint = https://%(bucket)s.s3.cbk.cloud.syseleven.net/%(location)s/
+#website_endpoint = https://s3.cbk.cloud.syseleven.net/%(bucket)s/%(location)s/
 host_base = s3.dbl.cloud.syseleven.net
 host_bucket = %(bucket).s3.dbl.cloud.syseleven.net
-#website_endpoint = http://%(bucket)s.s3.dbl.cloud.syseleven.net/%(location)s/
-website_endpoint = http://s3.dbl.cloud.syseleven.net/%(bucket)s/%(location)s/
+#website_endpoint = https://%(bucket)s.s3.dbl.cloud.syseleven.net/%(location)s/
+website_endpoint = https://s3.dbl.cloud.syseleven.net/%(bucket)s/%(location)s/
 #host_base = s3.fes.cloud.syseleven.net
 #host_bucket = %(bucket).s3.fes.cloud.syseleven.net
-#website_endpoint = http://s3.fes.cloud.syseleven.net/%(bucket)s/%(location)s/
-#website_endpoint = http://%(bucket)s.s3.fes.cloud.syseleven.net/%(location)s/
+#website_endpoint = https://s3.fes.cloud.syseleven.net/%(bucket)s/%(location)s/
+#website_endpoint = https://%(bucket)s.s3.fes.cloud.syseleven.net/%(location)s/
 ```
 
 Next, create an S3 Bucket.

user/pages/04.Reference/08.network/02.lbaas/docs.en.md

@@ -86,7 +86,7 @@ The test protocol (health monitor type) can be configured, among other things, u
 
 The pool together with the pool members represent a set of backend servers. It is possible to configure the protocol between backend and load balancer.
 
-Using the special PROXY protocol it is possible to retrieve the client IP address, even with TCP or non-terminated HTTPS load balancing protocols. Please refer to the HAProxy documentation for a [specification of the PROXY protocol](http://www.haproxy.org/download/1.8/doc/proxy-protocol.txt).
+Using the special PROXY protocol it is possible to retrieve the client IP address, even with TCP or non-terminated HTTPS load balancing protocols. Please refer to the HAProxy documentation for a [specification of the PROXY protocol](https://www.haproxy.org/download/1.8/doc/proxy-protocol.txt).
 
 Your application must support the PROXY protocol. It is possible to add a reverse proxy like nginx between your application and the Octavia loadbalancer to add PROXY support. The nginx documentation provides a how-to for [receiving the proxy protocol](https://docs.nginx.com/nginx/admin-guide/load-balancer/using-proxy-protocol/).
 

user/pages/04.Reference/08.network/docs.en.md

@@ -111,7 +111,7 @@ See our terraform examples on GitHub [for an example how to connect two regions
 
 ### Known interoperability issues
 
-As control over configuration details is limited in this VPNaaS implementation, connections to external destinations require flexibility on the remote side. For example there are multiple ways specified in IPsec how to connect multiple networks over a connection. Our VPNaaS supports only the variant, where each pair of networks uses a distinct SA (security association). This is known to cause problems hard to diagnose in conjunction with [GCP Cloud VPN](https://cloud.google.com/vpn/docs/concepts/choosing-networks-routing#ts-ip-ranges). One possible workaround is to set up distinct connections for each pair of networks, which can become awkward to maintain. Another would be to use a TCP VPN like [OpenVPN](https://openvpn.net/), [VTun](http://vtun.sourceforge.net/), [Wireguard](https://www.wireguard.com/), [Tinc](https://tinc-vpn.org/) or [Zerotier](https://www.zerotier.com/). As a third alternative approach, we are working on the preconditions needed to run virtual appliances like [PFSense](https://www.pfsense.org/) in our platform and let them provide self managed VPN services.
+As control over configuration details is limited in this VPNaaS implementation, connections to external destinations require flexibility on the remote side. For example there are multiple ways specified in IPsec how to connect multiple networks over a connection. Our VPNaaS supports only the variant, where each pair of networks uses a distinct SA (security association). This is known to cause problems hard to diagnose in conjunction with [GCP Cloud VPN](https://cloud.google.com/vpn/docs/concepts/choosing-networks-routing#ts-ip-ranges). One possible workaround is to set up distinct connections for each pair of networks, which can become awkward to maintain. Another would be to use a TCP VPN like [OpenVPN](https://openvpn.net/), [VTun](https://vtun.sourceforge.net/), [Wireguard](https://www.wireguard.com/), [Tinc](https://tinc-vpn.org/) or [Zerotier](https://www.zerotier.com/). As a third alternative approach, we are working on the preconditions needed to run virtual appliances like [PFSense](https://www.pfsense.org/) in our platform and let them provide self managed VPN services.
 
 ## Customer public IP space (Bring your own IP addresses)
 

user/pages/04.Reference/11.orchestration/docs.en.md

@@ -404,7 +404,7 @@ You can also build a setup where a virtual machine has more than 50 GiB of stora
 
 Heat template files are written in YAML and describe the virtual infrastructure. They consist of five important sections:
 `heat_template_version`, `description`, `parameters`, `resources` and `output`.
-You can find the current specification of all heat components and options at the [Heat Project online documentation](http://docs.openstack.org/developer/heat/template_guide/openstack.html).
+You can find the current specification of all heat components and options at the [Heat Project online documentation](https://docs.openstack.org/developer/heat/template_guide/openstack.html).
 
 ### Heat version
 

user/pages/04.Reference/12.timezone-ntp/docs.en.md

@@ -16,6 +16,6 @@ Please be aware that the time shown in your instance logs may differ from the lo
 
 SysEleven does **not** provide time servers for you to use. Please select public time servers in your instances.
 
-The following list could be a starting point:  
+The following list could be a starting point:
 
-[http://www.pool.ntp.org/en/use.html](http://www.pool.ntp.org/en/use.html)
+* <https://www.pool.ntp.org/en/use.html>