Can't access Mangagement Console - Server Error

Status
Not open for further replies.

Yellow_Flash

Customer
Advanced Certified
Joined
Mar 11, 2019
Messages
288
Reaction score
37
Hi,

I'm having issues with our Debian(v16 iso downloaded from 3cx wesbite) Install.
I had logged into the management console a while back and one of the services wasn't running, I believe it was database server.
I tried to restart it and from that point on I'm not able to login to the Management Console.
When I try to login, it gives me "Server Error"

I am attaching the messages I received when I tried to run the following commands.

service 3CXPhoneSystemMIC01 status
• 3CXPhoneSystemMC01.service - 3CX PhoneSystem 01 Management Console
Loaded: loaded (/lib/systemd/system/3CXPhoneSystemMC01.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Fri 2019-11-08 04:56:32 GMT; 25min ago
Process: 4140 ExecStopPost=/bin/rm -f /var/run/phonesystem/management_console01.socket (code=exited, status=0/SUCCESS)
Process. 4134 ExecStopPost=/bin/rm -f /var/run/phonesystem/3CXPhoneSystemMC01.pid (code=exited, status=0/SUCCESS)
Process. 4113 ExecStart=/usr/lib/3cxpbx/3cxmanagementConsole --pid /var/run/phonesystem/3CXPhoneSystemMC01.pid -p /var/lib/3cxpbx/Instance1/Data/Http/webroot (code=exited, status=137)
Main PID: 4113 (code=exited, status=137)
Nov 08 04:56:31 3cx systemd[1]: Starting 3CX PhoneSystem 01 Management Console...
Nov 08 04:56:32 3cx systemd[1]: 3CXPhoneSystemMC01.service: Main process exited, code=exited , status=137/n/a
Nov 08 04:56:32 3cx systemd[1]: Failed to start 3CX Phonesystem 01 Management Console.
Nov 08 04:56:32 3cx systemd[1]: 3CXPhoneSystemMC01.service: Unit entered failed state.
Nov 08 04:56:32 3cx systemd[11: 3CXPhoneSystemMC01.service: Failed with result 'exit-code'.


service 3CXPhoneSystemMC01 start
Job for 3CXPhoneSystemMC01.service failed because the control process exited with error code.
See "systemctl status 3CXPhoneSystemMC01.service" and "journalctl -xe" for details.


Has someone encounterd the same issue, can someone let me know what can be done to resolve the issue?


Thank you.
 
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
112,363
Messages
592,123
Members
165,536
Latest member
Wecare_ITA