Website service over LAN on macOS Venutra—Jekyll RB's server

Got it sorted.

When running the

jekyll serve

command, to enable Ruby to listen to all the bindable addresses I need to identify the host, which can be shortcutted to 0.0.0.0.

Then macOS dutifully asks whether I do indeed want to allow Ruby to listen on those ports through a popup.

Not sure how I got around this in the past. Probably something dumb on my part with the Firewall.

A good article on this, generally, as to the

jekyll serve

command can be found here:

https://zarino.co.uk/post/jekyll-local-network/

Hope this helps anyone else messing with this. (I suspect there is another way to force a bind and listening, but I did not find it before I found this.)

Whelp, up, ports are closed. Sigh. Now I just have to figure out why, and how to open them up. NMAP results:

Nmap scan report for 192.168.1.*

Host is up (0.0078s latency).

Not shown: 998 closed tcp ports (conn-refused)

PORT   STATE  SERVICE

5000/tcp filtered upnp

7000/tcp filtered afs3-fileserver

Nmap done: 1 IP address (1 host up) scanned in 5.15 seconds

No, the Apache-based solution doesn't work. In fact, in that solution, if I recall, it does not discuss opening up the server to the LAN anyhow. (There is another post on changing the config file to grant access to all hosts.)

The issue appears to be an inability to access the TCP port for the Mac, but I'm not sure why that is not the case (or what I did in prior OS versions to allow for it).

It's a pain. Installing Homebrew so I can add nmap and do some port scanning. Maybe that will help narrow it down.

I know the server is up and running. I can access it on the computer itself. I simply cannot hit port 4000 and access it on the LAN. But I CAN ping the computer on the LAN.

Alas. I feel like there is a setting somewhere obivous that I'm missing.

Yea. I know. It should just work. And, yeah, I don't use the system version of Ruby. Chruby is installed.

Once again, the issue is that everything works on the machine, but the LAN cannot access the server for some reason.

And now I'm stuck installing Homebrew on one of those external machines on the LAN so I can do some port sniffing.

It's a bit of a pain. For example, your take on installing Apache would run into this same issue (although, I do wonder if changing some of the hostname access settings in config files would work).

I could maybe edit /etc/hosts, but my machines IP address may change over time (it's assigned by the router).

It should just work—and it DID just work in older macOS versions—but, for the life of me, I can't remember what the switch was that I used to get it to work. (I think it was as simple as opening up the Port in the Firewall; but that's OFF entirely in Ventura, so that shouldn't be it, either.)

Just waiting on Homebrew to stop being a shallow clone, doing a brew update, and trying out nmap . . .

And on the local machine running the server, here is what NMAP shows:

Nmap scan report for localhost (127.0.0.1)

Host is up (0.00011s latency).

Not shown: 996 closed tcp ports (conn-refused)

PORT   STATE SERVICE

631/tcp open ipp

4000/tcp open remoteanything

5000/tcp open upnp

7000/tcp open afs3-fileserver

RemoteAnything is the Jekyll Server (running on port 4000).

For the life of me, I cannot sort out how to open up this port. But it may be a tomorrow issue.

It stinks when you get around to missing Linux.

(And Homebrew is perfectly fine. It's less risky than Macports. And if you're doing serious development on the Mac, then it's a great tool for setting up common development environments across POSIX and *NIX systems.)