I have allowed elements to receive local network connections in the firewall and in the Privacy & Security settings. I restarted my Mac, iPad and iPhone but am still not able to connect the elements server. I do not have any other third party sw like Little Snitch, etc on my Mac. I also am now getting the server stopped responding error on the safari window.
Any other suggestions ?
@jenkman Steve, I’m not that familiar with MacOS firewall, so this is a few adjacent observations. Maybe just turn off firewall for testing purposes. I’ve run w/o forever, but your environment could have different needs.
php-n, where ‘n’ is somewhat random. This is probably a tiny http server. This process is what receives the request either on 127.0.01:<port_num> or your LAN iplsof | grep 'php.*LISTEN'lsof produces 32k lines.lsof -nP ``-iTCP@127.0.0.1`` -sTCP:LISTEN*<nnnnn>Phil
Project Settings
I followed your suggestions and the port number matched. I even forgot the wifi network on the Mac and reconnected. I have seen that maybe trashing a plist file for the network and doing a restart may work.
None of the above worked. I am unable to use this feature. There is an app from Icon Factory called WorldWideWeb server that you can export your site to and with the iOS companion app you can test out your sites on those devices. I guess I will continue to use that. It’s a web server also and I have not had any issues using it.
It may not be relevant but just in case: On your Mac, check Settings > Privacy & Security > Local Network and see if Elements.App is checked?
@jenkman Here is a test that may help partition the problem.
In MacOS terminal, issue:
nc -vz <yourMacIP> <phpPortNumber>
Example:
nc -vz 192.168.68.52 49879
Connection to 192.168.68.52 port 49879 [tcp/*] succeeded!
This will confirm the php-n process is listening. If it succeeds, then focus towards firewall, or some exotic aspect of your LAN.
on an iphone or iPad, you can install a terminal or shell and issue the above command. You could also try: (be sure you know how to issue a control-C from the terminal app)
ping <yourMacIP>
tracedroute <yourMacIP
@logrunner That’s an interesting point. The php-nprocess that serves the html locally has Elements, as it’s parent. The default is not to inherit this privacy setting, but Elements is probably handling it. (he said without evidence :^) It just worked for me on first try.
Here is a decent summary on Howard Oakley’s The Eclectic Light Company. He’s credible.
I don’t recall being prompted. It just worked. However, much of the discussion is on the sticky nature that is hard to reset. I’d suggest:
@Jenkman I have no evidence this will work, as I haven’t had the problem (other than moving to various LANs) and needing to restart Elements web server (noted above). The ‘nc’ (netcat) command is where I would start.
@ThatPhilGuy Thanks for the assist. I restarted my Mac a second time after the deletion of the network pref files. Now it works flawlessly. I did also try another project file and restart the server. that kicked in the butt a little I suspect.
thanks,
Wow, thanks for the support @ThatPhilGuy, it really sounds like you know your stuff!
Nice to be noticed 