MacPorts question

[mf2k at macports.org]

[Cc’ing Macports Users this time]

> On Oct 7, 2016, at 7:39 AM, Ryan Schmidt <ryandesign at macports.org> wrote:
> 
> 
>> On Oct 7, 2016, at 8:35 AM, mf2k at macports.org wrote:
>> 
>> Hi Ryan,
>> 
>> 
>> Thank you for the reply. So I think that you did not see my other post. I wonder why the mailing list did not send it? Maybe because I had modified the subject title? Here it is again:
> 
> You're right, I didn't see that message.
> 
> 
>> OK, the solution was actually very simple. I added the httpd application to the Firewall. It is located here:
>> 
>> /opt/local/apache2/bin/httpd
>> 
>> This survived a reboot for me. 
>> 
>> Steps to add it (sorry if this is obvious):
>> 1. Starting from the Terminal type:
>>    - cd /opt/local/apache2/bin/
>>    - open .
>> 2. Open System Preferences->Security & Privacy->Firewall tab.
>> 3. Click the lock to unlock it.
>> 4. Click Firewall Options…
>> 5. Click +
>> 6. In Finder, drag “httpd” (now visible in Finder from Step 1) to the dialog. 
>> 
>> <apache firewall.png>
> 
> I'm familiar with this procedure; I've read it on many web sites. But it often simply does not work. Despite the program having been added to the firewall options in this manner, communication remains blocked. I was only able to get it to work by using a terminal command to add it to the firewall, and I don't recall whether that turned out to be a permanent solution or not; I have a feeling it either did not survive reboot or did not survive updating the port that provided that binary.

OK. I played around with this some more and did a bunch of rebooting. The problem is that apache2 itself does not survive the reboot! I tested this by looking at “httpd” in activity monitor. So the firewall rule is correct. But we have another issue that the startupitem for Apache2 is not properly working in El Capitan (at least). 

I use the port load command like so:

 - sudo port load apache2
 - httpd is present and running in Activity Monitor
 - Reboot
 - httpd is gone!


-Frank

> On Oct 7, 2016, at 7:32 AM, Ryan Schmidt <ryandesign at macports.org> wrote:
>>> 
>>> I haven't had time to try your solution. But I saw your follow-up that said that it did not survive a reboot.
>>> 
>>> 
>>>> On Oct 7, 2016, at 8:29 AM, mf2k at macports.org wrote:
>>>> 
>>>> Hi Ryan and Zachary,
>>>> 
>>>> 
>>>> I posted how to do this to the list and got no response. I’m curious why that is? I have to conclude one of the following:
>>>> 
>>>> - It didn’t work for you. 
>>>> - You didn’t see it. 
>>>> - Something else I’m missing?
>>>> 
>>>> I am happy to document the solution on the wiki, but I want to make sure that it works for others first and that my instructions are clear. 
>>>> 
>>>> 
>>>> Cheers!
>>>> Frank
>>>> 
>>>> 
>>>>> On Sep 29, 2016, at 2:05 PM, Ryan Schmidt <ryandesign at macports.org> wrote:
>>>>> 
>>>>> 
>>>>>> On Sep 29, 2016, at 10:30 AM, Zachary Waibel <zjwaibel at gmail.com> wrote:
>>>>>> 
>>>>>> Sorry for the spam, but I have a question regarding my MacPorts installation, and I’m not sure if filing a ticket is the right way to go to get my question answered. If it is then I will do that.
>>>>>> 
>>>>>> Here’s my question: 
>>>>>> 
>>>>>> I've installed the latest MacPorts and my issue is that if I start apache2 using the command "sudo port load apache2” I can then find my website from outside my network.  However, after restarting my Mac and I cannot find my website anymore.  It turns out if I turn off macOS’s Firewall I can then find the website from the outside again.  The other way I can solve it is by doing "sudo port unload apache2” and then "sudo port load apache2”, which seems to open port 80.  However, after a restart the port is not opened, but apache2 is running.  So is MacPorts not compatible with El Capitan’s Firewall?
>>>>>> 
>>>>>> Thank you for any help!
>>>>> 
>>>>> Writing to the macports-users mailing list is probably the right thing to do. I'm Cc'ing the list now. To reply, please make sure you're subscribed to the list first.
>>>>> 
>>>>> I've also been frustrated with the new macOS firewall for some years. I don't understand it. Maybe someone else on the list does and can give us both some advice.
>>>>> 
>>> 
>>> 
>> 
>