Can't access Mangagement Console - Server Error

Status
Not open for further replies.
Thank you.
I will monitor the system for a week and see how it goes.
 
Also, what does it mean by

"There's no valid Domain certificate/key for SIP domain Custom_FQDN.

I saw this while going through the activity log, after the reboot was completed.
 
Also, what does it mean by

"There's no valid Domain certificate/key for SIP domain Custom_FQDN.

I saw this while going through the activity log, after the reboot was completed.
what type of FQDN are you currently using? (3CX or custom?)
 
If the management console does not load, check if any SSL errors can be seen in the nginx logs. In .\3CX Phone System\Bin\nginx\logs\error.log an emergency error will be generated if any mistake was made in the SSL import.

[emerg] 2568#896: PEM_read_bio_X509_AUX(".\3CX Phone System\Bin\nginx/conf/instance1/ol.eg.com-crt.pem") failed (SSL: error:0906D06C: PEM routines: PEM_read_bio:no start line:Expecting: TRUSTED CERTIFICATE)
 
If the management console does not load, check if any SSL errors can be seen in the nginx logs. In .\3CX Phone System\Bin\nginx\logs\error.log an emergency error will be generated if any mistake was made in the SSL import.

[emerg] 2568#896: PEM_read_bio_X509_AUX(".\3CX Phone System\Bin\nginx/conf/instance1/ol.eg.com-crt.pem") failed (SSL: error:0906D06C: PEM routines: PEM_read_bio:no start line:Expecting: TRUSTED CERTIFICATE)

Hi, the install is Debian.
Where do I have to check these files in Debian Install?
Thank you.
 
Hello,

Look under /var/log/nginx/

You can also find historic logs there if you want to peek into past events
 
Hello,

Look under /var/log/nginx/

You can also find historic logs there if you want to peek into past events
Hi,
I had a check on the log files and the only thing worth noting is,

[warn] 553#553: "ssl_stapling" ignored, issuer certificate not found.

What does this mean?
 
I would suggest to look it up online, these are specifically nginx logs and I'm not too familiar with them.

If I'm not mistaken though, nginx might give this error if you use self-signed certs that didnt come from a Root CA so it could not validate them. You are using a custom FQDN as you said so this depends on what certs you feed into nginx
 
Status
Not open for further replies.

Forum statistics

Threads
111,934
Messages
589,819
Members
164,811
Latest member
aurorasigntrtechitnet