Timeline for Trying to set up self signed certificates on other devices
Current License: CC BY-SA 4.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 4, 2024 at 11:33 | history | edited | terdon♦ | CC BY-SA 4.0 |
setup is a noun, oddly enough; The verb for is set up.
|
| Jun 4, 2024 at 11:01 | comment | added | arizona525 | Thanks again, I've been struggling with this for so long. To fix the IP issue. You have to change the cfg - instead of DNS in .cfg file you have to pass IP. Example: [alt_names] IP.1 = 127.0.0.1 | |
| Jun 4, 2024 at 10:52 | comment | added | Marcus Müller | "is not yet valid" is pretty explicit about the certificate not being valid at this point in time :) | |
| Jun 4, 2024 at 10:49 | comment | added | arizona525 | How did you know it was the time issue? I had to enable automatic time synchronisation on my Arch PC, and then the error went away. Thank you. Now another issue that I will try to solve is something complaining about the DNS - curl: (60) SSL: no alternative certificate subject name matches target ipv4 address '192.168.1.218' More details here: curl.se/docs/sslcerts.html curl failed to verify the legitimacy of the server and therefore could not establish a secure connection to it. To learn more about this situation and how to fix it, please visit the web page mentioned above. | |
| Jun 4, 2024 at 10:34 | comment | added | Marcus Müller | "curl: (60) SSL certificate problem: certificate is not yet valid" check the clocks of all the machines involved. | |
| Jun 4, 2024 at 10:22 | history | edited | arizona525 | CC BY-SA 4.0 |
ssl err
|
| Jun 4, 2024 at 9:56 | history | edited | arizona525 | CC BY-SA 4.0 |
correct ip
|
| S Jun 4, 2024 at 9:55 | review | First questions | |||
| Jun 6, 2024 at 23:39 | |||||
| S Jun 4, 2024 at 9:55 | history | asked | arizona525 | CC BY-SA 4.0 |