@@ -264,48 +264,41 @@ When dialog messages related to LXD configuration are shown, please answer in th
#### SSL certificate problem
OSM is installed by default using https with a selfsigned certificated. You will obtain the error '*SSL certificate problem: self signed certificate*' on the client side. To skip this error use the appropriate option to skip certificate validation (e.g. `--insecure` for curl, `--no-check-certificate` for wget, ...). However if for some reason you cannot use this option, you can install this certificate as a valid one in your client system.
By default, OSM installer uses a self-signed certificate for HTTPS. That might lead to the error '_SSL certificate problem: self signed certificate_' on the client side. For testing environments, you might want to ignore this error just by using the appropriate options to skip certificate validation (e.g. `--insecure` for curl, `--no-check-certificate` for wget, etc.). However, for more stable setups you might prefer to address this issue by installing the appropriate certificate in your client system.
To install NBI certificate on the client side (tested for Ubuntu):
Get the certificate file "cert.pem" by one of:
- copy from running docker:
These are the steps to install NBI certificate on the client side (tested for Ubuntu):
1. Get the certificate file `cert.pem` by any of these means:
Add to the list of '*/etc/hosts*' a host called "nbi" with the ip address where OSM is running. Can be localhost if client and server are the same machine. Add (or edit) one of these lines:
3. Add to the list of `/etc/hosts` a host called "nbi" with the IP address where OSM is running.
- It can be `localhost` if client and server are the same machine.
- For localhost, you would need to add (or edit) these lines:
```text
127.0.0.1 localhost nbi
OSM-ip nbi
```
Finally for the URL use host 'nbi' <httts://nbi:9999/osm> (not localhost neither 127.0.0.1). Test it with:
4. Finally, for the URL, use the `nbi` as host name (i.e. <httts://nbi:9999/osm>).