Log in to create and rate content, and to follow, bookmark, and share content with other members. Not a member? Join Now!

AnsweredAssumed Answered

I'm loosing access over port 443

Question asked by ibrahim_bittar on Jan 28, 2019
Latest reply on Jan 29, 2019 by Julio Toledo

Like • Show 0 Likes0
Comment • 6

Hi All

Last week I lost access to my server over port 443. It was out of the blue. No warning, no nothing. Just stopped working.

Today I reinstalled FileMaker Server 17. Everything was working fine until this afternoon. I added some files to the HTTPS docs folder, changed their permissions to Owner = fmserver (read, write), Group = fmsadmin (read, write), Everyone (read only).

Now access through port 443 is blocked. This morning I also upgraded the OS to Mojave and everything was fine .

Hope someone can shed some light here...

My server is a Mac Mini 2014 which was working without a hassle for a couple years.

No one else has this question

Outcomes

6 Replies

ibrahim_bittar Jan 28, 2019 5:01 PM
Mark Correct
Correct Answer
Some more info:

Digging in the log files I found the error: AH00169: caught SIGTERM, shutting down.

It seems to be an Apache problem. I'm looking how to solve it in Google. If someone has seen this before please chime in. I'll appreciate it.
1 person found this helpful
Like • Show 0 Likes0
Actions
Suresh @ ibrahim_bittar on Jan 28, 2019 8:09 PM
Mark Correct
Correct Answer
Hi ibrahim_bittar,

Good Day!

Is there any possibilities to restart Apache Server by sudo code? If Yes, kindly validate the following...

try Code:
```
sudo /etc/init.d/apache2 stop 
```
followed by Code:
```
sudo killall apache2 
```
then make sure no services are running on port 80 Code:
```
sudo netstat -l|grep www 
```
then (re)start apache Code:
```
sudo /etc/init.d/apache2 restart
```
Source : apache2 restart [fail]

HTH,
Suresh
1 person found this helpful
Like • Show 0 Likes0
Actions
ibrahim_bittar @ Suresh on Jan 29, 2019 6:38 AM
Mark Correct
Correct Answer
Hi Suresh, thank you for your response. Unfortunately it didn't work .

I got "command not found" when I tried to use "sudo /etc/init.d/apache2 restart". Then I tried with "sudo /Library/FileMaker\ Server/HTTPServer/bin/httpdctl start" and I got this:

========== start ==========
Tue Jan 29 08:33:48 CST 2019
/usr/sbin/httpd -k start -D FILEMAKER -f /Library/FileMaker Server/HTTPServer/conf/httpd.conf
exit code 1

I've been looking for solutions to this error but have not found nothing conclusive yet. I'll keep you posted.
Like • Show 1 Like1
Actions
ibrahim_bittar Jan 29, 2019 5:30 PM
Mark Correct
Correct Answer
Problem solved! (for now, fingers crossed)

It seems that it had to do with a faulty SSL certificate.

When I created my CSR, I used an online CSR generator that allowed me to use periods and commas in my request. Our company legal name is Eikonsys, S.A. de C.V. and the software allowed me to create the CSR with those characters, silly me...

The CSR creation service is OpenSSL CSR Tool - Create Your CSR Faster | DigiCert.com

When you use this generator it creates a terminal command to generate the CSR:
openssl req -new -newkey rsa:2048 -out xxxxx_com.csr -keyout xxxxx_com.key -subj "/C=MX/ST=Guanajuato/L=León/O=Eikonsys S.A. de C.V./OU=IT/CN=xxxxx.com"

Do you see the the accent in "León" (our city) and commas and periods in the Organization Name?, wrong!, I masked the domain name on purpose.

Now I used the same service but I intentionally removed all non alphabetical characters and created a new CSR, rekeyed it with GoDaddy and reinstalled. After restarting the server everything seems to be working normally again.
4 people found this helpful
Like • Show 1 Like1
Actions
Julio Toledo @ ibrahim_bittar on Jan 29, 2019 5:38 PM
Mark Correct
Correct Answer
So takeaway here seems to be no special characters diacriticals in your CSR's
Like • Show 3 Likes3
Actions
Julio Toledo @ Julio Toledo on Jan 29, 2019 7:57 PM
Mark Correct
Correct Answer
"special chargers OR diacriticals" (auto-correct is a plague invading all operating systems).
Like • Show 2 Likes2
Actions

I'm loosing access over port 443

Outcomes

Related Content

Recommended Content