Can't access new install

Discussion in 'Plesk Automation Suggestions and Feedback' started by Robbie Wright, Oct 31, 2015.

Tags:
  1. Robbie Wright

    Robbie Wright Bit Poster

    Messages:
    5
    Having a hard time getting a new install of PPA to work right. In a NAT'd environment, set the single IP to the private address since that's what's bound to the internal NIC. Getting this error in the log:

    [emerg] 9045#0: BIO_new_file("/usr/local/psa/admin/conf/httpsd.pem") failed (SSL: error:02001002:system library:fopen:No such file or directory:fopen('/usr/local/psa/admin/conf/httpsd.pem','r') error:2006D080:BIO routines:BIO_new_file:no such file)

    Ran through this kb article to recreate the key, which is now in the directory, but we still can't access the control panel and it is still throwing the error even though the file exists. Can't even telnet to the server which tells me the PPA service(s) aren't listening on the right port because it can't find the SSL cert.

    Through SSH, can you turn off the SSL for the control panel and test access over HTTP? How can we recreate the cert again or get the service to listen on the right port? Netstat shows https is bound but it is acting like it isn't.
     
  2. Robbie Wright

    Robbie Wright Bit Poster

    Messages:
    5
    If anyone else hits this, when ended up reinstalling PPA to get rid of the issue.
     
  3. writesindia

    writesindia Bit Poster

    Messages:
    1
    Hello
    Anyone here?
     

Share This Page