Internal error 1060 - missing CommonName

Hi! I had OwnCloud working well, but needed to reinstall. This time I chose to use an unsigned certificate for SSL/HTTPS access, simply clicking the appropriate checkbbox in the admin page through my browser. Calendars sync well and web access through a browser is also working through https. However, i get the following error when starting the OwnCloud sync program on my client box:

]an internal error number 1060 happened server certificate was missing commonname attribute in subject name

restarting apache on the server gives this:

Could not reliably determine the server's fully qualified domain name, using for ServerName
httpd (pid2080) already rung\ning

From advice on this post, II tried viewing the SSL certificate by entering:

openssl x509 -noout -text -in ssl.crt

but was informed:

Error opening Certificate ssl.crt
3074087176:error:02001002:system library:fopen:No such file or directory:bss_file.c:398:fopen('ssl.crt','r')
3074087176:error:20074002:BIO routines:FILE:CTRLsystem lib:bss_file.c:400:
unable to load certificate

The above link suggested generating a new "snake oil certificate" :smiley: but I'm a bit nervous about doing that, having it fail, and me having to reinstall all over again. The only other advice I found was rather generic at this this post about eliminating SSL errors...and that seems even riskier.

I could revert to using simple http as before, perhaps that is not so bad since I'm blocking all unknown MAC addresses and live in a rather quiet suburban (almost rural!) neighborhood....but if I can, I'd like to use SSL.

So -- any advice? My commandline knowledge is rudimentary at best, so please keep instructions clear and step-by-step. Or, if perhaps the advice given on one of the two websites linked to (above) seems fairly safe, do let me know that and I'll give it a shot.

Thanks in advance!


please move this topic into the following category: as this is not related to ownCloud itself but more about a correct SSL configuration of your Webserver.

If you don't get an answer here you might also do a search on your own on the net. I think such SSL configuration issues are wide spread and you might get some additional infos by users having the same issue on your used webserver.

Oh, i know to do my homework before posting. :wink: I went to copy this to tthe "miscellaneous" section but it looks like it's already moved there -- ??

Anyway, still needing an answer, thanks.