Windows Server 2016 Desktop version with updates through 8/17/2019.

Installed in the default location.

Required ports or forwarded to the server and are open on the server. 80, 443, 2399, 5003, 16000

The instructions for getting a certificate are very confusing.  When I follow the instructions, I get the following error(s):

 

My FQDN is ARTinLizzies.com

 

OpenSSL> req -nodes -newkey rsa:2048 -keyout artinlizzies.com.key -out artinlizzies.com.csr

Can't open C:\Users\tony_zepeda.SC\Desktop\git_fmsource\fmsource\ThirdParty\ports\openssl\InstallDir/openssl.cnf for reading, No such file or directory

2412:error:02001003:system library:fopen:No such process:crypto\bio\bss_file.c:72:fopen('C:\Users\tony_zepeda.SC\Desktop\git_fmsource\fmsource\ThirdParty\ports\openssl\InstallDir/openssl.cnf','r')

2412:error:2006D080:BIO routines:BIO_new_file:no such file:crypto\bio\bss_file.c:79:

Generating a RSA private key

...........+++++

..............+++++

writing new private key to 'artinlizzies.com.key'

-----

unable to find 'distinguished_name' in config

problems making Certificate Request

2412:error:0E06D06A:configuration file routines:NCONF_get_string:no conf or environment variable:crypto\conf\conf_lib.c:270:

error in req

OpenSSL>

 

Maybe I guessed wrong on what the inputs should be?  What is tony_zepeda.sc????

any particular reason why you are using the openssl utility and not just the fmsadmin command line?

Also look for the "missing filemaker server admin tool" which builds a wrapper around the necessary command lines, makes it a whole lot easier.

 

tony zepeda is probably a contributor to the openssl utility you downloaded and there's a broken link in the source code somewhere.

Wim, thanks for taking time to respond to my question.  I had just purchased the upgrade from 15 to 18 and then upgraded to 18.0.2.  Filemakers release notes said that the fmsadmin process would not work with 18.0.2 and actually suggested the openssl to replace their fmsadmin tool/process.  

To avoid the problem I uninstalled the program (using a process provided by FileMaker), reinstalled version 18 without the update and the fmsadmin process seems to be working now.